Situation Analysis or SWOT for This Decision? Wrong Question

Choosing between situation analysis or SWOT is the wrong question. Neither tool tests the assumption your decision depends on. Both sort observations into categories. The right question is whether your chosen method forces the room to name the assumption carrying the recommendation and test it before acting.

Situation analysis or SWOT is the wrong question because neither tests the assumption the decision depends on. Both sort observations into categories. Neither asks which observation matters, which assumption is load-bearing, or what evidence would change the call. The choice between them is between two frameworks that stop one step short of the work the decision requires.

Someone in your organisation has told you to "do an analysis" before the team commits to a decision. You need to walk into the next meeting with something structured enough to survive scrutiny. The question forming in your mind is whether to run a SWOT or a full situation analysis.

I have spent nearly fifty years watching people produce thorough analyses and still make poor decisions. I have sat in boardrooms where the SWOT grid was thorough, the situation analysis was detailed, and the decision was still wrong. The analysis had sorted observations into neat categories without testing the assumptions that the entire decision rested on. The framework was never the problem; what did not happen after the grid was full was the problem every time.

A situation analysis maps the context around a decision. SWOT sorts it into four categories. Neither framework tests whether what it finds is true.

What SWOT Actually Does

SWOT sorts observations into four boxes: strengths, weaknesses, opportunities, threats. The grid forces a team to articulate what they see. The damage begins when the completed grid is treated as a conclusion, because the appearance of rigour substitutes for the work that would actually connect the analysis to the decision.

Terry Hill and Roy Westbrook studied SWOT use across 50 UK manufacturing companies in 1997 as part of the Department of Trade and Industry's Manufacturing Planning and Implementation Scheme. Over 20 of those companies generated SWOT outputs, and every application showed the same result: no prioritisation and no attempt to verify whether any listed item was actually true. Lists averaged 40 or more factors, each described in three or four words. None of the companies subsequently used their SWOT outputs in the later stages of the strategy process.

That study is nearly thirty years old; the pattern has not changed. Marilyn Helms and Judy Nixon reviewed 141 peer-reviewed studies on SWOT usage across multiple sectors in 2010. Their conclusion: no strategic direction emerged from the analysis itself, and no implementation strategies were developed to match strengths with opportunities. If you want to understand what SWOT analysis sorts and where it stops, the evidence is consistent across every sector and every decade.

Take the SWOT grid or situation analysis your team completed and write the assumption each entry depends on beside it. Start the Walk →

What a Situation Analysis Adds

A situation analysis examines factors that a SWOT grid excludes by design. Where SWOT asks "what are our strengths and weaknesses?", a situation analysis maps the full context around a decision: internal factors, external pressures, and the wider environment that neither you nor your competitors control.

Some of the most consequential changes arrive from outside the competitive frame that SWOT captures. They are not competitors; they are shifts in the conditions under which the entire competitive frame was built. A four-box grid has no category for that kind of change, and no mechanism for detecting it.

A situation analysis that examines context across all three bands creates a structured obligation to look at changes arriving from outside the competitive frame. Even so, a thorough situation analysis carries the same structural limitation as SWOT: it sorts information into categories without testing whether that information is correct, and it does not connect the sorted output to the decision that prompted the exercise.

Why Nokia's Analysis Was Thorough and Fatal

Nokia had every analytical tool available and still made a fatal decision. Timo Vuori and Quy Huy at INSEAD interviewed 76 Nokia top and middle managers, engineers, and external experts across multiple studies beginning in 2016. Nokia had extensive strategic planning infrastructure throughout the 2000s; the company correctly identified the smartphone transition as a strategic priority, and its environmental scanning was thorough by any reasonable standard.

A SWOT at the time would have listed "strong brand, global distribution network, Symbian platform" as strengths. A situation analysis would have mapped the competitive environment, the technology shift, and the regulatory environment across all three context bands. Both frameworks would have produced outputs that looked rigorous and complete.

The failure was underneath those outputs. Middle managers were afraid to share negative information with senior leaders, and the result was that senior leadership operated on overly optimistic assessments of Nokia's software capabilities. "Strong software capability" appeared as a strength in every strategic review; it was, in fact, a critical weakness that nobody tested. Nobody asked how confident they actually were that the claim was true. Nokia lost 90% of its market value between 2007 and 2012. I have watched the same dynamic in organisations that had every reason to test what they believed and chose not to.

Kodak invented the digital camera in 1975, and internal reports throughout the 1990s correctly identified digital photography as both a threat and an opportunity. The analysis was right; the decision was not made. Organisational culture, sunk costs in film manufacturing, and the untested assumption that the brand would provide adequate protection prevented action on what the analysis clearly showed. Kodak filed for bankruptcy in January 2012.

That is the structural problem with both frameworks. Completing a thorough situation analysis or SWOT does not produce a better decision; it produces a more thoroughly documented reason to believe you have already done the hard work.

What a Decision-Focused Analysis Looks Like

The only question that matters is whether your analysis tests the assumptions your decision depends on.

A SWOT is sufficient when the decision is well defined, the context is familiar, and the team needs a structured way to compare what it already knows. If you are deciding whether to extend a product line in a market you understand, a SWOT can organise the relevant considerations in an afternoon. For decisions that involve unfamiliar territory, volatile conditions, or commitments that stretch across years, a situation analysis will surface factors that a four-box grid would miss entirely.

Neither tool is sufficient on its own, because neither asks the questions that separate analysis from decision. Which of these observations are actually true? Which ones have the most influence over the outcome? What would change if a key assumption turned out to be wrong? Testing significance means examining each assumption for two properties: how much influence it has over the outcome, and how confident you are that it is accurate. An assumption with high influence and low confidence is the one that can destroy the decision; those assumptions are invisible on a SWOT grid and rarely surface in a conventional situation analysis.

Roger Estall and I built the Universal Decision-Making Method around that sequence: establish the context for this specific decision, surface the assumptions the decision depends on, and test those assumptions before committing resources. We wrote Deciding because we kept encountering organisations that had produced excellent analysis and still made poor decisions. The analysis was always sound; the assumptions underneath were never examined.

If someone has asked you to "do an analysis," the question to take back is not "SWOT or situation analysis?" The question is: what are the assumptions this decision depends on, and what happens after the grid is full? The framework you choose for sorting is secondary. What matters is whether anyone tests the assumptions before the organisation commits resources.

---

Grant Purdy is the co-author, with Roger Estall, of Deciding (2020), and the architect of the Universal Decision-Making Method.