Who This Helps
This is for junior analysts who need to diagnose a sudden KPI drop and deliver a clear, board-ready recommendation. You don't have hours to dig through dashboards. You need one focused session to find the root cause and ship a clean analysis. The Board Finance & Runway Narrative course teaches you how to build that narrative with scenarios and triggers.
Mini Case
Imagine you're Viktor, a junior analyst at a growth-stage startup. Your CEO just saw a 12% drop in monthly recurring revenue (MRR) in the last 7 days. The board wants a root cause analysis by Friday. You have one hour to diagnose the drop and recommend a fix. In the Board Finance & Runway Narrative course, Viktor's first mission is to define the single board-level signal for this cycle. That signal is your starting point.
Do This Now (5 Steps)
- Grab the one signal. Open your dashboard and find the single metric that matters most to the board. For Viktor, it's MRR. Don't get distracted by vanity metrics.
- Slice by segment. Break MRR into customer cohorts, product lines, or regions. Look for the segment that dropped the most. In our case, the 12% drop came from a 20% drop in the enterprise segment.
- Check the trigger tree. Use a trigger tree to list possible causes: churn, downgrades, failed payments, or new customer slowdown. For enterprise, you find a 30% increase in churn from one customer group.
- Interview the data. Ask one question: what changed 7 days ago? You discover a pricing change for that group. That's your root cause.
- Write the recommendation. State the root cause clearly: pricing change caused 12% MRR drop. Recommend rolling back the change for that segment and monitoring for 3 days.
Avoid These Traps
- Don't chase every data point. Stick to the one signal.
- Don't blame the data. Blame the process that changed.
- Don't write a novel. One page memo, three bullet recommendations.
- Don't forget the timeline. Board wants action, not history.
- Don't ignore the human. The team that made the pricing change needs to know.
- Don't skip the scenario. What if the drop continues? Have a backup plan.
- Don't use jargon. Say "churn" not "customer attrition rate."
- Don't overcomplicate. Root cause is usually one thing.
Your Win by Friday
By Friday, you'll have a one-page board finance memo with a clear root cause and three actionable recommendations. You'll look like the analyst who saved the board meeting. And you'll have a repeatable process for the next KPI drop. Plus, you'll finally understand why Viktor's first mission is so important. (Spoiler: it's the signal that saves the story.)
Now go diagnose that drop. You've got this.