Your goal: take one question from a blank page to a scoped MVP with a metric and a risk,
change the plan calmly when a constraint breaks it, and make a call when your metric and your
guardrail disagree.
How this works (about 30 minutes)
- You're a PM at Meta. Ben asks one question and goes deep on it. Ask him what you need (the
goal, the team, the scope); 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 up, a guardrail down:
ship, hold or change?), then "what do we build first".
- If you want to sketch the MVP or jot options, 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 one user with one pain before any solution
- Three solutions that differ in kind, not three versions of one app
- A clear pick with the criteria and what you gave up, why Meta is the one to build it now, and
a first version with a cut line
- A metric tied to the goal, with a guardrail beside it, and a risk with who it hurts
- A new plan, in the open, when a feature you needed disappears, 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: Solutions and MVP first.
- Say what you are not building, and why, out loud.