Diagnose a KPI Drop: Junior Analyst Fix in 1 Session

Who This Helps

This is for you, Junior Analyst. You see a number drop and your brain goes, "Uh oh." Maybe revenue dipped 12% this week. Or user signups flatlined. You need to find the real reason fast and tell your team what to do about it. No panic. No guesswork. Just a clean diagnosis.

This guide is part of the Founder Finance Basics Mission Pack, where you learn to turn messy data into calm decisions. Today, we focus on one mission: diagnosing a KPI drop.

Mini Case

Imagine you work for a SaaS startup. Last month, new user signups dropped 15% overnight. The CEO is worried. Your job: find out why.

You pull the data. You see that traffic from a key ad channel fell 30%. But wait—conversion rate from that channel stayed the same. So the problem is not the website. It's the ad spend. You check the budget: the marketing team paused that channel 7 days ago to test a new one. That's your root cause.

Now you can recommend: restart the old channel or double down on the new one with a small test budget.

Do This Now (5 Steps)

1. Grab the raw numbers. Pull the KPI for the last 30 days. Look for the exact day it dropped. Write that date down.

1. Segment by source. Break the KPI into pieces: by channel, by region, by customer type. Which piece changed? In our case, it was one ad channel.

1. Check the conversion funnel. Did fewer people show up? Or did fewer people convert once they arrived? This tells you where the leak is.

1. Ask one question to a teammate. Ping the person who owns that piece. "Hey, did anything change on [date]?" They might say, "Oh yeah, we paused that campaign." Instant answer.

1. Write a one-paragraph summary. State the root cause, the impact (15% drop), and one clear recommendation. That's your analysis. Ship it.

Avoid These Traps

• Blame the data first. Before you blame a bug or a bad report, check if a human changed something. Humans cause most KPI drops.
• Over-analyze. You don't need a 10-page report. One paragraph with a number and a recommendation is enough.
• Ignore the easy answer. Sometimes the drop is just a holiday or a weekend. Check the calendar before you dig deeper.
• Forget to ask. A quick chat with a teammate can save you hours of analysis.

Your Win by Friday

By Friday, you will have diagnosed one KPI drop in under 2 hours. You'll know the root cause (like a paused ad channel) and you'll have a clear recommendation (restart the channel or test a new one). Your team will see you as the person who finds answers fast. That's a win.

And hey, you might even get a high-five from the CEO. Not bad for a week's work.