Purpose
Identify the specific ways a business could be disrupted — across technology, new entrants, regulation, and business model innovation — and rank each threat by likelihood and impact, with the early-warning signals to watch and defensive moves to consider. Replaces vague "what could go wrong" anxiety with a structured threat radar leadership can actually monitor and act on.
When to Use
Invoke this skill when the user asks to:
- Scan an industry for emerging competitive threats or disruption
- Assess how exposed their business is to being disrupted
- Identify near-term vs. long-term threats to their market position
- Pressure-test strategy against new entrants, tech shifts, or regulatory change
- Build a threat radar or early-warning system for strategic planning
- Prepare a board or leadership briefing on disruption risk
Inputs Required
Before starting, collect:
- Industry/market: The specific sector and sub-segment the company operates in
- Company description: What the business does, its model, and how it makes money
- Position in market: Incumbent leader / challenger / niche player / new entrant
- Core revenue drivers: The 1–3 activities or assets the business depends on most
- Known threats already on radar: Anything leadership is already watching
- Time horizon: How far out to scan (default: 0–18 months near-term, 18 months–5+ years long-term)
- Geographic scope: Local / national / global — regulatory and entrant analysis depends on this
If position in market or revenue drivers are unclear, infer from the company description and state the assumption explicitly.
Instructions
Step 1: Map the Disruption Surface
Before generating threats, identify what is actually disruptable. For each core revenue driver and key asset, ask:
- What customer job does this fulfill, and could that job be fulfilled another way?
- What does this depend on (a distribution channel, a regulation, a cost structure, a data moat) that could change?
- Where is the business advantaged today purely by inertia, scale, or switching costs rather than genuine value?
Note the 3–5 points of maximum exposure — these anchor the scan.
Step 2: Scan Across the Four Disruption Vectors
Generate threats in each of the four categories below. Aim for 8–12 distinct threats total, weighted toward the most exposed vectors identified in Step 1.
Vector 1 — Technology Shifts Capabilities that change what's possible or collapse a cost curve.
- Look for: AI/automation displacing a labor- or expertise-heavy step; a cost curve dropping (compute, sensors, energy, materials); a platform shift (mobile, on-device, edge); adjacent tech maturing into the category
- Test: Does this make the company's core activity cheaper, faster, or unnecessary for someone else?
Vector 2 — New Entrants Players entering from outside the traditional competitive set.
- Look for: adjacent-industry players with a customer relationship and a reason to expand inward; well-funded startups attacking a single profitable slice; platform/aggregator players who could absorb the function; international entrants crossing into the geography
- Test: Who already has the customer, the data, or the distribution and is one step from the company's revenue?
Vector 3 — Regulatory & Policy Change Rule changes that reshape what's allowed, required, or economic.
- Look for: pending legislation, enforcement shifts, data/privacy rules, sustainability mandates, licensing or liability changes, subsidy/tariff shifts
- Test: Would a plausible rule change make the current model illegal, more expensive, or suddenly open to competitors?
Vector 4 — Business Model Innovation New ways of packaging, pricing, or delivering value to the same customer.
- Look for: subscription replacing transactional; bundling/unbundling; marketplace disintermediating a middleman; freemium attacking a paid base; outcome-based or usage-based pricing; verticalization or platformization
- Test: Could a competitor win the same customer with a fundamentally different economic model?
Step 3: Score and Rank Each Threat
For every threat identified, assign:
- Likelihood (Low / Medium / High): probability of materially affecting the business within its time horizon
- Impact (Low / Medium / High): severity if it materializes — revenue at risk, defensibility lost
- Time horizon: Near-term (0–18 months) or Long-term (18 months–5+ years)
- Composite priority: High-likelihood + High-impact threats are Tier 1; rank the rest accordingly
Build a 3x3 likelihood-by-impact placement so the highest-priority threats are unambiguous.
Step 4: Define Early-Warning Signals
For each Tier 1 and Tier 2 threat, specify the leading indicators that would tell leadership the threat is moving from possible to imminent:
- A measurable signal (a funding round, a regulatory comment period opening, a competitor hire, a pricing change, an adoption threshold)
- Where to watch for it (filings, patent activity, job postings, analyst coverage, customer churn reason codes)
- A rough trigger point that should escalate internal attention
Step 5: Recommend Defensive and Offensive Moves
For each Tier 1 threat, give 1–2 concrete strategic responses — distinguishing between:
- Defensive: protect the core (deepen switching costs, lock in distribution, lobby, acquire the threat)
- Offensive: pre-empt by becoming the disruptor (launch the new model yourself, partner before forced to, cannibalize deliberately)
Step 6: Scenario Synthesis
Close with two short scenarios (4–6 sentences each):
- Most likely disruption scenario: how the highest-priority threats plausibly combine over the time horizon
- Highest-impact tail scenario: the lower-probability but business-threatening case worth pre-planning for
Output Format
- Structure: Disruption surface map → threats organized by the four vectors → ranked threat table → early-warning signals → strategic moves → two scenarios
- Length: 1,100–1,500 words
- Format: Structured document with a likelihood/impact ranking table; threats as labeled entries; scenarios as short prose
- Sections: Disruption Surface → Threats by Vector → Ranked Threat Table → Early-Warning Signals → Strategic Moves → Scenario Synthesis
- Tone: Strategy director briefing the board — analytical, specific, and willing to name uncomfortable threats; no hedging into generic "the market is changing fast" filler
Quality Checklist
Before delivering output, verify:
- [ ] All four disruption vectors are covered with at least one named threat each
- [ ] Total threats fall between 8 and 12, weighted toward the most exposed vectors
- [ ] Every threat has a likelihood rating, impact rating, and time horizon
- [ ] Tier 1 threats each have a specific early-warning signal with a place to watch it — not "monitor the market"
- [ ] Each Tier 1 threat has at least one concrete defensive or offensive move
- [ ] Both scenarios reference the specific threats identified — not generic futures
Notes
- The most dangerous threats usually come from new entrants and business model innovation, not technology — incumbents tend to over-watch tech and under-watch who already owns the customer
- Resist listing every conceivable threat; a radar with 30 items gets ignored. Rank ruthlessly and make Tier 1 small enough to actually monitor
- If the company is the incumbent leader, weight the scan toward asymmetric attackers (someone willing to lose money on a slice the leader can't afford to)
- Early-warning signals are the most actionable part of this deliverable — a threat without a trackable signal is just speculation
How to use this skill
This file is a Claude Code skill in Anthropic's standard format — markdown with YAML frontmatter at the top.
Installing in Claude Code:
~/.claude/skills/<folder-name>/SKILL.md— auto-loads in every session anywhere on your machine (recommended for skills you'll use across multiple projects)<your-project>/.claude/skills/<folder-name>/SKILL.md— auto-loads only when working in that project (recommended for project-specific skills)
Restart Claude Code or open a new session to register.
Using in Claude.ai, ChatGPT, Gemini, or other AI tools:
- Drag this file into a new chat, or copy and paste its contents
- Send your task or request as your next message — the AI will apply the skill where it fits
For Claude Code skill details: https://docs.anthropic.com/en/docs/claude-code/skills