A SWOT analysis helps a team examine the internal capabilities and external conditions affecting a specific decision. Its value comes from testing evidence and choosing a response. This article explains the four categories, shows how to avoid confusing assumptions with facts, and works through a practical example you can adapt before committing resources to a new initiative.
What SWOT analysis means
SWOT stands for Strengths, Weaknesses, Opportunities and Threats. Strengths and weaknesses describe internal factors relative to your objective. Opportunities and threats describe external conditions that may help or hinder it. The same factor can matter differently for different decisions, so define the scope before filling the boxes.
CIPD describes SWOT as a diagnostic and planning framework. A completed matrix is an organised view of the situation; it is not a strategy, a financial forecast or proof that a project will succeed. The next step is to compare possible responses and decide what evidence is still missing.
Start with a decision, not a brainstorming session
Replace a vague question such as “What are our strengths?” with a decision such as “Should we introduce an appointment service for business customers?” Specify the customer group, location, planning period and available capacity. This makes it easier to distinguish relevant evidence from interesting background information.
Ask colleagues from operations, finance, customer service and sales to contribute. Give participants time to submit concerns before the meeting. A facilitator should prevent seniority or enthusiasm from turning an unsupported opinion into an accepted fact. Record disagreements as questions to investigate.
Put each factor in the right category
| Category | Useful question | Evidence to look for |
|---|---|---|
| Strength | What relevant capability do we already perform well? | Delivery records, demonstrated skills or reliable capacity |
| Weakness | What internal limitation affects this decision? | Rework, capability gaps or unresolved process delays |
| Opportunity | What external change creates a possible opening? | Customer requests, market evidence or a verified change in demand |
| Threat | What external condition could undermine the objective? | Competitor offers, supplier disruption or changing customer expectations |
An intention to train employees is an action, not a strength. A plan to launch a new service is an option, not evidence of an opportunity. “Competition” is too broad to be useful: identify which competing offer affects which customer decision, and why.
For example, dependence on a single supplier results from an internal choice and may be a weakness, while that supplier suffering a disruption or leaving the market is an external threat. Record the factors separately when they affect the decision, then connect them to an appropriate response. This distinction separates an internal cause from an external event and clarifies what the business can change directly and what it needs to prepare for.

A worked example: appointment-based support
Consider a fictional service business reviewing an appointment option. This is an illustrative example, not an ATMACSS client case. Its experienced team can resolve complex enquiries, but requests arrive through several unconnected channels. Customers have asked for predictable appointments, while a competitor already offers extended opening hours.
The team records expertise as a possible strength, fragmented intake as a weakness, evidenced customer demand as an opportunity, and the competing availability as a threat. It then checks whether expertise is available during the proposed appointment hours. Without that check, the claimed strength may not support the proposed service.
A possible response is a limited appointment pilot with one intake route and a defined escalation owner. An alternative is to improve existing response times before adding appointments. Comparing these options exposes capacity and cost questions that the four-box matrix alone cannot answer.
To make the option testable, assume a 4-week pilot covering 40 completed appointments. The team defines a key performance indicator (KPI) in advance: the percentage of completed appointments where service began within 5 minutes of the scheduled time, with an illustrative target of 95%. If 36 appointments meet the condition, the result is 36 ÷ 40 × 100 = 90%, or 5 percentage points below target. Report cancellations and no-shows separately so the indicator does not hide part of the customer experience.
The operations owner also checks that the pilot has not delayed service for customers outside the appointment system, and reviews staff effort and delivery cost. Better appointments at the expense of other service are not sufficient evidence for expansion. At the end of the 4 weeks, document a decision to continue within available capacity, revise arrangements and retest, or improve existing response times instead of adding appointments. These figures are hypothetical, not a universal benchmark or evidence of preferences across the whole market.
Turn the matrix into choices
Combine factors to generate options. Can an existing strength address an external opportunity? Does a weakness prevent you from responding to a threat? Avoid assigning a project to every box. A short list of coherent choices is easier to assess than a long list of disconnected initiatives.
For each option, document the intended outcome, required resources, main assumptions, accountable owner and decision date. Identify what would make you pause or stop. A small pilot should answer a defined uncertainty, not become an indefinite activity that continues because nobody reviews it.
Prioritise without false precision
Discuss the effect on the objective, urgency and strength of evidence. A numerical score can structure that conversation, but multiplying subjective ratings does not create reliable probabilities. Explain the scale and show the reasoning behind each priority.
Keep an evidence log beside the matrix. Record the source, date, scope and whether an entry is observed or assumed. Customer interviews from one branch may reveal a problem without proving that all branches face it. When evidence is weak, assign a research task instead of presenting the claim as settled.
Review the analysis when the situation changes
Revisit the matrix after a pilot, a material change in demand or a significant operational constraint. Compare the assumptions with what happened. Retire factors that no longer matter, and keep a brief version history so later decisions can be understood.
SWOT works best alongside more detailed analysis. Use customer research to test demand, process analysis to understand delivery problems, and financial modelling to assess affordability. It cannot replace these activities or guarantee business growth.
Keep a short log of unresolved questions
For each assumption that affects the choice, record the verification question, evidence source, person responsible for gathering it and decision it could change. Do not give every question the same priority: start with those that could rule out an option or change the scale of commitment. When evidence arrives, update the relevant factor and explain its effect on the proposed response. This log turns the analysis workshop into practical follow-up instead of repeating the same discussion at the next meeting without new information.
Apply the findings with ATMACSS
Bring your decision question, existing performance evidence and proposed options to a discussion with ATMACSS. Our Strategic Planning & KPIs service can help structure priorities and translate the selected direction into responsibilities and measures. The company strategic plan article explains how these choices fit into a wider plan.

