Who This Helps
This is for Product Managers who see a metric drop and need to move from 'What happened?' to 'What do we do?' fast. It uses the core idea from the Metrics & Dashboards Basics course: building a system you trust for calm decisions.
Mini Case
Maya's team saw their core activation rate dip from 42% to 38% last week. The Slack channel lit up with theories—was it the new signup flow? A holiday weekend? She pulled the team into a 30-minute huddle, not to brainstorm guesses, but to diagnose using their weekly scoreboard.
Do This Now (5 Steps)
- Pause the panic. One number moving is a signal, not the full story. Take a breath.
- Open your weekly scoreboard. This is your single source of truth, as outlined in the course. It should have your North Star and its 3-5 supporting metrics.
- Check the guardrails. Look at the metrics around your main KPI. Did user signups also drop? Or did support tickets spike? This tells you if the problem is isolated or systemic.
- Look one level deeper. If a supporting metric changed, drill into its components. For example, if 'Feature A usage' is down, check if it's down for all user segments or just new users.
- Form your one-sentence hypothesis. Based on the connected movements, state the likely root cause. 'The dip seems linked to a 15% drop in new user signups, not a product issue.'
Avoid These Traps
- Chasing every number. You track 20 things, but only a few matter right now. Focus on the metric tree from your dashboard layout.
- Starting with 'Why?' Start with 'What else moved?' The correlations point you to the right 'why.'
- Endless debate. Set a 30-minute timer for the diagnosis session. If you need more data, assign one person to get it—don't stall the whole team.
- Ignoring your own guardrails. You set up supporting metrics for a reason. Use them. It's like having a smoke alarm and then ignoring the beep.
Your Win by Friday
By Friday, you won't just have a theory about last week's drop. You'll have a clear, evidence-informed action. Maybe it's a small tweak to an onboarding email, or maybe it's confirming the issue was a one-off blip. You'll have turned a worrying question into a measurable decision for your next sprint. That's a calm, confident product manager move.