SWOT analysis

What it is

SWOT is a 2×2 grid with four quadrants — Strengths, Weaknesses, Opportunities, and Threats. The rows split by source (what’s inside the team versus outside), and the columns split by valence (what helps versus what hurts). Strengths and Weaknesses describe the team itself; Opportunities and Threats describe the world around it.

The framework’s origin is contested. It’s commonly credited to Harvard Business School’s strategy curriculum under Kenneth Andrews in the 1960s — and Andrews’ Business Policy: Text and Cases (1965) does use the Strengths/Weaknesses/Opportunities/Threats framing. More recent scholarship (Puyt et al., Long Range Planning, 2023) traces the specific SWOT acronym to Albert Humphrey’s team at Stanford Research Institute in the same era, via an earlier “SOFT” variant. Either way, the framework has since been applied to everything from Fortune 500 strategy decks to startup pitch decks to individual career planning — and, more recently, to retrospectives and team self-assessment, which is where we use it.

The key insight of SWOT isn’t any single quadrant. It’s the crossings — Strengths that can be aimed at Opportunities, Weaknesses that are being exploited by Threats, Threats that can be neutralized by combining Strengths with Opportunities. That’s where the strategy lives.

When to use it

Use SWOT when:

• You need an honest team self-assessment before digging into the numbers. Participants engage with data more willingly when they’ve named the problem in their own words first.
• The problem being investigated has both internal (team behavior, process, tooling) and external (stakeholder availability, vendor friction, organizational structure) dimensions. SWOT forces both to surface.
• You need a short framing exercise that builds shared context quickly — 20 minutes is plenty.

Don’t use SWOT when:

• You need root-cause analysis. SWOT surfaces observations; it doesn’t structure the why behind them. After a SWOT, a 5 Whys or fishbone on the top Weakness is often the right next step.
• You need a quantified decision. SWOT produces lists, not numbers. If you need to pick between options by cost, effort, or impact, use a 2×2 prioritization matrix or force rank.
• The team is conflict-avoidant and no one is going to write real Weaknesses or Threats on the board. SWOT needs psychological safety to work. If you don’t have that, start with TRIZ (sabotaging-behavior naming) to build it.

In the planning workshop, SWOT is used as the opening exercise — specifically because planning waste is diffuse, and participants who’ve named the shape of the problem in their own words engage with the data exercises more honestly than if they’d been dropped straight into a meeting audit.

How to run it

Total time: 20 minutes. You can stretch it to 30 minutes on a large team, but any longer means you’re letting the conversation sprawl; that belongs in the exercises that follow.

Setup (2 min). Draw the 2×2 on the board — one quadrant in each corner, clearly labeled. Stickies in four colors (one per quadrant) help visual clarity; a single color works if that’s what you have.

Explain the categories (3 min). Teams frequently confuse Weaknesses and Threats, so be explicit. The distinguisher is who owns the fix. If the team could change it by deciding to, it’s internal (Strength or Weakness). If the fix requires someone outside the team to do something different, it’s external (Opportunity or Threat).

Silent fill (5 min). Each participant writes stickies silently, placing them in the appropriate quadrants. Silent start is critical — it’s the “1” of 1-2-4-All — because it prevents loud voices from anchoring the discussion before quiet voices have written anything.

Share and cluster (7 min). Each person walks their stickies to the board, reading each aloud and placing it. The facilitator clusters similar items live, working in the background. Don’t debate at this stage — just capture. If doing this remotely, mimic the ceremony by giving everyone a turn and having them read their “sticky” as they place it on a digital board.

Scan for patterns (3 min). The facilitator points at the clusters. “We’ve got a big Weakness cluster around decision timing. We’ve got Threats around vendor latency. We’ve got one shared Strength — the team actually respects the retrospective.” Name the themes. These become the starting points for whatever exercises come next.

Worked example

A six-person product team runs SWOT at the start of a planning workshop. Here’s what lands on the board:

