SWOT Analysis

Origin & evolution

The origins of SWOT are genuinely disputed, and no single inventor is documented with certainty. The technique is most often traced to corporate-planning research carried out at the Stanford Research Institute (now SRI International) through the 1960s and early 1970s, where a team studying why corporate planning failed at large companies developed a method that several accounts attribute to Albert Humphrey. Humphrey himself credited the wider team and an earlier "SOFT" framing (Satisfactory, Opportunity, Fault, Threat). The cleaner four-letter acronym spread through business-school teaching and consulting during the 1980s, helped along by Heinz Weihrich's 1982 paper on the TOWS matrix, which paired the four quadrants to generate strategies. Today SWOT opens marketing plans, competitive reviews, and product strategy decks, usually as a warm-up exercise and not the conclusion.

How it works in practice

Draw a two-by-two grid. The top row holds internal factors, the bottom row external ones. The left column is helpful, the right harmful.

• Strengths: internal advantages the team controls. A loyal install base, a proprietary dataset, a fast release🚢ReleaseProduct SpecificationA shipped version of the productView reference → cadence.
• Weaknesses: internal gaps. A thin support team, a single-region deployment📤DeploymentEngineeringA deployment eventView reference →, a capability💪CapabilityStrategyAn ability that enables value deliveryView reference → the market expects that you lack.
• Opportunities: external openings. A competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → sunsetting a product, a regulation that favours your model, an under-served segment.
• Threats: external risks🎲RiskComplianceA risk to the product or businessView reference →. A well-funded entrant, a platform policy change, a shift in buyer budgets.

The discipline is in the sorting. A common mistake is to log a market trend📉Market TrendMarket IntelligenceAn emerging trend in the marketView reference → under Strengths because it feels positive. A trend is external, so it belongs in Opportunities or Threats. Once the grid is full, do the step teams usually skip: pair the boxes. Match a Strength to an Opportunity to find a move you are positioned to make. Match a Weakness to a Threat to find an exposure worth closing now. That pairing is the TOWS step, and it turns a static list into a set of candidate strategies.

A worked example. A B2B analytics tool lists a strong onboarding flow under Strengths and a wave of teams migrating off a deprecated competitor under Opportunities. Pairing the two points straight at a migration-assist campaign timed to the competitor's shutdown date.

When to use it (and when not)

Reach for SWOT at the start of a planning cycle, ahead of an annual strategy session, or when you enter a new market and the team needs🫀NeedUserA user need, pain, desire, or constraintView reference → a shared baseline quickly. It is fast, needs no special data, and gets tacit knowledge onto one surface.

It earns its keep as a structuring step and falls down when treated as an answer. The grid has no weighting, no evidence🔎EvidenceValidationData supporting or refuting a hypothesisView reference → bar, and no ranking, so a long list of plausible items can feel like analysis while committing the team to nothing. The usual failure modes: filling all four boxes evenly for appearance, confusing internal and external factors, and stopping at the grid without pairing the quadrants into decisions⚖️DecisionStrategyA recorded decision with context, rationale, and consequencesView reference →. When you need to rank options or model a market structurally, follow SWOT with a scoring method or with Porter's Five Forces.

In the Unified Product Graph

SWOT is a matrix framework in the strategy category. Its four quadrants map onto distinct entity types, which is why the Unified Product Graph keeps them as separate, linkable nodes and not free text in a box:

• Strengths become capability💪CapabilityStrategyAn ability that enables value deliveryView reference → entities, the things the product or team can reliably do.
• Weaknesses surface as need🫀NeedUserA user need, pain, desire, or constraintView reference → entities, the gaps the product has yet to close.
• Opportunities are opportunity🚪OpportunityDiscoveryA validated gap worth solvingView reference → entities, openings worth pursuing.
• Threats are competitor🥊CompetitorMarket IntelligenceA competing product or companyView reference → entities and other external risks, the forces acting against the plan.

Modelling SWOT this way means a Strength logged once can connect to the feature⭐FeatureProduct SpecificationA product capability or featureView reference → that delivers it, and a Threat can link to the competitor it names. The grid stops being a one-off snapshot and becomes part of the live product graph, where every quadrant item carries its own relationships.