SWOT vs Porter's Five Forces
SWOT analyzes a specific position. Five Forces analyzes the industry that position sits inside. Confusing them produces strategy decisions that don't survive contact with the market.
These are the two most-recognized strategy frameworks. Both feel like "competitive analysis" tools, which is why they get conflated. The difference matters: SWOT is about who you are; Five Forces is about which game you're playing.
At a glance
| SWOT | Five Forces | |
|---|---|---|
| What it analyzes | A specific firm, product, or position | An entire industry's structure |
| Unit of analysis | One company / one decision | One market / one industry segment |
| Time horizon | Snapshot (months) | Structural (years) |
| Output | 4 quadrants of actions | 5 force-strength assessments + structural verdict |
| Question answered | "What should this team do?" | "Is this a good industry to be in?" |
| Origin | Humphrey at SRI, 1960s | Michael Porter, 1980 |
When to use SWOT
You're evaluating a specific decision facing a specific organization. The internal/external structure (S/W are internal; O/T are external) directs you to actions that fit your particular situation.
When to use Five Forces
You're trying to understand the long-run profitability potential of an industry, or you're deciding whether to enter / exit / restructure within an industry.
Full Five Forces Academy guide →
The pattern that works
Five Forces first, then SWOT — when entering or evaluating an industry.
- Five Forces tells you whether the industry is structurally attractive (will any well-run firm here make money?)
- If yes, SWOT tells you whether this specific firm has the position to capture that opportunity.
A SWOT done without industry context produces strategy that ignores structural forces. A Five Forces without SWOT tells you the game is worth playing but not whether you can win it.
The conflation pattern
Teams sometimes try to fold Five Forces into SWOT's Threats quadrant. This sort of works but loses fidelity — the Threats quadrant becomes a long list, and the structural force most likely to dominate gets buried among tactical threats.
The cleaner pattern: do Five Forces as a standalone session. Identify the dominant force (usually one of the five is much stronger than the others). Then in SWOT, the dominant force becomes a single specific entry in Threats — with the structural reasoning behind it documented in the Five Forces output.
Common failure mode
Treating internal capability (SWOT strength) as a substitute for industry structure (Five Forces). A team will say "we have a strong team and great product — we can win in this market." But if Five Forces shows the industry compresses every player's margins to near zero (e.g., airlines), team quality doesn't save you. Buffett famously made this mistake on airlines twice.
The diagnostic question: if you're certain you have strengths but the industry has shown long-run low returns for everyone, the structural force is winning. Either change the game (find a niche the structural forces don't dominate) or pick a different industry.
When neither is the right tool
- For product-level decisions, both are too high-level — use RICE or JTBD
- For risk evaluation on a specific bet, a premortem is sharper
- For organizational design, use McKinsey 7S, not Five Forces
In 30 seconds
Specific position, specific decision → SWOT. Whole industry, structural question → Five Forces. Real strategy work → both, Five Forces first.