Who This Helps
You are a Junior Analyst who just saw a KPI drop. Maybe revenue per user slipped 12% overnight. Or churn jumped 7 days in a row. Your boss wants a clear root cause and a recommendation by end of day. This guide helps you get there fast, using the approach from the Board Finance & Runway Narrative course.
Mini Case
Imagine you work at a subscription company. Last month, monthly recurring revenue dropped 12%. You dig in and find that the drop came from a single customer segment: small teams on the annual plan. Their usage fell 30% after a product update. Now you have a lead. The course mission "Runway Trigger Tree" shows how to build decision branches from a signal like this.
Do This Now (5 Steps)
- Isolate the drop. Pull the metric by segment, plan, and region. Find the one slice that moved. In our case, it was small teams on annual plans.
- Check the timing. Look at the 7 days before and after the drop. Did a feature ship? Did pricing change? Did support tickets spike? Map events to the timeline.
- Talk to one user. Call a customer from the affected segment. Ask: "What changed for you last week?" One 10-minute call can reveal the real story.
- Build a trigger tree. Draw a simple tree: if usage dropped because of the update, then rollback or fix. If because of pricing, then offer a discount. If because of support, then train the team. The Runway Trigger Tree mission teaches this exact structure.
- Write your recommendation. State the root cause (product update confused users), the impact (12% revenue drop), and one action (rollback the update and re-release with onboarding). Keep it to 3 sentences.
Avoid These Traps
- Don't blame the data. A 12% drop is rarely a data bug. Assume the signal is real until proven otherwise.
- Don't overcomplicate. You don't need a regression model. A simple timeline and one user call often crack the case.
- Don't skip the recommendation. Your job is not just to find the cause, but to ship a fix. Even a simple "rollback and retest" is better than no action.
- Don't ignore the board signal. The course mission "Board Signal Alignment" reminds you to connect your analysis to the one metric the board cares about. For your company, that might be net revenue retention.
Your Win by Friday
By Friday, you will have shipped a clean analysis with a clear recommendation. Your boss will see you as someone who can diagnose a KPI drop in one focused session. And you will have practiced a skill that every analyst needs: turning a scary number into a simple story with a next step. Plus, you will have a new tool in your belt from the Board Finance & Runway Narrative course. Not bad for a week's work.