SWOT Analysis: Why Four Boxes Are the Beginning, Not the Strategy

Four boxes fill a slide. One contains strengths, another weaknesses, another opportunities and another threats. The meeting has produced something tidy. But has it produced a decision?

That is the tension at the centre of SWOT analysis. The framework makes a complicated discussion easier to arrange. It can also make a collection of opinions look more settled than it really is.

A confident phrase such as “strong brand” may sit beside “growing market” without anyone asking how either was established. Once both appear in a diagram, the next conclusion can seem obvious: expand. The missing information has not disappeared. It has simply been given a neat place on the page.

This guide looks at what SWOT can usefully organise, why its origin story deserves care and how to move beyond a completed template. The aim is not to dismiss a familiar tool. It is to stop asking that tool to supply evidence it does not contain.

What the four letters actually organise

SWOT stands for strengths, weaknesses, opportunities and threats. The CIPD's SWOT factsheet describes a planning framework that considers an organisation alongside its environment. Strengths and weaknesses generally concern internal factors; opportunities and threats concern external ones.

That distinction provides a starting arrangement, not a complete explanation of the business.

Owning a machine, for example, is an internal fact. Whether it helps fulfil a particular requirement is another question. A new event taking place nearby is an external development. Whether its organisers need anything the business can sensibly supply is another question again.

The boxes help keep those questions in view. They do not answer them automatically.

A useful way to read the framework is as a set of prompts: what can help, what can hinder, what is changing outside the organisation and which changes matter to the decision?

The invention story is not as tidy as the diagram

Many accounts attach SWOT to a single inventor. Others place it in a particular business school. Those stories should not be repeated as though every detail were settled.

The CIPD factsheet credits Albert Humphrey. A 2023 research paper by Richard W. Puyt, Finn Birger Lie and Celeste P.M. Wilderom takes an archival approach to the history, drawing on records, interviews and literature.

The researchers reconstruct an earlier SOFT approach: satisfactory, opportunities, faults and threats. Their published abstract describes managers identifying issues, grading them with evidence and discussing them with stakeholder needs in view. SOFT was subsequently relabelled as SWOT.

The researchers identify Robert Franklin Stewart as the originator of the approach they reconstruct. That attribution differs from the Humphrey account repeated by CIPD.

This does not require us to announce that every question of attribution has now been closed. It does show why a brief internet origin story is not enough to establish one person's invention, a precise founding moment or a standard recipe followed by every later user.

The interesting practical detail is the process behind the initials. Issues, evidence and discussion mattered. Reducing the exercise to filling a diagram risks retaining the labels while losing the work.

Begin with one decision

“Analyse the business” is a very broad instruction. It can produce a long list with no obvious destination.

A narrower question gives the discussion a purpose. Should an established service be explained more clearly? Is a new product worth investigating? Does a recurring customer difficulty point to a change in the offer?

These are proposed questions, not recommendations for a particular company. The important point is that each creates a different boundary around the information needed.

A capability can be useful for one decision and irrelevant to another. A location can help visitors reach a shop while doing little to explain a delivery service. A distinctive style can suit one audience without appealing equally to everyone.

Write the decision above the diagram. Then ask whether each entry changes how that decision should be considered. If it does not, it may belong in a different conversation.

A strength needs a context

“Good service” is a compliment. It is not yet a useful planning observation.

What does the phrase mean here? Clear explanations? Reliable handovers? Help choosing between products? A particular skill? And what evidence allows the business to say it?

The wording becomes more useful when it describes something a customer can recognise. For an illustrative business, “customers can discuss an uncertain requirement with an experienced member of staff” says more than “excellent customer care”. It still needs to be true.

A claimed strength also needs a limit. Being able to complete a task does not establish unlimited capacity. Having experience does not prove that every future job will be suitable. A capability may be valuable while remaining dependent on materials, time or another person's involvement.

Those qualifications do not weaken the observation. They make it usable. A strength that cannot survive a clear explanation is a fragile basis for a plan.

A weakness should describe a problem, not assign blame

Weaknesses can be the most awkward part of a workshop. People may hear criticism of their work rather than an attempt to understand an obstacle.

Precise language helps. “The website is bad” offers little direction. “Visitors cannot find the information needed before asking for a quotation” identifies a problem that can be inspected.

The next question is whether that problem has been observed or merely assumed. Has anyone reviewed the page from a first-time visitor's viewpoint? Are enquiries repeatedly missing the same detail? Is there a clear route to help?

These are suggested checks, not claims about an actual business. They turn a judgement into something that can be examined.

Do not force every difficulty into an internal failing. Some constraints cannot be removed by a better attitude or a redesigned page. Naming the boundary is more useful than inventing a solution because the diagram requires one.

An opportunity is not simply something a competitor sells

A competing business introduces a product. It appears in the navigation, with attractive images and several variations. That is evidence of an offer. It is not evidence of its sales, profitability or suitability for another producer.

The opportunity question begins after the discovery. Who needs it? What job does it do for them? Can the business fulfil the requirement accurately and at a sensible level of effort?

