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 idea from the Board Finance & Runway Narrative course: defining clear triggers for action.
Mini Case
Your team's weekly active user growth drops from a steady 8% to just 2%. The usual chatter starts: 'Was it the feature launch?' 'Maybe the market changed?' Instead of a week of debates, you run a one-hour root cause session. You map it to a recent decision to slow marketing spend by 15% to extend runway. Now you have a specific, actionable reason, not a vague worry.
Do This Now (5 Steps)
- Grab one number. Pick the single KPI that dropped. Write it down with the old and new values.
- Set a 45-minute meeting. Invite only the 2-3 people closest to that metric. No spectators.
- Draw the timeline. Mark the exact date the drop started. Note every team event, launch, or external change in the 7 days before it.
- Build your 'Trigger Tree.' Ask: 'What specific decision or change could have directly caused this?' Branch out from there. Was it a budget cut? A pricing test? A server hiccup?
- Vote on the most likely root. Have each person silently pick one branch. The winner is your hypothesis to test. The meeting is over. Go test it.
Avoid These Traps
- Chasing five problems at once. You'll solve none. One KPI, one session.
- Letting the discussion become philosophical. Stick to observable events and decisions on your timeline.
- Skipping the silent vote. Talking it out often leads to groupthink. The silent vote surfaces the quiet, often correct, hunch.
- Forgetting to connect it to runway decisions. Like in the course mission 'Runway Trigger Tree,' a KPI drop is often a trigger you pre-defined. Ask: 'Did we slow something down to conserve cash?'
Your Win by Friday
By Friday, you'll have moved your team from 'Why is this happening?' to 'We think it's X, and here's our 3-point test to confirm.' You'll replace anxiety with a clear, small next action. And you might just uncover a hidden assumption, like Viktor did when defining his board-level signals. Now that's a good week's work.