Who This Helps
Junior analysts who need to stop guessing and start diagnosing KPI drops fast. You're the one who gets asked "why did revenue dip?" and you want an answer that sticks. The Board Finance & Runway Narrative course gives you a structured way to find the real culprit without drowning in data.
Mini Case
Imagine you see a 12% drop in monthly recurring revenue. Your instinct is to blame churn. But after running a quick trigger tree from the course, you discover the real issue: a 7-day delay in payment processing due to a new gateway. The fix? Switch back to the old provider. Within two weeks, revenue recovers. That's the power of a focused diagnosis.
Do This Now (5 Steps)
- Pick one KPI that dropped (like revenue, sign-ups, or retention). Don't chase three at once.
- List three possible causes (churn, pricing, technical issue). Write them down.
- Check the data for each cause in order of likelihood. Start with the easiest to verify.
- Use a trigger tree from the Runway Trigger Tree mission in the course. It helps you branch out systematically.
- Write one recommendation based on what you found. Keep it short: "Switch payment gateway" or "Fix onboarding email."
Avoid These Traps
- Fixing symptoms, not root cause. A 12% drop might look like churn, but it's actually a billing error.
- Overcomplicating the analysis. Three charts are better than ten. Focus on the one metric that matters.
- Skipping the recommendation. Your boss wants a decision, not a data dump. Always end with a clear action.
- Blame culture. Don't point fingers at teams. Frame it as a process issue, not a people problem.
- Ignoring time frames. A 7-day delay is different from a 30-day trend. Check the window.
- Not validating assumptions. If you think it's churn, talk to the customer success team first.
- Forgetting to document your steps. You'll need to explain your logic later.
- Panicking. A KPI drop is normal. The goal is to learn and adjust.
Your Win by Friday
By Friday, you'll have a one-page memo that shows the root cause of the KPI drop, the data you used, and your top recommendation. Your manager will see you as the analyst who doesn't just report numbers but solves problems. And you'll feel like a detective who cracked the case (minus the trench coat).