SWOT Analysis: Why a SWOT Is Not a Strategy (and How to Use It Anyway)

This is one of RoadmapOne ’s articles on Strategy for Product Leaders .

SWOT analysis is a structured scan of an organisation’s position, with four quadrants: Strengths (internal advantages), Weaknesses (internal limitations), Opportunities (external conditions to exploit), and Threats (external conditions that could impede progress). SWOT is widely used for strategic planning — but it is description, not strategy. A SWOT produces inputs; a real choice framework (Playing to Win, Rumelt’s kernel) is required to turn those inputs into strategic commitments.

In 1997, Terry Hill and Roy Westbrook published a paper in Long Range Planning with a headline that should have changed an industry: “SWOT Analysis: It’s Time for a Product Recall”. Hill and Westbrook had spent several years studying how SWOT analysis was actually used in practice, across multiple organisations, and the results were devastating. The typical SWOT contained roughly forty unprioritised items. Nobody in the organisation used the outputs for any downstream decision. The exercise consumed meaningful management time, produced a matrix that was filed, and changed essentially nothing. Hill and Westbrook’s conclusion: in its current usage, SWOT produces no discernible benefit and should be reconsidered as a strategic tool.

That was twenty-nine years ago. SWOT has not been recalled. It remains the single most widely-used strategic-assessment tool in the world. Management teams at every level of every industry produce SWOTs annually, present them in board meetings, and file them. They also, almost universally, make the same four mistakes Hill and Westbrook identified: too many items, no prioritisation, no connection to action, and padding in Strengths while minimising Weaknesses. The 1997 critique aged perfectly. The practice has not.

This article is a contrarian take—because the SWOT literature is so uncritical that a corrective is genuinely needed—but it’s not a dismissal. SWOT has real value when used correctly. The value is not as a strategy. The value is as an input to strategy, specifically as a structured scan of the company’s position that feeds into a proper choice framework like Playing to Win or Rumelt’s diagnostic kernel . Used as strategy, SWOT is theatre. Used as input, it’s genuinely useful. The distinction matters enormously.

Sign up (free) to turn situational scans into strategic choices

What Is a SWOT Analysis?

SWOT stands for Strengths, Weaknesses, Opportunities, and Threats, typically presented as a 2×2 matrix:

• Strengths — internal capabilities, resources, and positions that give the organisation an advantage.
• Weaknesses — internal gaps, limitations, or disadvantages relative to competitors or requirements.
• Opportunities — external conditions the organisation could exploit to achieve outcomes it otherwise wouldn’t.
• Threats — external conditions that could impede the organisation’s outcomes or erode its position.

The horizontal axis splits internal (Strengths/Weaknesses) from external (Opportunities/Threats). The vertical axis splits positive (Strengths/Opportunities) from negative (Weaknesses/Threats). The framework is attributed to Albert Humphrey of Stanford Research Institute in the 1960s, though the precise origin is disputed. Since then it has been universally taught, universally adopted, and—to Hill and Westbrook’s original point—almost universally misused.

At its best, SWOT produces a structured scan of the organisation’s position in its environment. It forces the team to name strengths explicitly (not assumed), acknowledge weaknesses directly (not euphemised), identify opportunities beyond the obvious, and confront threats that might otherwise be ignored. That scan is useful. The scan is not, however, a strategy.

The 1997 Critique That Nobody Cites

Hill and Westbrook studied 20 companies using SWOT, conducted interviews with managers, and audited the outputs. Their findings:

1. The average SWOT contained 40 unprioritised items. There was no mechanism to identify which Strengths mattered most, which Weaknesses threatened survival, or which Opportunities justified capacity allocation.
2. The items were vague. Strengths included things like “strong brand” or “experienced team”. Weaknesses included things like “need to improve technology” or “skills gaps”. These descriptions were not specific enough to drive action.
3. Strengths were padded. Organisations systematically listed more Strengths than Weaknesses, and the Strengths were often assertions rather than evidence-backed capabilities. The political dynamic of the SWOT workshop rewarded positive framing.
4. Outputs were not used downstream. The SWOT was presented in a strategy document, filed, and never referenced again in any subsequent decision. The 40-factor list was disconnected from the actual initiatives, budget allocation, and roadmap the organisation pursued.

Hill and Westbrook’s recommendation was not to abolish SWOT but to recall the practice and redesign the tool so that it actually drove decisions. Twenty-nine years later, the recommendation remains unimplemented. The typical SWOT in 2026 has the same four defects the 1997 paper described. Product leaders who want to use SWOT intelligently should start by reading the Hill-and-Westbrook critique and explicitly designing around the four failure modes it identified.

