You're here when: A competitor launches something your users are asking about. You feel urgency to react. But you're not sure if responding is the right move for your product.
The Heuristic
Reacting to competitors means playing their game on their terms. The default answer should be: don't respond. Override the default only when real evidence forces it.
- Does this threaten your core use case or a peripheral one? If the competitor move targets the exact thing your best users love about you, pay attention. If it's an adjacent feature, it's noise.
- Are your users actually leaving, or just mentioning it? "Hey, competitor X launched this cool thing" is different from "I'm cancelling because competitor X does this better." Check churn data, not Twitter.
- Can you differentiate rather than match? Feature-matching is a race to the bottom. The better response is usually to go deeper on what makes you different, not to copy what makes them the same.
- Would responding pull you off your current roadmap bet? Every hour spent reacting to a competitor is an hour not spent on your own strategy. If your current bet is right, the cost of reacting is higher than the cost of ignoring.
Decision Tree
Quick Example
When a new team chat product entered a category dominated by an incumbent, the incumbent responded by matching features one by one. The challenger kept deepening the core experience instead. Matching features didn't close the gap because the gap was never about features. It was about the experience.
The Anti-Pattern
The Reactive Roadmap. Every competitor announcement triggers an emergency planning session. The roadmap becomes a mirror of what competitors ship rather than a reflection of what your users need.
This is what it looks like when competitors define your positioning. Once you're reacting to their moves, you've already lost the frame. The companies that win define their own category and let competitors react to them.
Written with ❤️ by a human (still)