Diagnose a KPI Drop: Junior Analyst Root Cause Fix

Who This Helps

You're a junior analyst who just saw a key number drop. Maybe it's conversion, maybe it's retention. Your boss wants answers, not excuses. This guide, built from the Board Finance & Runway Narrative course, helps you diagnose the root cause in one focused session. No fluff, just a clear path to a recommendation.

Mini Case

Imagine you run a monthly report for a SaaS company. Last month, new sign-ups dropped 12%. Your CEO sees the number and asks, "Why?" You have 7 days to deliver a clean analysis with a clear recommendation. Using the course's Runway Trigger Tree mission, you can trace the drop to a specific channel or behavior. In this case, you find that a pricing page change caused a 30% increase in drop-off. Your fix: revert the change and test a new version.

Do This Now (5 Steps)

1. Grab the data – Pull the last 3 months of the metric. Compare week over week. Look for the exact day the drop started.
2. Segment the drop – Break it down by channel, region, or user type. The 12% drop might be 20% in one segment and flat in others.
3. Trace the trigger – Use the Runway Trigger Tree approach. Ask: What changed right before the drop? A new feature? A pricing update? A marketing campaign end?
4. Test one hypothesis – Pick the most likely cause. For example, check if the pricing page load time increased. If yes, that's your root cause.
5. Write your recommendation – State the cause, the impact (12% drop), and one clear action. Keep it to 3 sentences. Your boss will love it.

Avoid These Traps

• Don't overcomplicate – You don't need a 10-page report. One page with a clear cause and fix wins.
• Don't blame data quality – Unless you're sure, assume the data is right. Focus on what changed.
• Don't skip the numbers – Always include the percentage drop and the time frame. Without numbers, it's just a story.
• Don't guess – If you don't know, say "I need to check X." Honesty builds trust.
• Don't forget the fix – A diagnosis without a recommendation is incomplete. Always suggest a next step.
• Don't ignore context – The drop might be seasonal. Check last year's same period.
• Don't work alone – Ask a teammate to review your hypothesis. Fresh eyes catch blind spots.
• Don't delay – Ship your analysis within 3 days. Speed matters more than perfection.

Your Win by Friday

By Friday, you'll have a one-page memo that pinpoints the root cause of the KPI drop. Your boss will see the 12% drop explained, the trigger identified, and a clear fix recommended. You'll feel like a detective who cracked the case. And hey, you might even get a "nice work" in the next standup.