What the facilitator does with this. The Weaknesses cluster around decision timing — three of the four items point at the same root. That cluster is a strong candidate for the event storming workshop, which maps the team’s decisions onto a timeline and exposes exactly where late decisions cost hours. The Opportunities show that two external parties have offered faster turnaround but the team hasn’t taken them up on it — those go directly into the action-item list. The Threats show the team is blocked by external parties whose behavior isn’t going to change quickly, so the action isn’t “make legal go faster” but “file earlier, bundle better.”

The Strengths matter too, but they’re about protection — don’t accidentally reform them away. If your retrospectives produce action items, don’t reform them as part of a “streamlining” action.

Common failure modes

• The Strengths quadrant is full of aspirations, not observations. “We deliver high-quality software” is a hope, not a Strength. A Strength is something you can point at with evidence. Ask: “When did this last show up? What did we see?” If the answer is hand-wavy, the item belongs in Opportunities, not Strengths.
• Weaknesses and Threats get conflated. Teams love to move blame externally. “Our CI is slow” is a Weakness (we own the CI); “vendor X’s SDK breaks” is a Threat (we don’t control their release process). If a facilitator lets Weaknesses migrate into Threats, the team ends up with a short action list because nothing feels like their problem.
• No one writes anything real in Weaknesses. This is a safety problem, not a SWOT problem. Pause, call it out (“we’ve got six people and two Weaknesses, which is suspicious”), and consider running TRIZ to prime the pump. Once the team has admitted to sabotaging behaviors as hypotheticals, Weaknesses fill in.
• Treating the output as the goal. SWOT is a warm-up, not the investigation itself. Resist the urge to drill into each item. The quadrants populate whatever exercises come next — don’t eat that time here.

Common crossings to look for

After the SWOT is populated, the real strategic content is in the crossings:

• Strength + Opportunity: Where can we use a strength to capitalize on an external opening? (Example above: the team’s respect for retrospectives + the customer’s openness to weekly demos → commit to a weekly review ritual.)
• Weakness + Threat: Where are we most vulnerable? An internal weakness exploited by an external force. This is the “emergency action” category — address these first. (Example: slow legal review + our habit of deciding late → we will be blocked.)
• Strength + Threat: How can we use our strengths to defend against external threats? (Example: engineering + product trust + vendor SDK instability → we can pair and triage faster when the vendor breaks something.)
• Weakness + Opportunity: What external openings could close our internal gaps? (Example: we don’t have good CI + platform engineering wants to pair → accept the pairing offer; another is our slow decision making + customer open to weekly reviews → schedule frequent UX reviews.)

This is sometimes called a “TOWS matrix” — same quadrants, explicit pairing. In practice, a good facilitator runs it informally during the “scan for patterns” step rather than drawing a second grid.

References

In the playbook

• My formula for running a successful workshop — the meta-framework every workshop in the Guides section follows.
• 1.2 Current state analysis — SWOT appears here as one of the core current-state-assessment tools for a Delivery Playbook engagement.
• 2.1 Product strategy — where SWOT graduates from retrospective-style team assessment to actual strategic positioning.
• 2.3 Strategic event storming — the structural follow-up for Weakness clusters around decision timing (as seen in this page’s worked example).

External references

• Kenneth R. Andrews, The Concept of Corporate Strategy (Irwin, 1971) — the Harvard Business School formulation most often credited as SWOT’s source.
• Richard W. Puyt, Finn Birger Lie & Celeste P.M. Wilderom, “The origins of SWOT analysis,” Long Range Planning (2023) — the contemporary scholarly re-examination that traces the specific acronym to Albert Humphrey’s team at Stanford Research Institute.
• Heinz Weihrich, “The TOWS matrix — A tool for situational analysis,” Long Range Planning (1982) — introduces the crossings/pairings extension (TOWS).
• TeamRetro, SWOT retrospective template — the agile-adaptation reference I most often point facilitators at.
• SessionLab, SWOT analysis — workshop-ready facilitator notes.
• Mind Tools, SWOT Analysis — a gentle introduction that pairs well with the canonical texts above.