Build a disruptive innovation radar for your category
Your category is stable, you are winning, and you cannot see the disruptor coming — which is exactly when one arrives. This builds a radar that scans low-end, new-market, and adjacent-tech disruption vectors every quarter so you spot the threat while it is still cheap to respond.
Why Stable Categories Get Disrupted First
Clayton Christensen's disruptive innovation research — since operationalized across the industry — showed that incumbents rarely lose to better products; they lose to cheaper, simpler, or radically different products they initially dismiss. The Reforge product strategy research notes that the most common mistake in competitive tracking is monitoring only direct competitors at the same price point. By the time a low-end entrant is visible on a traditional competitive grid, they have already captured the price-sensitive half of the market.
How the Build a disruptive innovation radar for your category Prompt Works
The prompt forces quarterly scans across three vectors (low-end, new-market, adjacent-tech) with named signal metrics for each so the radar is not just a diagnostic but a triggered response system. The response menu — ignore/monitor/respond — converts vague threat awareness into specific decisions with trigger thresholds.
When to Use It
- Your category has been stable for 3+ years.
- A new platform primitive (AI model, API) is enabling entrants in adjacent verticals.
- A board member is asking what could kill your product in 5 years.
- You are the market leader and want to stay paranoid.
- An entry-level competitor is growing faster than you expected.
Common Pitfalls
- Monitoring only same-price-point competitors. Disruption starts below you. If your radar only looks sideways, you will see the threat after your buyers have already switched.
- Dismissing "toys". Low-end entrants look primitive on purpose. The question is what "good enough" line they will cross next — not whether they are weaker today.
- No trigger metrics. A radar without response triggers is a quarterly doc that gets ignored. Name the metric that moves a threat from monitor to respond.
Sources
- Why Startups Fail — CB Insights
- The Product Strategy Stack — Reforge
- Andreessen Horowitz AI — Andreessen Horowitz
- First Round Review — First Round
Sources
- Why Startups Fail — CB Insights
- The Product Strategy Stack — Reforge
- Andreessen Horowitz AI — Andreessen Horowitz
- First Round Review — First Round
Prompt details
Ready to try the prompt?
Open the live prompt detail page for the full workflow.