← Back to blog

Junior Analyst · Board Finance & Runway Narrative

Diagnose a KPI Drop with a Runway Trigger Tree

Find the real cause of a metric drop in one session. Stop guessing and start fixing with a clear action plan.

Who This Helps

This is for junior analysts who need to move from just reporting a problem to explaining why it happened. It's a core skill from the Board Finance & Runway Narrative course, where you learn to build a disciplined finance story. Think of it as moving from 'the number is down' to 'here's the root cause and what we should do next.'

Mini Case

Your weekly report shows a 15% drop in new user activation rate. The team is pointing fingers at the new onboarding flow, marketing traffic quality, and even a recent holiday. You have 45 minutes before the stand-up to figure it out. Using the trigger tree method, you segment the data and find the entire drop is from a single traffic source that changed its ad format last Tuesday. The problem isn't your product—it's a specific, fixable marketing channel issue.

Do This Now (5 Steps)

  1. Isolate the Signal: Don't look at the overall KPI. Break it down by your key segments—like traffic source, user cohort, or region—for the last 7 days.
  2. Find the Biggest Delta: Identify which single segment shows the largest negative change. That's your primary suspect.
  3. Check for External Shifts: For that segment, ask: Did anything change in its source? (e.g., a campaign ended, a partner changed their link).
  4. Trace the Timeline: Pinpoint the exact day the drop started. Then, cross-reference with your team's release calendar or external news.
  5. Draft Your One-Liner: Write your finding as: "[KPI] dropped by [X%] because [Segment Y] changed due to [Event Z] on [Date]." This is your root cause.

Avoid These Traps

  • Chasing Every Fluctuation: A 2% daily wobble is noise. Focus on sustained, significant drops (like 10%+ over a week).
  • Starting Without a Hypothesis: Don't just dive into the data. Begin with your best guess (e.g., "I think it's the new feature") and try to prove or disprove it.
  • Mixing Multiple Causes: If you find two issues, diagnose them separately. One clear root cause is better than three maybes.
  • Forgetting the 'So What': A diagnosis without a recommended action is just a fact. Always pair your finding with the next step, like pausing a campaign or rolling back a test.

Your Win by Friday

By Friday, you can walk into your team sync and say: "I diagnosed the activation drop. It's coming from our social media partner 'Channel Alpha.' Their click quality shifted last Tuesday, accounting for 90% of the decline. I recommend we pause that spend and re-test with a new creative." You've just turned a confusing problem into a clear, actionable recommendation. That's the power of a sharp, focused diagnostic session—and it's exactly the kind of disciplined thinking the Board Finance & Runway Narrative course builds. You got this.