Use when building a structured framework to assess a competitive landscape, evaluate market position, or inform strategic decisions about differentiation
Scanned 9/8/2026
Install to Claude Code
npx -y skills add jeffreytse/grimoire-core --skill design-competitive-analysis --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Design Competitive Analysis?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/jeffreytse-design-competitive-analysis)More formats (shields.io, HTML) on the badges page.
---
name: design-competitive-analysis
description: Use when building a structured framework to assess a competitive landscape, evaluate market position, or inform strategic decisions about differentiation
source: Michael Porter "Competitive Strategy" (1980); Porter "The Five Competitive Forces That Shape Strategy" HBR (2008); McKinsey competitive intelligence methodology
tags: [competitive-analysis, porter, market-intelligence, business-strategy]
verified: true
---
# Design Competitive Analysis
Build a structured competitive analysis framework that reveals market position, competitor vulnerabilities, and defensible differentiation.
## Why This Is Best Practice
**Adopted by:** McKinsey & Company, BCG, Bain, Fortune 500 strategy teams, and VC-backed startups in competitive markets
**Impact:** Porter's Five Forces framework has been cited 40,000+ times and used by 95% of Fortune 500 strategy teams. McKinsey research shows companies that conduct systematic competitive analysis outperform peers on revenue growth by 15% over 5 years.
**Why best:** Competitive analysis done structurally — not as a feature comparison spreadsheet — reveals structural industry dynamics, sustainable competitive advantages, and whitespace opportunities that ad-hoc benchmarking misses.
Sources: Porter "Competitive Strategy" (1980); Porter "The Five Competitive Forces That Shape Strategy" HBR (2008); McKinsey Competitive Strategy Methodology
## Steps
1. **Define the competitive arena** — specify the market boundary: what is the product category, customer segment, and geography you are analyzing. Overly broad definitions dilute insight; overly narrow miss substitutes.
2. **Run Porter's Five Forces** — assess each force on a 1–5 scale: (1) Threat of new entrants, (2) Bargaining power of buyers, (3) Bargaining power of suppliers, (4) Threat of substitutes, (5) Rivalry among existing competitors. Forces that are high (3–5) constrain industry profitability.
3. **Map the competitive set** — identify: direct competitors (same product, same customer), indirect competitors (different product, same job-to-be-done), and substitutes (different category, same outcome). Include incumbents and emerging entrants.
4. **Build a competitor profile for each key player** — document: products/features, pricing, target segments, distribution channels, strengths, weaknesses, recent moves (funding, hires, product launches), and stated strategy.
5. **Create a positioning map** — select two dimensions that matter to customers (e.g., price vs. complexity, speed vs. customization). Plot all competitors. Identify whitespace that is both unoccupied and valued by customers.
6. **Analyze competitive moats** — for each competitor, identify their sustainable advantage: (1) network effects, (2) switching costs, (3) scale economies, (4) cost advantages, (5) brand, (6) patents/IP, (7) regulatory licenses. Moats determine durability of position.
7. **Assess competitive dynamics** — identify: who is growing, who is declining, which segments are contested, where pricing pressure is highest, and what strategic moves each competitor is likely to make in 12–24 months.
8. **Identify your differentiation** — given the landscape, articulate where you have or can build a defensible advantage. Test whether the differentiation is real (customers will pay for it), rare (few competitors have it), and durable (hard to copy in < 18 months).
9. **Define strategic implications** — translate findings into decisions: which segments to enter or avoid, which product capabilities to accelerate, which partnerships to pursue, and how to price relative to competitors.
10. **Establish an intelligence cadence** — assign ownership of ongoing competitor monitoring: set up Google Alerts, track job postings (signals hiring priorities), monitor product releases, and review pricing pages quarterly.
## Rules
- Never build a competitive analysis around features alone — features are copyable; structural advantages are not.
- Include substitutes and indirect competitors, not only direct rivals — Uber's main competitor in 2010 was not Lyft, it was taxis and car ownership.
- Validate competitor intelligence with primary research — customer interviews about why they evaluated competitors are more reliable than analyst reports.
- Update the analysis when a competitor raises funding, makes an acquisition, or launches a new product line.
- Separate facts from assumptions in competitor profiles — label inferred information as "estimated."
## Common Mistakes
- **Feature comparison tables only** — these show parity but not structural advantage; they invite product managers to copy features rather than build moats.
- **Ignoring incumbents' switching costs** — established competitors retain customers even with inferior products through switching friction; this must be quantified.
- **Static analysis** — a competitive landscape analyzed once and filed away provides no ongoing strategic value.
- **Anchoring on direct competitors** — companies disrupted by substitutes from adjacent categories (Blockbuster vs. Netflix) failed to monitor the right competitive set.
## When NOT to Use
- Brand new market creation where no competitors exist (use Jobs-to-be-Done analysis and substitute mapping instead)
- Internal process improvement initiatives without external market relevance
- Academic analysis without decision-making application (use only if tied to a specific strategic question)
Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!