SWOT Analysis for Projects: How to Use It in Planning

What is a SWOT analysis for a project?

swot analysis for projects is a key topic in modern project management and teamwork. A SWOT analysis for a project is a structured assessment of the internal strengths and weaknesses the project team controls, and the external opportunities and threats it does not. It is scoped to one project and one decision — usually “should we proceed, and how should we approach delivery?” — and its output should be a small set of strategies, not four lists.

The internal/external split is the part people get wrong most often. Strengths and weaknesses are things the project team owns: skills, availability, existing code, relationships, budget flexibility. Opportunities and threats come from outside: market timing, vendor pricing, regulation, competitor moves, platform changes. If you cannot change it with a decision this quarter, it is probably external.

Why does SWOT so often produce nothing?

Because it is usually run as a brainstorm rather than an analysis, and the research on this is unusually blunt.

Terry Hill and Roy Westbrook published a study in *Long Range Planning* in 1997 titled “SWOT analysis: It’s time for a product recall.” They examined the UK Department of Trade and Industry’s Manufacturing Planning and Implementation Scheme, covering 50 companies. Twenty used SWOT, with 14 different consultancies involved. The lists were long, general, and unprioritised, and in most cases nobody used the outputs in later stages of the strategy process.

Nearly thirty years later, the failure mode is recognisable: a list of adjectives, no evidence, no owner, no decision. The method is not broken; the facilitation is.

Two design choices separate a SWOT that gets used from one that becomes a photo:

1. Cap each quadrant at five items. A long list hides the items that matter. If you have twelve strengths, you have not decided which three you will rely on.
2. Require evidence for every item. Each entry gets a number, a date, or a specific precedent. Anything that cannot be evidenced gets moved to an “assumptions to test” list.

> Important note: A SWOT without a decision attached is a workshop activity, not planning. Decide before the session which decision the output will inform — proceed or pause, build or buy, one vendor or two, accelerate or descope.

How do you run a project SWOT in 90 minutes?

Five steps, with time boxes. The preparation matters as much as the session.

Step 1: Send an evidence pack 48 hours ahead (20 minutes of prep)

Give participants the documents that make opinions checkable: the statement of work, the resource plan with named people and allocation percentages, the last two post-mortems, and the vendor quotes. Ask each person to arrive with no more than three candidate items per quadrant and the evidence behind each.

Step 2: Separate internal from external, out loud (10 minutes)

Post the four boxes and read the definitions. Then have the group sort the pre-submitted items. The argument about whether “the client’s approval process” is a weakness or a threat is worth having, because the answer determines whether you can act on it or only prepare for it.

Step 3: Build the four lists with evidence, capped at five (25 minutes)

Work quadrant by quadrant. For each item, the facilitator asks one question: how do we know? Items that survive get a short, specific phrasing. Items that do not survive go to the assumptions list, which is itself a useful output.

Step 4: Cross the quadrants into strategies (35 minutes)

This is the step that most workshops skip, and the only one that produces anything actionable. Pair each internal item with an external one and write a strategy for each of the four combinations.

Step 5: Keep three to five strategies with an owner, a first step, and a date (20 minutes)

Score the candidate strategies on value and feasibility, choose three to five, and assign them. Everything else is recorded but not resourced. A SWOT that produces eleven strategies has produced none.

What belongs in each quadrant?

The table below is the working reference for a project-level SWOT. The example column uses a CRM migration project so the items stay concrete.

Two rules of thumb make the quadrants useful:

Opportunities must have a deadline. “Growing demand for integrations” is a market observation. “Vendor credit expires 30 June, worth $42,000” is an opportunity you can act on. If it has no date, it will never be scheduled.

Threats must be sized. A threat without a number cannot compete for attention against one with a number. “Licence price rises 12% at renewal on $340,000 of annual spend” is $40,800 — a figure you can compare to the contingency reserve.

How do you turn the four boxes into strategy?

You cross them. The TOWS matrix, published by Heinz Weihrich in *Long Range Planning* in 1982, pairs internal and external items to generate four families of strategy. The name is SWOT reversed, and the logic is the reverse too: SWOT describes, TOWS decides.

Each cell should produce at most two strategies. If a cell is empty, that is a finding worth noting: an empty SO cell means your strengths do not line up with where the opportunity is, which is often the most important output of the whole exercise.

Write each strategy as a sentence with a verb, an owner, and a cost. “Leverage our integration experience to launch the payments module before the competitor’s June release, using the existing adapter library. Owner: platform lead. Incremental cost: 80 engineer-hours.”

What does a full worked example look like?

A mid-sized retailer is migrating from a legacy CRM to a cloud platform. Budget $620,000, 9 months, 6 internal engineers plus a systems integrator.

The SWOT, capped and evidenced:

• Strengths: two engineers with two prior migrations; an existing integration library covering 60% of required connectors; a sponsor with budget authority.
• Weaknesses: no automated tests on the billing module; the data analyst who owns customer segmentation is 50% allocated elsewhere; no in-house experience with the target platform’s permission model.
• Opportunities: vendor migration credit of 15% if the contract is signed by 30 June ($42,000); a competitor’s CRM outage in Q1 created client interest in switching; the integrator has a reference implementation for this sector.
• Threats: licence price rises 12% at renewal on $340,000 of annual spend ($40,800); a regulatory change on consent tracking lands in Q4; the integrator’s two senior consultants are also booked on a competing project.