Why SWOT Is Description, Not Strategy

A SWOT is a scan. It catalogues things that are true about the organisation and its environment. Nothing in the tool forces a choice between alternatives, a commitment to a direction, or a coherent set of actions. The Strengths don’t prioritise themselves. The Opportunities don’t rank themselves against the organisation’s capacity to pursue them. The Threats don’t self-weight by severity or probability.

Compare with a real strategy framework:

• Playing to Win forces five cascading choices. You cannot complete the cascade without making a commitment.
• Good Strategy Bad Strategy requires a kernel—diagnosis, guiding policy, coherent action—each of which is a choice.
• 7 Powers demands you name which of seven specific structural Powers you are building.
• Porter’s Generic Strategies requires picking one of three (or, in 2026, effectively one of one).

SWOT has no equivalent forcing function. You can complete a SWOT without making any commitment whatsoever. That’s why the tool produces such uneven results: in the hands of a disciplined strategist, SWOT is a useful scan that feeds into a real choice framework; in the hands of an undisciplined team, SWOT is the scan and the strategy, which produces forty unprioritised items and no decisions.

Hill and Westbrook’s point was never that SWOT is worthless. It was that SWOT alone is not a strategic output. The tool needs to be paired with, and subordinated to, something that forces commitment.

The Four Hallmarks of a Vanity SWOT

Vanity SWOTs—the kind produced at offsites and filed in Confluence—share four characteristics. If your product-strategy document’s SWOT has two or more of these, you have a vanity SWOT:

Too many items. More than ten items per quadrant is almost always too many. A SWOT with 40 items is a catalogue, not an analysis. The discipline of keeping each quadrant to three to five items forces prioritisation at the moment of capture, which is the only point in the process where prioritisation is natural. Add items later and the list grows without bound; start with the constraint and the list is forced to be strategic.

Padding the Strengths. Organisations produce more Strengths than Weaknesses because the political dynamic of the workshop rewards positive framing. The workshop participants don’t want to advertise organisational weakness, especially in writing, especially in a document the board might read. The result is a Strengths list that includes aspirational capabilities (“best-in-class engineering culture”) and a Weaknesses list that omits the obvious structural problems everyone in the room could recite from memory. A SWOT that fails to include the five-biggest-weaknesses-everyone-privately-acknowledges is not a strategic document; it’s a marketing document.

Vague items. “Strong brand” is not a Strength—it’s an assertion. “Strong brand in UK mid-market accounting with 70% aided recall among CFOs at firms over £5m revenue” is a Strength. The specificity transforms the item from a claim to an evidence-backed position that can be tested, measured, and defended. Vague SWOT items cannot be used downstream because they don’t carry enough information to drive action.

No link to downstream decisions. This is the defect Hill and Westbrook emphasised most. A SWOT that doesn’t connect to actual budget, roadmap, capacity-allocation, or business-case decisions is strategy theatre. The test: can you trace each item in the SWOT to a subsequent commitment? If not, why did you do the SWOT?

SWOT-as-Telemetry: The AI-Era Reframe

The traditional SWOT cadence is annual—produced at a strategy offsite, presented to the board, filed, refreshed twelve months later. That cadence assumed the landscape moved slowly enough that annual refresh was sufficient.

In 2026, the landscape moves too fast for annual refresh. Capabilities that were Strengths eighteen months ago may have become table-stakes as competitors caught up. Opportunities that were real twelve months ago may have been captured by faster-moving entrants. Threats that didn’t exist six months ago may now be category-defining. The annual-offsite SWOT produces a snapshot that is partially obsolete before it reaches the board pack.

The corrective is to treat SWOT as telemetry—continuous, signal-driven, lightweight. Quarterly refresh at minimum, with live updates when specific events warrant them. A new AI-native entrant with aggressive pricing is a new Threat; log it. A new regulatory tailwind in a target segment is a new Opportunity; log it. A capability gap you’ve closed in the last quarter is a retired Weakness; remove it. The SWOT becomes a living artefact that reflects the current strategic landscape, not a once-yearly snapshot of the landscape as it was.

This reframing also changes how the SWOT feeds into downstream decisions. Instead of producing an annual document that gets buried, telemetry-style SWOT feeds the quarterly strategic review, the OKR-setting cycle, and the roadmap allocation conversation. It becomes infrastructure, not event. The 1997 critique’s core problem—outputs not used downstream—dissolves because the outputs are now continuously produced and consumed by the ongoing decision cycle.

Sign up (free) to make SWOT signals drive roadmap reallocation

SWOT vs PESTLE vs Five Forces: Which to Use When

Each of these frameworks scans a different layer of the environment. Using one to answer another’s question produces shallow analysis; using them together produces a complete picture.

