Diagnose a KPI Drop: Junior Analyst Rescue Plan

Who This Helps

You're a Junior Analyst who just saw a KPI drop and your manager wants answers by Friday. This guide helps you pinpoint the root cause fast and ship a clean analysis with clear recommendations. It's built from the Founder Finance Basics Mission Pack, specifically the Unit Economics Snapshot mission.

Mini Case

Imagine your startup's weekly active users dropped 12% last week. Revenue stayed flat, but your CEO is worried. You dig into the data and find that new user sign-ups fell 20% while existing user activity held steady. The drop is in acquisition, not retention. Using the Unit Economics Snapshot mission, you map the funnel and see the problem: a pricing page change caused a 7-day conversion lag. You recommend rolling back the change and testing a simpler version.

Do This Now (5 Steps)

1. Isolate the metric. Pick one KPI that dropped—like weekly active users or revenue per user. Don't chase three at once.
2. Check the date range. Compare the drop period to the same period last week or month. A 12% drop over 3 days is different from 12% over 30 days.
3. Segment the data. Break the KPI by channel, user type, or region. In our case, new users vs. returning users showed the real story.
4. Find the trigger. Look for a change in the product, marketing, or pricing that happened right before the drop. The pricing page change was the culprit.
5. Write one recommendation. Don't list five options. Pick the most likely fix and explain why. "Roll back the pricing page change" is clear and actionable.

Avoid These Traps

• Don't blame a single event without data. A server outage might not cause a 12% drop if it lasted 10 minutes.
• Don't ignore seasonality. A drop on a holiday weekend might be normal. Check last year's data.
• Don't overcomplicate the analysis. Three charts are better than ten. Focus on the one chart that shows the root cause.
• Don't forget to ask a teammate. Sometimes a quick chat with the product manager reveals the pricing change you missed.

Your Win by Friday

By Friday, you'll have a one-page analysis that shows the root cause (pricing page change), the impact (12% drop in new users), and your recommendation (roll back and test a simpler version). Your manager will see you as the analyst who ships clean work with clear next steps. Plus, you'll have saved the team from guessing—and that feels pretty good.