← Back to blog

Junior Analyst · Board Finance & Runway Narrative

Diagnose a KPI Drop Like a Board Analyst

One focused session to find root cause and ship clean recommendations.

Who This Helps

Junior analysts who need to stop guessing and start shipping analysis that actually gets used. If you've ever stared at a KPI drop and felt stuck, this is for you. The Board Finance & Runway Narrative course gives you the exact structure to turn a scary number into a clear story.

Mini Case

Imagine you're Viktor, a junior analyst at a growth-stage company. Last month, your net dollar retention dropped from 112% to 98%. That's a 14-point swing. Your VP wants a root cause by Friday. No pressure. Using the Runway Trigger Tree mission from the course, you can break this down in one focused session.

Do This Now (5 Steps)

  1. Grab the single number that matters. For Viktor, that's the NDR drop. Don't chase three metrics at once.
  2. List all possible causes. Think: churn, downgrades, expansion slowdown. Write them down fast.
  3. Check the easiest data first. Look at your top 10 accounts by revenue. Did any of them downgrade? (Spoiler: two did, for 8% of the drop.)
  4. Build a simple trigger tree. Start with the KPI, then branch into segments. Use the Runway Trigger Tree mission from the course as your template.
  5. Write one recommendation. Example: "Re-engage top 5 accounts with a check-in call this week." That's it. One action, not a list of 10.

Avoid These Traps

  • Don't try to explain everything. A 14-point drop might have one main cause. Find that.
  • Don't wait for perfect data. Use what you have now. You can refine later.
  • Don't write a novel. Your VP wants a one-page memo, not a thesis. The course's Board finance memo (1 page) outcome is your guide.
  • Don't blame the data tool. It's not the tool's fault. It's your story.
  • Don't skip the recommendation. Analysis without action is just noise.
  • Don't overcomplicate the math. Simple percentages and counts work fine.
  • Don't forget to check the timing. Did the drop happen after a price change? That's a clue.
  • Don't work alone. Ask a teammate to sanity-check your trigger tree. Two brains are faster.

Your Win by Friday

By Friday, you'll have a one-page analysis with one root cause and one clear recommendation. Your VP will see you as the analyst who gets to the point. And you'll feel like you actually solved something, not just shuffled numbers. Plus, you'll have a repeatable process for next month's KPI surprise. (Because there's always a next one.)