Diagnose a KPI Drop with a Runway Trigger Tree

Who This Helps

This is for team leads who see a sudden dip in a critical number and need to move from panic to a clear plan. It pulls a key tool from the Board Finance & Runway Narrative course to make your diagnosis sharp and repeatable.

Mini Case

Your team's weekly active user growth drops from 8% to 2% for two weeks straight. The immediate guess is a new competitor feature. But after a quick 45-minute session using the steps below, you trace it back to a recent pricing page update that accidentally increased load time by 3 seconds. You fix the page, and growth returns to 7% the following week. No more blame games.

Do This Now (5 Steps)

1. Call a 60-minute huddle. Invite only the three people closest to the data and the process. No spectators.
2. Write the problem plainly. Put "Weekly Growth: 8% → 2%" on a whiteboard. That's your only focus.
3. Build your trigger tree. This is the core move from the Runway Trigger Tree mission. Draw three main branches: User Acquisition, User Engagement, and Platform Performance.
4. Ask 'What changed?' on each branch. For Acquisition, was there a campaign shift? For Engagement, did a core feature break? For Performance, did load times creep up? Assign one person to check each branch with real data.
5. Vote on the most likely root. After 30 minutes of digging, have each person name their top suspect. The winner gets a clear action owner and a 24-hour check-in.

Avoid These Traps

• Don't let the meeting become a general performance review. Stick to the one KPI drop.
• Don't start with solutions. You must diagnose first. Solutions come after.
• Avoid vague answers like "market conditions." Demand specific, internal changes you can actually measure.
• Don't skip documenting the suspected cause and the verification plan. What gets written down gets done.
• Resist the urge to add more than five people. Too many cooks spoil the diagnosis.

Your Win by Friday

By using this focused routine, you'll stop the weekly 'what happened?' meetings. You'll have a clear, one-page note (like the board finance memo from the course) that states the KPI, the diagnosed root cause, and the action taken. Your team will spend its energy on building, not on endless forensic analysis. You'll look like the calm captain who knows how to steer through rough data.