How to build a metric tree during a product manager interview
Most interview metric trees are topic lists with indentation. A real one decomposes arithmetically and bottoms out in things a team can actually change.
PMMockr.com
Quick Answer
Pick a top metric, decompose it into factors that multiply or add to it, and keep going until each leaf is something a specific team could move next quarter. If your branches do not recombine into the parent, you have drawn a mind map and called it a tree.
The multiplication test
Revenue equals users times conversion times average order value times purchase frequency. That is a tree, because the arithmetic closes. "Revenue: acquisition, engagement, brand" is not, because no operation turns those three into revenue. Every time you add a branch, say the operator out loud. If you cannot, you are listing themes.
Stop at the actionable layer
A tree that bottoms out at "conversion rate" has not helped anyone. Push one more level until you hit something with an owner.
- Not "checkout conversion" but "share of carts that hit a payment error".
- Not "engagement" but "share of new users who complete the first import in week one".
- Not "retention" but "share of accounts with a second seat invited by day fourteen".
Prune out loud
The tree is a search tool, not a deliverable. Build two levels, then say which branch you are walking down and why the others are smaller. "Frequency is the biggest branch here because AOV is capped by the catalogue, so I am going down frequency." Interviewers score the pruning more than the drawing, and a candidate who expands every branch evenly has not made a decision.
Practice question
Ten minutes: "As a PM for Lyft, what dashboard would you build to track app health?" Build the tree first and let the dashboard fall out of it. Say the operator at every branch, and prune to one path before you finish.
Turn this into reps
Run a metrics case on PMMockr, then redraw your tree from the transcript. Any branch you cannot join to its parent with an arithmetic operation is a branch that cost you points.
FAQ
How deep should the tree go in an interview?
Two levels wide, then one branch deep. Depth on the branch you chose beats symmetry across branches you are not going to use.
Should I draw it if the interview is remote?
Narrate the structure instead of fighting a whiteboard tool. "Top level splits four ways, I am expanding the second one" is easy to follow without a picture.
What if the interviewer disagrees with my top metric?
Take the correction and rebuild from theirs. The tree skill transfers; arguing about the root wastes the half of the interview where you could have shown it.