What Is a SWOT Analysis? Using It for Product Decisions

A SWOT analysis sorts what you know about a situation into four boxes: strengths, weaknesses, opportunities and threats. Plenty of product teams have filled one in at an offsite. Fewer have used one to settle an argument, because the version made at offsites describes the whole company and so can't favor any one choice over another.

Scoped to a single decision, the same grid is useful. It forces a team to separate what it controls from what it doesn't, and to write down the evidence behind each claim before arguing about priority.

What is a SWOT analysis

It's a two-by-two grid. One axis splits internal factors from external ones. The other splits factors that help the goal from factors that hurt it.

	Helps the goal	Hurts the goal
Internal (you control it)	Strengths	Weaknesses
External (you don't)	Opportunities	Threats

The internal/external line is the part people get wrong. "Our onboarding has a 40% drop-off at step 3" is a weakness, since the team built step 3 and can change it. "A competitor just shipped free onboarding templates" is a threat, since nothing the team does will un-ship it. Mixing the two produces a grid where every box contains a to-do item and nothing about the environment.

The method comes from 1960s business-policy teaching, and it was built for company-level strategy. Product teams borrow it for smaller calls: whether to build a feature, enter a segment, change pricing, or sunset something.

Scope it to one decision

Write the decision at the top of the page as a question with a yes or no answer, and a time frame. "Should we build offline mode in the next two quarters?" works. "Product strategy 2027" does not, because every fact about the business is relevant to it.

The scope also sets what counts as a strength. A large enterprise customer base is a strength for an admin-controls feature and irrelevant to a consumer sharing feature.

Where each quadrant's evidence comes from

A SWOT made from memory in a meeting records opinions. Give each quadrant a source before anyone fills it in.

Strengths and weaknesses come from your own product data and research:

• Funnel and retention metrics for the flows the decision touches.
• Support ticket tags and volume.
• Findings from user interviews and usability tests.
• Engineering constraints: what the current architecture makes cheap or expensive.

Opportunities and threats come from outside:

• Competitor releases, pricing pages and changelogs.
• Shifts in platform rules, such as app store policy or browser changes.
• Regulation that affects the market, like accessibility or privacy law.
• Unmet needs that show up in research across customers, not in one account's feature request.

Tag every line with where it came from, and mark the ones nobody has checked yet as assumed. For how much weight an interview finding can carry next to a funnel metric, see qualitative vs quantitative research. A line with no source stays on the page, marked as an assumption to check.

A worked SWOT example for a feature bet

The company here is hypothetical: a mid-size web app for field inspection teams, deciding whether to build offline mode.

Strengths

• Inspectors already complete 70% of forms on mobile (product analytics).
• The form engine stores drafts locally, so part of the sync work exists (engineering review).
• Most accounts are on annual contracts, and none of the large ones renew in the next two quarters (billing data).

Weaknesses

• No conflict-resolution logic; two people editing one form would overwrite each other (engineering review).
• The mobile app has a 3.1 store rating, with sync errors named in a third of low reviews (store reviews, tagged).
• Support has no tooling to inspect a device's local data when a sync fails (support team).

Opportunities

• Interviewees at 9 of 14 accounts described working in basements or rural sites with no signal (interview synthesis).
• Two target industries are moving from paper to digital inspection records (industry reports; assumed, not yet checked).

Threats

• A direct competitor lists offline mode on its pricing page (competitor page).
• Mobile OS background-sync limits make long offline sessions harder to support (platform docs).
• Sales reports two open deals where offline support is on the buyer's requirements list (CRM notes).

The numbers are invented for the example. Each line names its source, and one is marked as unverified.

Turn the grid into options with TOWS

A finished SWOT is a description. The step that produces decisions is pairing the quadrants, a method Heinz Weihrich published in 1982 as the TOWS matrix. Each pairing asks a different question:

Pairing	Question	Example from above
S + O	Which strength lets us take this opportunity?	Local draft storage plus no-signal job sites: extend drafts into full offline completion, uploaded when the device reconnects.
W + O	Which weakness blocks this opportunity, and can we fix it?	No conflict resolution blocks shared forms: limit offline mode to single-owner forms in v1.
S + T	Which strength answers this threat?	No large renewals in the next two quarters: close the gap with the competitor's offline mode inside that window.
W + T	Where do a weakness and a threat combine into real risk?	Sync errors already hurt ratings, and OS limits add more failure modes: invest in sync reliability before scope.

The rows don't agree. S + O and S + T argue for building offline mode now; W + T argues for fixing sync reliability first, since offline mode multiplies the sync failures that already drive bad reviews. Here a reasonable call is a single-owner offline mode (the W + O row) with sync fixes scheduled ahead of it, which answers the competitor without adding shared-form conflicts.

Where SWOT misleads

Everything is weighted the same. A bullet in a box looks as important as every other bullet. Add a rough size to each line (how many users, how much revenue, how likely), or rank within each quadrant before pairing.

The team's own view fills the strengths. People inside a product overrate what they built. Confirmation bias shows up most in the strengths box; requiring a data source for every strength is the practical check.

It's a snapshot. Threats and opportunities change with each competitor release. Date the page, and rerun it when the decision comes back up rather than reusing last year's grid.

It stops at the grid. Name at least one option per pairing before closing the document.

SWOT and the other product strategy tools

SWOT fits early, when a team is deciding whether a direction is worth exploring. Other tools answer narrower questions:

• Opportunity solution trees break a chosen outcome into user problems and candidate solutions. They work at a smaller scale, once the direction is set.
• Porter's five forces look only at the external side, in more depth: supplier and buyer power, substitutes, new entrants, rivalry.
• Customer journey maps locate weaknesses at specific steps of use, which makes the weaknesses box more precise.
• A/B tests check an assumption from the grid once something is built.

More methods for turning research into product calls are collected in the product insights hub.

Frequently asked questions

What is a SWOT analysis used for in product management?

To frame one decision (a feature, a segment, a pricing change) by sorting evidence into internal strengths and weaknesses and external opportunities and threats, then pairing them to generate options.

What is the difference between strengths and opportunities?

Strengths are internal and under your control, like an existing capability or user base. Opportunities are external conditions you can take advantage of but didn't create, like a market shift or an unmet need.

What is a SWOT analysis example for a product?

A feature bet like offline mode for a field-inspection app. Other SWOT analysis examples cover pricing changes (strength: high retention on the current plan; threat: a cheaper competitor tier), and entering a new segment (weakness: no admin controls; opportunity: a segment moving off legacy tools).

How many items should each quadrant have?

Two to five sourced items per quadrant. With more than that, the ranking step gets skipped.

Who should be involved in a SWOT analysis?

People who hold the evidence: product, design and research for strengths and weaknesses, plus engineering for technical constraints and someone from sales or support for competitor and customer signals.

What is a TOWS matrix?

A follow-up step that pairs SWOT quadrants (S+O, W+O, S+T, W+T) to produce strategic options. It was described by Heinz Weihrich in 1982.

Sources: Heinz Weihrich, "The TOWS Matrix — A Tool for Situational Analysis," Long Range Planning 15(2), 1982 · Teresa Torres, Continuous Discovery Habits (2021), on opportunity solution trees.