Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

A SWOT analysis is a way to examine the strengths, weaknesses, opportunities, and threats that matter to a specific goal. Strengths and weaknesses are usually internal; opportunities and threats are usually external. The framework helps organize evidence and identify strategic choices, but a four-box list is not a strategy until you prioritize its findings and decide what to do.

What SWOT stands for

Each category describes a different kind of factor. Judge every entry in relation to a defined objective: the same condition could help one project and hinder another.

  • Strengths: Internal capabilities, resources, skills, relationships, or other assets that support the objective.
  • Weaknesses: Internal limitations or gaps that may hinder the objective and could be improved or addressed.
  • Opportunities: External conditions or changes that could help the organization, project, or effort achieve its aims.
  • Threats: External conditions that could obstruct the objective or put the project, operation, or mission at risk.

The UK Government’s Futures Toolkit describes SWOT as a practical technique for mapping issues that affect successful delivery of a policy or strategy. The internal-versus-external distinction is useful, but it is not a substitute for stating whose capabilities and which environment you are assessing.

How to conduct a SWOT analysis

  1. Define the objective and scope. State the decision, strategy, policy, project, organization, or activity being assessed. Keep that scope consistent throughout. If you are comparing substantially different options, make a separate SWOT for each.
  2. Gather evidence and perspectives. Review relevant reports, internal information, and changes in the wider environment. Include people familiar with internal capabilities as well as people who understand external conditions. A solo exercise is possible, but a group can surface different views.
  3. Identify internal factors. Consider people, skills, knowledge, budget, technology, geography, legal context, partners, and relationships. Ask what helps delivery and what constrains it. Assess weaknesses on their own terms rather than listing them as simple opposites of strengths.
  4. Identify external factors. Look for changes in economic conditions, technology, demographics, social attitudes, policy, and the wider operating environment. Horizon scanning or trend analysis can help reveal developments that a snapshot of current conditions might miss.
  5. Connect the factors. Ask how internal capabilities and gaps interact with external conditions. A strength may help capture an opportunity or reduce exposure to a threat; a weakness may make a threat more serious or limit the ability to act on an opportunity.
  6. Prioritize and plan. Decide which findings matter most to the objective. Turn them into options and an action plan that identifies priorities, timelines, costs, and required resources. Discuss the findings with relevant people and monitor changes that could affect the plan.

Turn the grid into strategic choices

A TOWS-style exercise makes the connections between the four categories explicit. The University of Kansas Community Tool Box describes four useful pairings:

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.
  • Strengths and opportunities: How could an existing capability help you take advantage of an external opportunity?
  • Weaknesses and opportunities: Could an opportunity help address a limitation, or does the limitation prevent you from acting?
  • Strengths and threats: Which capabilities could reduce exposure to an external threat?
  • Weaknesses and threats: What could limit the effect of a weakness while avoiding or preparing for a threat?

Not every factor needs to pair neatly with another. A mismatch may point to a need for more information, a contingency plan, or a decision to change the objective. SWOT findings can feed into strategic planning or scenario work, but they do not predict what will happen.

Example: assessing a potential partnership

Suppose an organization is considering a partnership to deliver a particular project. The relevant question is not whether the prospective partner is “good” or “bad” in general; it is whether the partner, project, and surrounding conditions support the project’s stated objectives.

  • Strengths are attributes of the partner, project, or activity that help achieve those objectives.
  • Weaknesses are attributes that could cause problems or prevent the objectives from being achieved.
  • Opportunities are external conditions or resources that could help achieve the objectives or improve outcomes.
  • Threats are external conditions that could obstruct delivery or put the intended outcomes at risk.

This framing comes from UK Government charity due-diligence guidance on partnership assessment. It illustrates why each entry needs to be judged against the objective and the specific context, rather than treated as universally positive or negative.

When SWOT is useful—and what it cannot do

SWOT can support strategic planning, policy or project assessment, problem solving, option evaluation, and decisions about how a plan should change as circumstances shift. The University of Kansas Community Tool Box also identifies uses in community health and development, education, and personal growth; CIPD lists activities including workshops, idea generation, product or competitor evaluation, personal development planning, and decision making.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Use it as one part of a decision process, not as a replacement for evidence or detailed analysis. PESTLE analysis can help examine external political, economic, social, technological, legal, and environmental conditions. Benchmarking or scenario work may be more useful when the external landscape is uncertain or contested.

Common mistakes and how to avoid them

  • Stopping at the list: A completed grid captures information, not a decision. Identify important issues, develop options, and assign next steps.
  • Relying on unsupported assumptions: Make the basis for each entry clear. Assessing an opportunity’s or threat’s impact and probability can be difficult; gather suitable information rather than presenting an impression as a fact.
  • Letting one viewpoint dominate: Invite perspectives from people who understand both internal capabilities and the external environment. Groups can also become overconfident about strengths or focus disproportionately on threats, so seek a measured view.
  • Treating the matrix as a forecast: SWOT often describes a current position. Consider how a weakness or threat might change, and whether an opportunity could become a threat as others respond to it.
  • Mixing up internal and external factors: Keep the distinction explicit and tie each entry to the objective. An internal capability is not the same as an external opportunity.

Run it as a workshop or a solo exercise

The UK Government’s SWOT facilitation worksheet outlines a two-hour workshop with an introduction, pre-workshop briefing, discussion of internal factors, discussion of external factors, identification of interrelationships, and a close. For an in-person session, it suggests note pads, pens, a screen, and space to display flip charts; participants can record findings on flip charts or an online whiteboard. Adapt the agenda and materials to the participants and setting. These workshop tools are optional for a solo desk exercise or virtual session.

For each entry, record enough context to make it useful later: what the factor is, how it relates to the objective, what evidence supports it, and—where relevant—its likely impact, probability, time horizon, and the organization’s ability to influence it. These details make it easier to compare issues and turn the analysis into a workable plan.

Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Support on Ko-Fi

Where the framework’s history is attributed

CIPD’s factsheet dated 20 May 2026 attributes the framework’s history to Albert Humphrey, whom it says led a Stanford research project in the 1960s and 1970s using data from leading companies involved in long-range planning. This is CIPD’s attribution; it should not be taken as independently established authorship.

Special offer. See more information about Outbyte and uninstall instructions. Please review EULA and Privacy policy.

Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.