• SWOT scans company-specific position—internal strengths/weaknesses vs external opportunities/threats. Use it to understand where this company stands.
• Porter’s Five Forces scans industry structure—the five forces determining whether the industry is attractive to operate in. Use it to understand whether you’re in a good market.
• PESTLE (Political, Economic, Social, Technological, Legal, Environmental) scans macro environment—the broad context affecting all industries. Use it to understand the weather beyond your industry.

A complete situational assessment uses all three. PESTLE establishes the macro backdrop. Five Forces diagnoses the industry within that backdrop. SWOT positions the specific company within that industry. Skipping layers produces blind spots. Running all three produces enough context to feed a real strategy framework like Playing to Win .

The common confusion is using SWOT for questions PESTLE or Five Forces should answer. “Economic uncertainty” is a PESTLE item, not a SWOT Threat. “Intense competitive rivalry” is a Five Forces diagnosis, not a SWOT Threat. When these show up in the SWOT quadrants, the analysis is either incomplete (missing the Five Forces and PESTLE context) or confused (using the wrong tool for the question).

How to Use SWOT Properly

Given the traps, a disciplined SWOT process looks like:

Step 1: Establish the macro and industry context first. Run PESTLE. Run Five Forces. These establish what’s true about the environment before you ask what’s true about the company. Without this context, SWOT produces items that belong in other frameworks.

Step 2: Enforce item discipline. Three to five items per quadrant. Each item specific, evidence-backed, and expressible in a single sentence. If the team wants to list ten Strengths, force the choice: which are the top five, and what are the criteria? The discipline of choosing at the moment of capture is the whole point.

Step 3: Address the Strengths-padding failure mode directly. Brief the workshop: we are going to list the five biggest Weaknesses everyone in this room privately acknowledges, before we list any Strengths. Make it safe to name the uncomfortable truths, or the SWOT will default to marketing.

Step 4: Connect to downstream decisions explicitly. At the end of the SWOT, for each item, name the downstream decision it affects. “This Strength means we should defend our position in segment X.” “This Weakness means we must close the capability gap before pursuing Opportunity Y.” “This Threat requires a capacity allocation to defensive work.” If an item affects no downstream decision, drop it.

Step 5: Feed it into a choice framework. The SWOT is the input. Playing to Win ’s cascade, Rumelt’s kernel , or the prioritisation frameworks are where the input becomes a decision. Never stop at the SWOT itself.

Step 6: Treat it as telemetry. Quarterly refresh at minimum. Live updates when specific events warrant them. The SWOT is never “done”; it is a living instrument that tracks your situational position over time.

When SWOT Earns Its Keep

For all the criticism, SWOT earns its keep in three specific use cases:

Onboarding a new leader. A new CPO or new board member coming into a business benefits enormously from a concise SWOT that captures the current situational assessment. Three-to-five items per quadrant, specific and evidence-backed, read in thirty minutes, produces context that would otherwise take weeks to accumulate. Used as context, SWOT is valuable. Used as strategy, it’s theatre.

Structured pre-read for a strategy offsite. Before running a Playing to Win exercise, a short SWOT establishes the shared baseline of what’s true. The strategy workshop then starts from the agreed-upon assessment rather than re-litigating the basics.

Board situational-awareness packs. Boards benefit from a compact SWOT as part of the regular reporting cycle—not as the strategy itself, but as the honest scan underlying it. A board that sees the same SWOT every quarter with items added, removed, and revised over time has telemetry on the company’s evolving position. Gaps between how strengths are described and how they’re performing (in the numbers) become visible.

In each of these cases, SWOT is used as input to something else. It is never used as the strategic output itself. That’s the whole distinction Hill and Westbrook were pointing at in 1997.

Connecting SWOT to the Roadmap

Once the SWOT has produced its input, the subsequent strategy framework’s output is what connects to the roadmap. If you’ve used SWOT correctly, the SWOT will have fed into a Playing to Win cascade, a Rumelt kernel , or a prioritisation exercise , any of which produces tagged Objectives that flow to the capacity grid in RoadmapOne .

When the SWOT changes—a new Threat appears, a Strength fades, an Opportunity expires—the downstream choice framework reruns and produces updated tags. The roadmap reallocates. This is what SWOT-as-telemetry looks like in practice: the scan updates, the choice updates, the allocation updates. The SWOT is not the thing that allocates capacity; the SWOT is the signal that drives the re-allocation.

FAQ

Is SWOT outdated?

