Whenever I hear a product pitch, the thing I most want to know (and that most often gets left out) is: who is this product for?
This seems like a simple question, but there are many ways the answer can be of insufficient depth. Thread 👇
1) Audience of "you"
A common pitch pattern involves walking "you"—the viewer—through a product demo ("you land on the website. You click Login... You go to the dashboard...")
This is great for seeing how the product works, but doesn't tell you at all who the audience is!
"You" are not audience, and the actions "you" take in this demo are what the product creator wants a user to take, not a guarantee of how they will actually use it!
Always ask: "So who are you imagining using your product this way? Why would they?"
2) Ambiguous "people."
Sometimes, a narrative can seem at first glance very people-oriented when there's phrases tossed around like "everyone wishes they could..." or "People really really want Y."
But who are these "people?" Bird-dog until you get to clarity.
3) A persona but not a problem.
Perhaps you hear that the target audience is "Betty," a high-school student who wears cardigans and avoids confrontation. Everyone smiles and nods because personas are great, and we go checkity-check on the "define audience" box.
Not so fast!
Just because we can imagine the protagonist doesn't mean we understand how this product should fit into her life. What problem does she have that this product is a solution for? When, specifically, is she going to turn to this product? What's going through her mind?
4) A person, a problem, but not a realistic picture of today.
Say your target user is Jack, who loves competitive video games, and your product is an exciting new multi-player arena battle game. Should be perfect PMF, right?
Well, what's Jack already playing? Fortnite? Lol? And who is he playin with? Assuming this existing reality, how do you imagine your product slotting into Jack's video game habits?
At the end of the day, "If you build it, they will come," is a lie.
Make it crystal clear what kind of person you believe will love your product. Who they are? What do they want? What are they currently doing?
Then, envision how your product would fit into their lives. When would they use it? What mindset would they be in? Why would they reach for your product rather than the status quo?
This story, told well, is what sells concepts--not mocks or prototypes.
• • •
Missing some Tweet in this thread? You can try to
force a refresh
Do you ever get called upon to give design or product feedback?
A guide below 👇
Step 1: Recap for the feedback receiver your take on...
a) what problem this project is solving for users
b) who the primary users are
c) what success for the project is
Get aligned on this before giving any feedback, otherwise you might speak past each other.
Step 2: Put yourself in the shoes of someone who is the primary user, and go through the flow step-by-step.
Wear your user hat right now, not your 'company employee' hat, and don't just focus on key screens. Experience the actual end-to-end experience.
Okay, serious question: what net results in greater efficiency for everyone when A asks B for a favor via e-mail.
1) B declines by not responding. 2) B declines through e-mail response with why they are declining. 3) B declines but it's just a simple "no" with no explanation.
I used to think 2 (because I prefer to get a definitive response as A and it's a nice human touch to know why from B). 2 and 3 also saves A from not having to reping if it's actually a favor A cares about.
On the flip side, there are situations where A asks for a favor but wouldn't reping, and getting 2 or 3 can feel worse than not hearing back. And as B it's effort to craft a decline e-mail, especially with a response, and particularly if saying no is hard for them.
Ask people all the time for feedback. Make your asks specific, and your tone curious so it's safe for the other person to tell something critical. People know when you're just fishing for compliments. Examples (thread)
After a presentation you gave: "How well did you think my points landed? What would have made them clearer?"
After an analysis you completed: "How impactful was this to your team? What would have made it more useful?"
How to describe your design work in a portfolio or presentation (thread below)
Describe the problem you set out to solve.
Explain the things that made this problem interesting or challenging—what was the space of options? What were the constraints you were forced to balance?