TechniqueFrameworkProductDecision-making
A metrics question is a structured hunt: north star, guardrails, then the segment
Aakash Gupta · Google Product Manager Metrics Interview: A Worked Mock
The idea
A product interviewer says a number fell and asks why. Aakash Gupta takes the question from clarifying it to a framework to the numbers that matter. The structure is to confirm which metric and over what period, separate the north star from the guardrail metrics it must not be traded against, and then decompose: by platform, by region, by user cohort, by funnel step, until the fall is isolated to a segment that explains it. The skill being tested is not knowing the answer but showing a process that would find it, and saying what you would check first and why.
Clarify the metric, protect the guardrails, then decompose the drop by segment until it is isolated; show the process, not a guess.
When it works
Product management interviews, any analytics role, and any desk conversation that starts with a number going the wrong way.
When it may fail
A framework can become a recitation, and interviewers hear the difference. The structure is a way of thinking out loud; the judgement about which branch to open first is what they are grading.
How to use it
Build the metrics tree in the lab for a product you use. Then practise one drop: pick a branch, say what you would pull first, and what result would make you stop and what would make you go deeper.
Where it came from
Video Google Product Manager Metrics Interview: A Worked Mock · Aakash Gupta
What the source says. Aakash Gupta takes a metrics question from clarifying it, to a framework, to the numbers that matter.
Connected ideas
Puts it to work
Shipping is an output. Nobody is paying for outputsMeasure what changed for the customer, not what was shipped; a team given an outcome behaves differently from one given a list.
Says something similar
Day 2 begins when a company manages to proxies and treats decisions as one-way doorsCheck whether the metric is still the goal or has become the goal, and reserve the heavy process for decisions that cannot be undone.
Concepts
Put it to work on L3VLUP
More like this
- TechniqueProductBook
Ask about what people already did, never about what they would do
Evidence about demand comes from what people have already done and paid for, not from what they say they would do.
From The Mom Test · Rob Fitzpatrick
- Post-mortemFounders and companiesDocumentary
A board that accepts a narrative has stopped doing diligence
A compelling story is a claim to test, and the test for a technology is watching it work.
From The Inventor: Out for Blood in Silicon Valley · 2019
- FrameworkInvestingFilm
A cheap measurable signal beats an expensive intuitive one at scale
The market misprices what is hard to measure, so a consistent cheap signal can beat an expensive expert.
From Moneyball · 2011
- Decision principleDecision-makingBook
A good decision and a good outcome are separate things
Judge a decision by what was knowable when it was made, and keep the outcome in a separate column.
From Thinking in Bets · Annie Duke