Who This Helps
This is for you, Junior Analyst. You just saw a KPI drop and your manager wants answers by Friday. No panic. The Strategy Basics: Competitive Map course gives you a repeatable way to find the real cause and recommend a fix.
Mini Case
Imagine you track weekly active users. Last week they dropped 12%. Your first instinct is to blame the latest product update. But when you map competitors, you notice a rival launched a free feature that same week. That 12% drop? 8% came from users who switched. Now you have a clear root cause and a recommendation: respond with a retention campaign.
Do This Now (5 Steps)
- Pull the KPI data for the last 30 days. Look for the exact day the drop started.
- List three possible causes. Don't overthink. Write down product bug, competitor move, seasonality.
- Check your competitor set. Use the Competitor Set mission from the course. Are any rivals making noise?
- Interview two users who churned. Ask one question: "What changed for you last week?"
- Write one recommendation. Keep it short. Example: "Launch a 7-day retention email series for users who tried the rival feature."
Avoid These Traps
- Don't blame the first thing you see. The drop might not be your product. Look at market signals first.
- Don't analyze alone. Share your hypothesis with a teammate. Fresh eyes catch blind spots.
- Don't write a 10-page report. One page with the root cause and one recommendation is enough.
- Don't ignore small data. A 2% drop in one segment can be a leading indicator.
Your Win by Friday
By Friday, you will have a one-page analysis with a clear root cause and a recommendation your manager can act on. You will feel confident because you used a structured method from the Strategy Basics: Competitive Map course. And hey, you might even get a "nice work" in the team standup.