← Back to blog

Junior Analyst · Board Finance & Runway Narrative

Diagnose a KPI Drop: Junior Analyst Runway Fix

Find the root cause of a KPI drop in one focused session. Ship clean analysis with clear recommendations.

Who This Helps

This is for you, the Junior Analyst who just saw a key number drop and needs to figure out why. You want to ship a clean analysis with clear recommendations, not a messy spreadsheet. The Board Finance & Runway Narrative course is built for this exact moment—it helps you turn a scary drop into a confident story.

Mini Case

Imagine you track weekly active users for your product. Last week, the number fell 12% in just 7 days. Your boss wants a root cause by Friday. You have one focused session to get it right. Here's how you do it, using a technique from the Runway Trigger Tree mission in the course.

Do This Now (5 Steps)

  1. Grab the last 4 weeks of data. Pull daily numbers for your KPI. Look for the exact day the drop started. Was it Monday? Wednesday? That's your clue.
  1. Split the data by user segment. New users vs. returning users. Mobile vs. desktop. One segment will show a bigger drop. That's your suspect.
  1. Check one external event. Did you launch a new feature? Did a competitor run a promotion? Did a server go down? Match the timing with your drop day.
  1. Build a simple trigger tree. Write the KPI at the top. Branch into possible causes: technical issue, marketing change, seasonal dip. Pick the branch with the strongest evidence.
  1. Write one recommendation. Based on your trigger tree, say exactly what to do next. Example: "Pause the new onboarding flow until we fix the sign-up error." Keep it short.

Avoid These Traps

  • Don't look at every metric at once. Focus on the one KPI that dropped. Too many numbers will slow you down.
  • Don't blame the data. It's rarely a data bug. Assume the numbers are correct and look for a real cause.
  • Don't wait for perfect proof. You don't need 100% certainty. A strong hypothesis with 3 supporting data points is enough to start.
  • Don't skip the recommendation. Your job is not just to find the drop. It's to say what to do about it.
  • Don't overcomplicate the fix. A simple action (like reverting a change) often works faster than a complex plan.

Your Win by Friday

By Friday, you'll have a one-page analysis that shows the root cause and your recommendation. Your boss will see you as the person who can diagnose problems fast. And honestly, that feels pretty good. You'll be ready for the next board meeting with a clear story—no panic, just facts.