Who This Helps
You are a Junior Analyst who just saw a key number drop. Maybe it's 12% fewer conversions this week. Your boss wants answers by Friday. This guide uses the Board Finance & Runway Narrative course to help you diagnose fast and recommend smart next steps.
Mini Case
Imagine you track monthly active users. Last month they dropped 12%. No obvious reason. You have 7 days to explain why and what to do. In the course, Viktor faces a similar problem: he must define the single board-level signal for this cycle. You can borrow his method.
Do This Now (5 Steps)
- Name the exact metric and time frame. Write down: "MAU dropped 12% in the last 30 days." Be specific.
- List three possible causes. For example: bug in signup flow, seasonal dip, competitor launch. Don't guess yet.
- Check the data for each cause. Look at signup funnel steps. Compare week-over-week. If you see a 7-day lag in activation, that's a clue.
- Pick the most likely root cause. Choose one. For Viktor, it's about defining a trigger. Your trigger is the data point that explains the drop.
- Write one clear recommendation. Example: "Fix the signup button bug by Wednesday. Expect recovery in 3 days." Keep it short.
Avoid These Traps
- Blame everything. Don't list 10 causes. Pick one.
- Skip the numbers. Without 12% and 7 days, your analysis is fuzzy.
- Forget the recommendation. Analysis without action is just noise.
- Wait for perfect data. Use what you have now. You can refine later.
- Ignore the board view. Your boss needs a story, not a spreadsheet.
Your Win by Friday
You ship a one-page memo: root cause = signup bug, impact = 12% drop, fix = deploy patch in 3 days. Your boss nods and says "good work." That's the win. And hey, you just used a board-level method without a board meeting.