Who This Helps
This is for team leads who see a KPI drop and need a clear, repeatable way to find the root cause with their team. It uses the Strategy Basics: Competitive Map course to turn a messy investigation into a structured routine.
Mini Case
Your weekly active users dropped 15% last month. The team is pointing fingers at five different features and three competitors. You spend two meetings debating, but no one agrees on the primary cause. Sound familiar? A competitive map session cuts through the noise.
Do This Now (5 Steps)
- Block 90 minutes with your core analysts for a 'diagnosis session' this week.
- Frame the problem: 'Our weekly actives dropped 15%. Is this a market shift or a competitor move?'
- Build a quick competitor set. Don't list every logo—focus on the 2-3 rivals your users actually compare you to.
- Map your differentiation grid. For each competitor, list one clear area where you win and one where you lose, based on recent user feedback.
- Vote on the single most likely 'market signal' causing the drop. This becomes your strategic artifact for the week.
Avoid These Traps
- Don't let the session become a feature wishlist. Stick to evidence of what changed in the market.
- Avoid choosing every competitor. Aisha's problem in the course is picking the right set, not a long list. More than three dilutes your focus.
- Don't skip the 'segment wedge'. If the drop is in one user group, focus there. Trying to solve for everyone means solving for no one.
- Don't debate without data. Use real numbers from the last 30 days, not gut feelings.
- Don't end without one clear hypothesis. The goal is a single, testable statement.
Your Win by Friday
By Friday, you'll have a one-page strategic artifact—your competitive map—that shows the probable cause of the KPI drop. You'll have a focused action for next week, and your team will have a new routine for the next time numbers wobble. No more panic meetings, just a clear path forward. You've got this.