Not outdated, but widely misused. The scan SWOT produces is as useful as ever. What’s outdated is the typical practice of using SWOT as a strategic output rather than an input. Hill and Westbrook documented the specific failure modes in 1997 (forty unprioritised items, padded Strengths, no connection to decisions) and they persist today. SWOT used as input to a real choice framework — Playing to Win , Rumelt’s kernel — is useful. SWOT used as strategy is theatre.

What comes first, SWOT or PESTLE?

PESTLE comes first. PESTLE (Political, Economic, Social, Technological, Legal, Environmental) scans the macro environment — the broad forces affecting all industries. SWOT then positions the specific organisation within that macro context. Running SWOT without PESTLE risks cataloguing “Threats” that are actually broad PESTLE forces affecting everyone — and missing the company-specific vulnerabilities that SWOT is meant to surface. The correct sequence is PESTLE → Porter’s Five Forces (industry layer) → SWOT (company layer) → choice framework (decision layer).

What replaced SWOT analysis?

Nothing has wholesale replaced SWOT, but several frameworks have filled its specific weaknesses. Playing to Win and Rumelt’s kernel cover the choice-making step SWOT was often asked to do and cannot. Wardley Maps cover the situational-awareness layer more rigorously than a SWOT quadrant. Porter’s Five Forces covers industry-structure analysis. SWOT remains useful as a lightweight scan; it just shouldn’t be asked to do the work the other frameworks do better.

What are the four parts of a SWOT analysis?

The four parts are: Strengths (internal capabilities that give advantage), Weaknesses (internal gaps or limitations), Opportunities (external conditions to exploit), and Threats (external conditions that could impede progress). The horizontal axis separates internal from external; the vertical axis separates positive from negative. The framework is a structured scan of the company’s situational position.

Who invented SWOT analysis?

The origin is disputed. It is most commonly attributed to Albert Humphrey at Stanford Research Institute in the 1960s, though some attribute earlier development to Harvard Business School faculty including Kenneth Andrews. The framework has been in widespread use since the 1970s and became a standard part of MBA curricula in the 1980s.

What are the limitations of SWOT analysis?

In 1997, Terry Hill and Roy Westbrook published “SWOT Analysis: It’s Time for a Product Recall” documenting four consistent limitations: the typical SWOT contained 40 unprioritised items, Strengths were systematically padded while Weaknesses were minimised, items were too vague to drive action, and outputs were not used for any downstream decision. Twenty-nine years later, most SWOTs still exhibit all four defects. The framework produces description without decision unless paired with a proper choice framework like Playing to Win .

How is SWOT different from Porter’s Five Forces?

Porter’s Five Forces analyses industry structure—whether the market is attractive to operate in. SWOT analyses company-specific position—where this specific company stands relative to the landscape. They are complementary. Use Five Forces to establish the industry context, SWOT to position the company within it. Confusing the two (applying SWOT to industry questions or Five Forces to company questions) produces shallow analysis.

Is SWOT still relevant in 2026?

Yes, used correctly. Used as strategy, SWOT produces the same forty-item, unprioritised, never-actioned document Hill and Westbrook criticised in 1997. Used as input to a real choice framework—Playing to Win, Rumelt’s kernel, a prioritisation exercise—SWOT is a genuinely useful structured scan. In the AI era, treat it as continuous telemetry (quarterly refresh minimum) rather than an annual offsite artefact, because the landscape moves too fast for yearly snapshots.

How do I use SWOT effectively?

Enforce item discipline (3-5 per quadrant, specific and evidence-backed), deliberately surface the uncomfortable Weaknesses before listing Strengths, connect each item explicitly to a downstream decision, feed the SWOT into a real strategy framework rather than treating it as the output, and refresh it quarterly as telemetry. The goal is to turn the scan into commitments. If the SWOT doesn’t produce commitments, it’s theatre.

Conclusion

SWOT has survived four decades of deserved criticism because it’s easy to teach, intuitive to run, and politically safe to produce. None of those qualities make it a strategy. The 1997 critique—forty items, vague, padded, unactioned—remains devastatingly accurate in 2026, and the response from the strategy literature has been, broadly, to ignore it. Product leaders who want to use SWOT intelligently start by reading Hill and Westbrook, designing around the four failure modes, and subordinating the SWOT to a real choice framework rather than treating it as the strategic output.

Used correctly, SWOT is a valuable structured scan that feeds into Playing to Win , Rumelt’s kernel , or prioritisation exercises and ultimately lands in the roadmap capacity grid as tagged Objectives. Used incorrectly, it is a 2×2 matrix in a strategy deck that changes nothing. The distinction is which side of that you work to land on. The framework itself won’t force you. That forcing function is what the other frameworks in this cluster are for.

Sign up (free) to turn SWOT signals into roadmap decisions