Now cross them. Three strategies survive scoring:

SO-1: Pull the payments module forward. Use the existing integration library to deliver payments in month 4 instead of month 7, ahead of the competitor’s launch. Revenue effect: $85,000 of subscription billing starts three months earlier. Incremental cost: 80 engineer-hours at $95 = $7,600. Net benefit roughly $77,400, and the largest single item in the plan.

WO-1: Use the vendor credit to fund the automation gap. Apply the $42,000 migration credit to contract a test-automation specialist for ten weeks at $24,000. Without it, the billing module’s 0% coverage is a credible three-week slip, and three weeks of delayed billing is worth about $45,000. Net position: +$21,000, plus a materially lower schedule risk.

ST-1: Lock the licence price now. Sign a 24-month renewal at the current rate before the increase lands, removing $40,800 of exposure that the contingency reserve ($25,000) cannot fully cover. Cost: a commitment, not cash.

Note what the exercise produced. Not forty-two sticky notes — three moves with costs, owners, and dates, two of which pay for themselves and one of which closes a $15,800 gap between exposure and reserve.## Should you weight the items?

Weighting is optional, and worth doing when you need to compare options quantitatively or when the group disagrees about which factors matter most. Give each item a weight that sums to 1.00 within its quadrant, rate it from 1 to 5, and multiply.

Read the two totals together, not separately. A readiness score of 4.15 against a drag score of 3.65 says the project can proceed, but the margin is thin enough that the billing weakness deserves a funded mitigation rather than a monitoring note. That is exactly the conclusion WO-1 acted on.

Weighting has a known weakness: the weights are judgements, and multiplying two judgements produces false precision. Use it to structure a conversation, not to settle an argument.## How is a SWOT different from a risk register or PESTLE?

They answer different questions and should feed each other, not compete.

The practical workflow runs left to right: PESTLE or market scanning produces external factors, the SWOT adds internal capability, TOWS produces strategies, and every threat that survives becomes a scored entry in the risk register. Skipping the last step is how a workshop full of insights turns into a project with no mitigations.

What are the common mistakes?

• Running one SWOT for the whole organisation and applying it to a project. Scope must match the decision. An enterprise SWOT will not tell you whether to hire a tester.
• Confusing weaknesses with threats. “The deadline is tight” is a constraint, not a weakness; “the regulator may change consent rules” is a threat. Mis-sorting makes both unactionable.
• Listing internal actions as opportunities. “We could improve onboarding” is a strategy, not an external condition. Put it in the TOWS, not the quadrant.
• No evidence column. The single highest-leverage fix, and the cheapest.
• Never revisiting it. Conditions change; a SWOT built at kickoff and never updated describes a project that no longer exists.

When is a SWOT the wrong tool?

Be honest about the limits. A SWOT is a qualitative, high-level snapshot built on judgement, and it does not size anything. It is the wrong choice when:

• You need a quantified decision, such as choosing between three capital options. Use a business case with discounted cash flow or a weighted scoring model.
• The question is purely about external environment change. Use PESTLE or scenario planning.
• The question is about competitive position and durable advantage. Use VRIO or Porter’s five forces.
• The team is in crisis and needs decisions this week. A SWOT takes 90 minutes and produces strategies, not a recovery plan.
• The culture punishes candour. A weaknesses list produced under threat creates false confidence.

The trade-off is consistent: SWOT is fast, cheap, and communicative, and it is shallow, subjective, and unsized. Use it to align a group and choose a direction, then fund the choice with quantitative tools.

How do you keep a project SWOT alive?

Two habits are enough. Revisit it at every stage gate — fifteen minutes, one question: which items have changed? Then review each strategy at the weekly meeting, because a strategy with no task attached is a sentence, not a plan.

The logistics usually defeat the habit. When the SWOT lives in a slide, the strategies in a business case, and the actions in a task board, the review requires three documents and a memory. Keeping the quadrants, the strategies, and the resulting tasks in one workspace makes the fifteen-minute review possible.

That is the workflow Doitify supports: a project brief, a SWOT or strategy note, and the resulting tasks with owners and dates in the same place, so a strategy becomes a task rather than a line in a document nobody reopens. We build the product, so read that as a description of scope; a shared document plus a disciplined task board covers the same ground for a small team.

Conclusion

A project SWOT is a 90-minute investment that either saves a quarter of misdirected effort or produces a JPEG. The difference is almost entirely in three habits: cap the lists, demand evidence, and cross the quadrants into strategies with owners and costs.

Do that, and the output resembles the retailer example — three moves, two of which pay for themselves, one closing a funding gap you did not know you had. Skip it, and the workshop will still feel productive; it just will not change what anyone does on Monday.

If this post on swot analysis for projects was helpful, you might also enjoy When Should You Stop Managing Projects in Excel? and Employee Onboarding Project Template.