SWOT Analysis in Project Management
SWOT has an image problem, and it has earned most of it. Run as a general appraisal of a project, it produces four boxes of adjectives: experienced team, tight timescales, new market, competitors. Everybody nods, the sheet is photographed, and nothing that happens afterwards is any different for its existence.
The tool is not the problem. A SWOT with a specific decision attached to it, run by people who will be held to the answer, is one of the fastest ways to surface what a group already collectively knows and has not said out loud. Section 5 of the PMBOK® Guide Eighth Edition lists it among the techniques available, and its usefulness depends almost entirely on three disciplines that take no extra time.
The discipline that makes it work
Attach it to a question. Not the project, but this decision: whether to bid for this contract, whether to take this delivery approach, whether to bring this work back in house. The four boxes only mean anything relative to something you are choosing between, and a group given a question argues about substance while a group given a project produces vocabulary.
Keep the axes honest. Strengths and weaknesses are internal and present tense: things about your organisation, your team and your position that are true today and that you can act on. Opportunities and threats are external and forward looking: things in the market, the client, the supply chain, the regulatory position that you do not control. Entries drift across that line constantly, and correcting the drift is where much of the value sits, because an item that moves from strength to opportunity changes what you can do about it.
Make every entry specific enough to check. Good relationships with the client is not an entry. A named engineering manager at the client who has worked with two of our people for six years is an entry, and it can be examined. The specific version is also the version that shows you something, which the general version never does.
Where it earns its place
Bid and no-bid decisions, where the whole question is whether your position is strong enough against what you can see coming. This is SWOT's natural home and the place where a disciplined hour saves months of expensive effort chasing work you were never going to win.
Choosing a delivery approach, particularly where the honest weaknesses are organisational. A team with no experience of iterative working, in an organisation whose funding arrives annually, is telling you something useful about which approach will actually function, whatever the preference in the room.
Entering a significant supplier relationship, where the external half does the work. Their market position, their other commitments, the possibility of acquisition, the concentration risk if they hold something you cannot replace quickly.
Mobilisation, before a project starts properly, as a structured way of asking what we are good at here and what is coming at us. It is a better opening conversation than a risk workshop, because it includes the strengths, and teams talk more freely about difficulties once they have been asked what they are good at.
A strength with a retirement date
An engineering contractor was deciding whether to bid for a place on a rail framework. The team assembled a SWOT in an hour, and the strengths column opened with their relationship with the client's principal engineer, which everyone agreed was the reason they had won the previous two packages.
The specificity rule turned that entry into something else. Written out properly, the strength was that one of their senior engineers had worked with that individual for eleven years, and that the individual was due to retire in the spring. Nobody had concealed this. It simply had not been in the same conversation as the bid decision before.
The bid went ahead, with two changes. The relationship was treated as a threat with a date rather than as a standing asset, and the proposal was written to stand on technical content that a stranger could assess. They won the place, and the client's new engineer arrived in April. Learning to run an appraisal like this so that a group tells you what it actually knows, instead of what sounds reasonable, is practical tool work that Omega's PMP® Exam Preparation rehearses.
What to do with the output
Convert or discard, the same afternoon. Every entry either becomes something with an owner, which usually means an action, a risk register line or a change to the approach, or it goes. A strength that leads to nothing is a compliment, and a threat with no owner is a worry somebody will have again in three months.
Date it and treat it as perishable. A SWOT describes a position at a moment, and positions move: people leave, competitors bid, regulations arrive. Re-running one before the next significant decision costs an hour, and it is more useful than defending a sheet produced when the situation was different.
For a PMP® candidate, the first question about any technique is what it is for. SWOT supports a judgement about position, which makes it an input to a decision and not a substitute for one. A scenario in which a team has completed an analysis and taken no decision is describing an incomplete piece of work, whatever the quality of the analysis.
The practical version is a whiteboard, four headings, the people who know the client, and a question written at the top before anybody speaks. Anything that survives the specificity test gets an owner before the group leaves the room, and everything else is rubbed out without ceremony.
Interested in going further?
Knowing which technique fits a decision, and how to run it so a group is honest rather than agreeable, is a practical skill that shows immediately in the quality of the calls you make. Omega's PMP® Exam Preparation covers the analytical tools alongside the judgement each one requires.
The PMBOK® Guide Eighth Edition sets out the wider family of techniques this one belongs to, which helps in choosing between them.
Ad · Amazon affiliate link.
References
A187: Retrospectives That Lead to Change
A180: Facilitation Techniques for Difficult Project Conversations
A184: Trend Analysis vs Variance Analysis
A182: Multicriteria Decision Analysis Explained
A161: Expected Monetary Value Explained
PMP and PMBOK are registered marks of the Project Management Institute, Inc.
