Who This Helps
You're a Product Manager staring at a dashboard that just turned red. Conversions dropped 12% overnight. Your team is panicking. Stakeholders want answers. You need a calm, structured way to turn that product question into a measurable decision—without wasting a week.
This approach comes straight from the Product Portfolio Strategy course, where we teach leaders how to size bets and sequence work. One of the missions, "Kill Criteria," shows you how to spot when a bet isn't working. Same logic applies to diagnosing a KPI drop: you need clear guardrails to know what's worth investigating.
Mini Case
Meet Priya, a PM at a subscription app. Her weekly active users dropped 8% in three days. She could have blamed the latest release, a competitor move, or a seasonal dip. Instead, she ran a one-hour diagnosis session. She found the root cause: a broken onboarding step that affected 40% of new sign-ups. Fixing it took two days. Users bounced back to normal within a week. The lesson? A focused session beats a week of guessing.
Do This Now (5 Steps)
- Grab your KPI data for the last 30 days. Look for the exact moment the drop started. Was it a specific hour, day, or release?
- List every change your team made in that window. Feature launches, bug fixes, marketing campaigns, pricing updates. Write them down. No judgment yet.
- Pick the top three suspects. Which changes overlap with the drop? Rank them by likelihood and impact. This is your shortlist.
- Run one quick test per suspect. For example, check if the drop only affects mobile users. Or new vs. returning users. Use your analytics tool—no code needed.
- Decide on one fix. Once you find the culprit, assign one person to fix it. Set a deadline. Track the KPI for three days after. You'll know if it worked.
Avoid These Traps
- Chasing every theory. You'll burn out. Stick to your top three suspects.
- Blinding the team with data. Share the one chart that matters. Keep it simple.
- Fixing everything at once. Pick one root cause. Fix it. Measure. Repeat.
- Ignoring the "no change" scenario. Sometimes the drop is external (a competitor launched a sale). Don't over-engineer a response.
- Forgetting to check your data source. A tracking bug can look like a KPI drop. Verify before you panic.
Your Win by Friday
By Friday, you'll have one root cause identified and one fix in progress. Your team will know exactly what to do next. Stakeholders will see a clear plan. And you'll have turned a scary dashboard into a simple decision. That's the power of a focused diagnosis session.
And hey, if the fix works, you can celebrate with a coffee. If it doesn't, you'll know what to try next. No drama, just progress.