Your goal: define success for a feature from its goal, pick one north star with inputs
and a guardrail, read the numbers when they disagree, and make a call when the fix has a cost.
How this works (about 30 minutes)
- You're a PM at Meta. Ben asks one metrics case and goes deep on it. He has a short fact sheet;
every number on it is made up for the exercise, not Facebook's. Ask what you need; he won't
volunteer.
- A shared notepad is there if you want to sketch your metric tree. Ask Ben to open it, and
tell him when you've written something.
- Lots of follow-ups, one curveball (numbers that disagree), then a trade-off turn on your fix:
ship, hold or change?
- No hints and no scores during the call. Your report comes after.
What scores well
- A goal before any metric, why Meta built the bell, and a user action that proves the goal
- One north star tied to the goal, a few inputs, and a guardrail with a threshold
- Saying which metrics are vanity, and why
- Reading numbers that disagree: split them until the story is clear
- A call you would defend, with who pays for it and what would change your mind
- Answers that say where they are going and land in a minute or two
Tips
- Take PM Coach · Metrics first.
- Say the goal in one sentence before you name a single metric.