Skills on AI 459 skills

Active theme: Light

SWOT Analysis

Use when asked to run or explain a SWOT analysis — Strengths, Weaknesses, Opportunities, Threats — the internal-vs-external strategic planning framework, sourced from Wikipedia's SWOT analysis article, including its history and known limitations.

SWOT analysis is a strategic planning framework organized around one core distinction: internal factors the organization controls (Strengths, Weaknesses) versus external factors it doesn't (Opportunities, Threats).

The four quadrants

  • Strengths — internal characteristics giving the organization a competitive advantage (human resources, physical assets, finances, reputation).
  • Weaknesses — internal characteristics placing the organization at a disadvantage relative to others.
  • Opportunities — external elements the organization could exploit to its advantage (market trends, economic conditions, legislative changes, demographic shifts).
  • Threats — external elements that could cause harm.

The internal/external split is the framework's defining structural choice — Strengths and Weaknesses are usually considered internal; Opportunities and Threats are usually considered external. This is exactly where PESTLE Analysis connects to SWOT: PESTLE's macro-environmental scan is a common, structured way to populate the external Opportunities/Threats quadrants rather than guessing at them.

History

The concept originated in 1965 through two parallel efforts: the Stanford Research Institute's Long Range Planning Service developed a related "SOFT" framework (satisfactory, opportunities, faults, threats), while Harvard Business School faculty published Business Policy: Text and Cases, establishing the internal/external division that SWOT still uses. The "SWOT" acronym itself emerged by 1972 and became widely adopted after that.

Typical process

  1. Identify internal and external factors across all four quadrants, usually via team discussion or workshop.
  2. Evaluate the relative importance of each identified factor — a long unranked list under each quadrant is less useful than a short, prioritized one.
  3. Examine relationships between quadrants, not just within them — a Strength that could address a specific Threat, or a Weakness that would block capturing a specific Opportunity, is where SWOT's real strategic value shows up.
  4. Present results, commonly as a 2×2 matrix, and connect the findings to an actual strategic decision.

Common criticisms

  • Findings often go unused — a well-documented, real criticism is that organizations frequently produce a SWOT matrix and then don't use its output in the later stages of actual strategy formulation; the exercise becomes a static artifact rather than an input to a decision.
  • Static analysis in a dynamic environment — like PESTLE Analysis, SWOT captures a snapshot and doesn't naturally account for how competitive conditions shift.
  • Personal bias in factor selection — what counts as a "Strength" or "Weakness" is often shaped by whoever is in the room, not by objective measurement.
  • Over-weighting external factors can produce a reactive strategy (responding to Threats/Opportunities) rather than a proactive one built from genuine Strengths.

Common pitfalls

  • Populating quadrants without prioritizing — an exhaustive but unranked list in each box is harder to act on than a short list of the few factors that actually matter most for the decision at hand.
  • Confusing "internal" and "external" placement — a factor phrased as a Weakness ("we lack market share") that's actually a symptom of an external Threat ("a well-funded competitor entered our market") gets the analysis backwards and can misdirect the response.
  • Stopping at the matrix — per the well-documented criticism above, the highest-value step (relating quadrants to each other and to an actual decision) is exactly the step most often skipped.
  • Never revisiting the analysis — treating a SWOT done once as permanently valid, when the framework's own known limitation is that it's a snapshot in a fluid environment.

Learn more

View swot-analysis/SKILL.md on GitHub