Your goal: find one specific user and their worst moment, defend the choice against the
others, show a design that fixes that pain and nothing else, and make a call when a win for your
user costs someone else.
How this works (about 30 minutes)
- You're a PM at Meta. Ben asks one design question and goes deep on it. Ask him what you want
to know about the users, the goal and the team. He hands over what he has, one line at a time,
and won't volunteer. The details are made up for the exercise.
- Lots of follow-ups, one curveball, then a trade-off turn: your metric rises while something
else falls. Ship, hold or change?
- If you want to sketch a journey or jot, say "can I use the notepad?" and Ben puts it up.
- No hints and no scores during the call. Your report comes after.
What scores well
- A goal and a scope before any segments
- Segments that are not just "busy people": real situations, one picked with criteria
- Why Meta, why now: what it already has that makes this its problem to solve
- One real person in one real week, and the moment it hurts, found rather than recited
- A pain separated from its symptom, ranked against two others, with who you are not building for
- A design that fixes that pain, a plan you change when the facts change, and a call when the
numbers disagree
- Answers that say where they are going and land in a minute or two
Tips
- Take PM Coach · Design: Users and Pain first.
- Ask Ben for the research: "what do we know about these people?"