Who This Helps
This is for you if you're staring at a red arrow on your dashboard and need to know why before your next check-in. The method comes straight from the Board Finance & Runway Narrative course, designed to move you from panic to plan.
Mini Case
Your team's user activation rate dropped from 65% to 58% last week. That's a 7-point dip. The gut reaction is to blame the new feature launch. But by building a quick trigger tree, you trace it back to a specific onboarding email that failed for 30% of new sign-ups—a server issue you can fix in an afternoon. Crisis averted.
Do This Now (5 Steps)
- Grab the one metric. Don't get lost in ten charts. Pick the single KPI that dropped. Write it down.
- Ask 'Why?' three times. For the KPI drop, ask 'Why did this happen?' Write the first answer. Then ask 'Why?' again for that answer. Do it one more time. You'll dig past surface symptoms.
- Map the branches. Turn your 'why' answers into a simple tree on a whiteboard or doc. This is your trigger tree, just like the Runway Trigger Tree mission in the course.
- Find the numbers. For each branch, attach one data point. Is it a 12% increase in load time? A 15% drop from one user segment? No numbers, no proof.
- Pick the fixable root. Circle the one branch you can actually do something about this week. That's your target.
Avoid These Traps
- Chasing ghosts. Don't start with 'maybe it's the economy.' Start with what changed in your system last week.
- Analysis paralysis. Give yourself 45 minutes for steps 1-4, max. The goal is a good enough answer to act on, not a PhD thesis.
- Skipping the 'so what?' Every root cause needs a clear next step. If you can't write the action, you haven't finished diagnosing.
- Forgetting your board memo. The course mission is to build a one-page finance memo. Think: could your diagnosis fit there? It keeps you focused on what matters to leadership.
Your Win by Friday
By Friday, you'll have one diagnosed KPI drop, a simple tree showing the 'why,' and one clear action to take next week. You'll walk into your team sync with a hypothesis and a plan, not just a problem. That’s how you stop being a data reporter and start being a decision-maker. You've got this.