Demand, capability and presentation are separate questions. A product might be technically possible but awkward to finish or deliver. It might be easy to describe but difficult to support. It might complement an existing offer without justifying a separate page.

Our Time for Designs interpretation is that an opportunity should remain an investigation until those important unknowns have been resolved. Giving it a place in the positive box does not turn it into a launch decision.

Sometimes the useful finding is that an existing service needs clearer explanation. That can be a better next step than adding another product to an already confusing range.

A threat is not a prediction

A potential obstacle belongs in the discussion because it could matter. Its presence does not establish that it will occur.

Keep a recorded event separate from a possible future development. A confirmed change in an arrangement is different from a rumour. An observed competitor offer is different from an assumption that all customers will prefer it.

The useful questions are what would be affected, what evidence is available and which signs would justify revisiting the decision.

A long catalogue of alarming possibilities can make a plan feel thorough without making it clearer. The discussion needs enough detail to identify relevant uncertainty, not a dramatic account of every imaginable problem.

Nor should the framework become an excuse for certainty in the other direction. Deciding not to pursue one option does not establish that the existing arrangement is safe forever.

Keep observation and interpretation on different lines

One simple discipline can improve the document: record what was observed before recording what it might mean.

For a hypothetical service business, the observation could be that several recent enquiries omitted a required measurement. The interpretation might be that the page does not explain how to measure. An alternative explanation could be that customers have not decided the size yet.

The proposed response differs depending on which explanation is right. Clearer instructions may help one problem; a conversation may be more appropriate for the other.

Do not invent enquiry totals to make this example look like a case study. Its purpose is to show the reasoning.

Alongside an important entry, record the source, date and unresolved question. That is less visually elegant than four isolated phrases, but it preserves the information a later reader needs.

The diagram can remain the overview. The evidence record should remain available behind it.

What an illustrative SWOT discussion might reveal

Imagine a business reviewing whether its website properly explains an existing made-to-order service. This is a hypothetical planning exercise, not a description of Time for Designs' performance.

• Possible strength: the business has the relevant capability, subject to checking the actual job requirements.
• Possible weakness: the page does not clearly identify what information a buyer should provide.
• Possible opportunity: a recognisable customer group may need the service, but demand and fit still require evidence.
• Possible threat: another supplier provides a clearer buying journey, without evidence of its commercial results.

The conclusion is not automatically “build a new page”. The first useful action might be to inspect the established page and clarify the offer.

A new page could duplicate an existing answer. More traffic could create unsuitable enquiries. More enquiries could increase clarification work rather than produce quote-ready requirements.

The example becomes useful when it leads to a question that can be checked. The boxes alone do not decide which action is right.

Decide what evidence would change your mind

A planning discussion becomes more disciplined when it allows an option to fail.

Before undertaking a change, describe what would make it worth continuing, revising or stopping. The appropriate evidence depends on the decision. Do not substitute an easy measurement for the outcome that actually matters.

For a website improvement, a useful review might distinguish page visits, enquiries, suitable requirements, quotations and completed orders. Those stages are not interchangeable. Where attribution is unavailable, leave it unresolved rather than assigning a result confidently.

This is a proposed review approach, not a promise of commercial improvement. The framework cannot supply a missing record of what happened.

It should also be possible to explain why an action was chosen. “It appeared in the opportunity box” is not sufficient. The decision needs its own reasoning and the appropriate approval.

The framework has limits

CIPD identifies risks including inadequate data, unfounded assumptions and oversimplification. It also distinguishes capturing information from the analysis that follows.

That is an important boundary. SWOT is not a forecast, an experiment or a substitute for checking specifications. It does not determine a financial outcome, establish legal permission or prove that a customer will buy.

It can help people see which questions they have neglected. It can give a discussion a shared structure. It can make competing interpretations easier to compare.

Its value depends on the quality of that conversation and the evidence brought to it. A professional-looking diagram cannot correct a mistaken premise.

If the issue requires specialist assessment, the diagram should point to that need rather than pretending to replace it.

The useful output comes after the boxes

A completed SWOT can feel like an ending because it resembles a finished document. Treat it instead as an invitation to write a shorter, more demanding conclusion.

What decision remains? What is known? What is uncertain? Which check or limited action should happen next, and who is responsible for it?

For design and communication work, that conclusion can become a much clearer brief. It identifies the customer question, the verified offer and the information needed before artwork or content is prepared.

Our practical interpretation is that the best framework makes the next question sharper. It does not make the answer look inevitable.

Four boxes can begin a useful discussion. The strategy lies in the choices, evidence and follow-through that come afterwards.

Sources and scope

The definitions and brief limitations draw on CIPD's published factsheet. The historical section draws on the researchers' official University of Twente publication record for their 2023 archival study. Their reconstruction is attributed rather than presented as an uncontested single-inventor story.

The examples and practical review suggestions are Time for Designs' interpretation. They are hypothetical, not claimed client results or evidence that SWOT caused the success or failure of a named company. This article does not provide financial, legal or specialist operational advice.