Who This Helps
You're a Junior Analyst who just saw a key number drop. Maybe it's 12% fewer signups this week. Your boss wants answers by Friday. This guide uses the Strategy Basics: Competitive Map approach to help you find the real cause fast.
Mini Case
Imagine you track weekly active users. Last month they were steady at 10,000. This week they're 8,800. Panic? Not yet. One analyst used the Market Signal Brief mission to spot that a competitor launched a free tier. That single signal explained 70% of the drop. No wild guesses. Just one clear root cause.
Do This Now (5 Steps)
- Pull the raw numbers – Get the last 30 days of data for your KPI. Don't filter anything yet.
- Check for data errors – A tracking bug can fake a drop. Look for sudden flatlines or missing days.
- Segment by user type – Split the drop by new vs returning users. If new users fell 80%, focus there.
- Look for external signals – Use the Competitor Set mission to list three rivals. Did any change pricing or launch a feature?
- Write one recommendation – Based on your finding, suggest one action. Example: "Add a free trial to match Competitor X."
Avoid These Traps
- Blame the data first – Always verify your source before hunting causes.
- Chase every theory – Pick the top suspect and test it. You don't have time for five rabbit holes.
- Skip the competitor check – A KPI drop often has a market reason. Ignoring it wastes days.
- Recommend without evidence – A guess dressed as a recommendation gets ignored. Back it with numbers.
- Forget the timeline – If the drop started Tuesday, look at events from Monday. Timing is everything.
Your Win by Friday
By Friday, you'll have a one-page analysis with: the root cause (like a competitor move or a bug), the impact size (12% drop, 7 days), and one clear recommendation. Your boss will say "Good work." And you'll feel like a detective who cracked the case. Plus, you'll have a reusable method for next time. That's a win.