Who This Helps
You're a junior analyst who just saw a key metric drop. Your boss wants answers by Friday. This guide uses the Strategy Basics: Competitive Map course to help you pinpoint the root cause and ship a clean analysis with clear recommendations.
Mini Case
Imagine you track weekly active users. Last week, they dropped 12%. Your first instinct is to blame a competitor's new feature. But after a quick Competitive Map session, you discover the real culprit: a pricing change you made 7 days ago confused your core segment. The map saved you from chasing the wrong problem.
Do This Now (5 Steps)
- Pull your KPI data for the last 30 days. Look for the exact day the drop started. Note any internal changes (pricing, feature launch, email campaign) on that day.
- Open your Competitive Map. If you don't have one yet, sketch a simple grid: your product vs. top 2 competitors. List 3 features your customers care about most.
- Check your Customer Segment Wedge. Did you accidentally target a new segment? For example, if you serve small businesses but ran a promotion for enterprise, that mismatch can cause a drop.
- Run a quick Differentiation Grid. Mark where you win and lose. If you lost on price, that's a signal. If you lost on speed, that's another. Focus on the gap that matches your KPI drop.
- Write one recommendation. Based on your map, pick one move: revert the pricing change, improve the feature, or adjust your messaging. Keep it short and specific.
Avoid These Traps
- Blame the competitor first. Most drops come from internal moves, not external threats. Check your own changes before looking outside.
- Overcomplicate the map. You don't need every competitor. Just the top 2 that matter for your segment.
- Ignore the timing. A drop that started 3 days after a price change is likely caused by that change, not a competitor's blog post.
- Skip the segment check. If your promotion targeted the wrong customer type, your map will show it.
- Recommend too many things. One clear action beats a list of maybes.
- Forget to share your evidence. Attach your map or a simple table to your analysis. It makes your recommendation stick.
Your Win by Friday
By Friday, you'll have a one-page analysis with a clear root cause and one recommendation. Your boss will see you moved fast and used a structured method. And hey, you might even get a nod of approval when you say, "I checked the Competitive Map first."