Who This Helps
This is for junior analysts who need to move from spotting a problem to explaining it. If your boss asks 'why did this drop?' and you want a solid answer, this method from the Board Finance & Runway Narrative course is for you. It turns panic into a plan.
Mini Case
Your weekly report shows a 15% drop in user activation rate. The team is pointing fingers at the new feature, the marketing campaign, and even 'seasonality.' You have 45 minutes before the stand-up. Using the Runway Trigger Tree method, you map it out: a 40% increase in sign-ups from a new channel (good!), but those users have a 50% lower activation rate (the root cause). You just turned a confusing drop into a clear channel-quality issue. High five!
Do This Now (5 Steps)
- Grab the one metric. Don't get lost in ten charts. Pick the single KPI that dropped, like 'activation rate' or 'average order value.'
- Write the drop at the top. Put it on a whiteboard or doc. For example: 'Activation rate down 15% week-over-week.'
- Branch out with 'Why?' Ask 'why' three times. Why down? Lower completion of step two. Why lower? New user segment is struggling. Why? The onboarding isn't clear for them.
- Add numbers to each branch. Don't use 'some' or 'a few.' Use 'Segment A makes up 70% of new traffic but has a 22% completion rate.'
- Pick the heaviest branch. The branch with the biggest number impact is your most likely root cause. That's what you report and act on.
Avoid These Traps
- Chasing ghosts. Don't start analyzing other metrics until you've fully mapped the main one. Stay focused.
- Skipping the numbers. 'A bit lower' isn't analysis. Always attach a percentage, count, or ratio to each idea.
- Blaming one thing. The trigger tree shows multiple possible causes. Your job is to find the primary one, not the only one.
- Forgetting the 'so what?' After finding the cause, state the next action. Is it a bug fix, a copy change, or pausing a campaign?
Your Win by Friday
By using this Runway Trigger Tree approach from the Board Finance & Runway Narrative course, you'll ship a clean diagnosis. Instead of a messy email with maybes, you'll provide a one-pager that says: 'Here’s the drop, here’s the primary cause (with data), and here’s my recommended fix.' You'll move the conversation from 'what happened?' to 'what's next?' That's how you build trust and show leadership, one clear analysis at a time.