Framework de entrevista PM
Root Cause Analysis (Issue Tree + 5 Whys)
Execution / analytical / debugging questions
Cuándo usarlo
Any 'metric X dropped / spiked', incident review, or 'why is the funnel broken'.
La cheat sheet de Root Cause Analysis (Issue Tree + 5 Whys)
- 1
State the problem precisely
What changed, when, by how much, for whom?
- 2
Segment
Internal vs external, geo, platform, user cohort, funnel step.
- 3
Build a MECE issue tree
Top-level branches must be mutually exclusive and collectively exhaustive.
- 4
Ask 5 Whys down each live branch
Drill until you hit a testable hypothesis.
- 5
Prioritize and test
Pick the highest-impact hypothesis; propose the test to confirm it.
| Paso | Significado | La acción |
|---|---|---|
| 1 | State the problem precisely | What changed, when, by how much, for whom? |
| 2 | Segment | Internal vs external, geo, platform, user cohort, funnel step. |
| 3 | Build a MECE issue tree | Top-level branches must be mutually exclusive and collectively exhaustive. |
| 4 | Ask 5 Whys down each live branch | Drill until you hit a testable hypothesis. |
| 5 | Prioritize and test | Pick the highest-impact hypothesis; propose the test to confirm it. |
Top trampas de Root Cause Analysis (Issue Tree + 5 Whys)
Son los pasos que convierten un framework sólido en una respuesta plana.
Guessing the cause before segmenting.
Overlapping branches (e.g., 'iOS users' vs 'paid users' — users can be both).
No concrete test at the end.
Pruébalo en este prompt
“Notifications open-rate dropped 8% week-over-week. Debug it.”