SWOT Analysis in Project Management: Steps, Template (2026)

Project SWOT analysis is a review of one project’s internal strengths and weaknesses and its external opportunities and threats. You run it at kickoff and on named triggers, and it ends with an owner for every high-scoring item.

The Project Management Institute (PMI) calls opportunities positive risks and threats negative risks. Because a threat is a risk, each one you list is a ready entry for the project’s risk register.

A company-level analysis differs from a project one in owner, scope, and time horizon. Leadership runs a company SWOT as part of strategic management, to find a competitive advantage.

A project manager (PM) runs one on a single project to test whether its scope, team, and budget hold. Store the project version with the project’s plan, bookings, and budget in your project management tool.

SWOT analysis factors fall into two groups, depending on whether the team controls them. In a 2×2 SWOT matrix, internal factors fill the top row and external factors fill the bottom row.

Opportunities and threats come from the external environment: the client’s business environment, vendors, and regulators. If the team can change an item before the project closes, it is internal.

If it depends on the client, a vendor, or a regulator, it counts among the external factors.

Run a SWOT analysis at project kickoff, before bookings are locked, and again whenever a named trigger fires. Hold the first session after the SOW is signed and before you finish project planning.

By then, the project initiation phase has produced the SOW and the project charter. Rebooking a person or amending a clause still costs nothing at this stage.

In Productive, add the SWOT session and its follow-up tasks to your kickoff project template. Project templates copy their tasks, assignees, and custom fields into every new project.

When the project closes, copy the strengths that held and the weaknesses that caused overruns into the estimate notes. The next similar project’s SWOT then starts from items your team has already tested.

Re-run the analysis after a margin drop, a big change request, a key person’s absence, or a new approver. You priced a margin at kickoff, and halfway through you need to know whether it is still there. Use these example thresholds or set your own:

Run a project’s SWOT analysis by naming the decision, gathering evidence, holding a workshop, scoring items, and assigning owners.

Name the decision the SWOT must inform before anyone lists an item. Open the signed SOW or the project brief and list the three things it fixes: scope, dates, and fee. Then write one sentence naming the decision, with the scope, the date, and the margin in it.

Example: whether to commit to 25 page templates and 180 migrated pages in 12 weeks at a 30% margin.

That sentence ties the project objectives and project goals to the agreed project scope. A SWOT analysis for project management starts from this decision sentence. If the PM cannot write it in one sentence, postpone the session until the SOW answers it.

Two working days before the workshop, send everyone an evidence pack with four documents:

Use the pack as your risk identification input to identify risks before delivery starts. Add a short form that asks the team and the client contact for items in each quadrant.

Past timesheets show only what already happened, so include forward bookings and the forecast as well. Your team cannot protect a budget it has never seen, so everyone in the room reads the same forecast.

Any item raised without one of these sources goes into an Unverified column and cannot take a top-three slot.
In Productive: Forms collect input from the team and the client before the session.

The resource planner shows who is booked and who can take on more work. Use it to check who is booked next month. Forecasts show cost and profit margins based on scheduled work.

The PM runs the SWOT workshop with the project team’s delivery leads, the account lead, and a finance partner. Add subject-matter experts for the riskiest work, such as the migration lead or a business analyst. Invite the client sponsor, one of your key stakeholders, for the last 20 minutes. Do this when the client’s management team will review the output.

Split the 60 minutes into four blocks:

Silent listing comes before open brainstorming because writing alone first keeps the first speaker’s items from setting everyone’s list. Save open brainstorming for the round-robin, which keeps the read-out a team effort.

The session passes when every item has a quadrant and a source. Anything unsorted at minute 60 goes into the Unverified column.

In Productive: the AI Notetaker can record the session and its decisions. It links recordings and notes to the project, so the discussion and the matrix are in the same project.

Take the sorted matrix from Step Three and score each item for impact and likelihood from 1 to 5. Multiply the two and enter the score in the scoring log from the template.

Multiplying impact and likelihood is standard in qualitative risk analysis. It gives decision-making in the room one number per item. Score strengths and opportunities the same way: impact on the decision times the likelihood that the item plays out.

A threat that has not happened yet still gets a likelihood score, so it can outrank today’s problems.

Project risks and other items at 12 or more get an owner in Step Five. Treat 12 as a starting point and adjust it once you have scored a few projects. Keep at most three items per quadrant at 12 or more. If more qualify, re-score that quadrant with the finance partner.

Scoring is the part of the SWOT technique that sets the order of work. The step passes when every quadrant is ranked and no item at 12 or more lacks a source.

Turn every item at 12 or more into an owned action before the session ends. Each one gets an owner, a due date, and a trigger. Weaknesses and threats become risk register entries with six fields: ID, description, owner, trigger, response, and review date. Move each threat into your risk register on the day of the session.

Strengths and opportunities become tasks in the plan, such as a phase-two proposal with a date. Together, these entries and tasks are the project’s action plan. Log over-servicing the same way: its trigger is the first client request outside the SOW.

Each register entry’s response field holds the risk mitigation step, plus a contingency plan if the trigger fires. Review the open entries at every weekly status meeting, which is where risk management happens on a live project.

The review also shows which risk management strategies held up and which did not. An item at 12 or more without an owner or a date reopens at the next status meeting.

In Productive: the AI Notetaker turns action items from the session into tasks with assignees. You can track threats as tasks in a Risks task list, with task custom fields for impact and likelihood.

This SWOT analysis example follows one project SWOT for a fictional agency, from the matrix to the owners. The agency is redesigning a client’s website in 12 weeks at a fixed fee.

The scope covers 25 page templates and 180 pages moved to a new content management system (CMS). Treat it as a SWOT project management example: copy the structure, then swap in your own items and sources.

Each item in this SWOT matrix cites the document it came from.

Five of the nine items are external factors. The two late-copy items show the sorting test. The client’s lateness is a threat, and the missing SOW clause is the team’s weakness. Vendor discounts count as opportunities only when they carry a date, like O1’s quarter-end deadline. Regulatory changes such as T3’s accessibility requirement are threats because the team cannot control them.

Two threats depend on the client’s management team: the content lead’s schedule and the legal review. The project team can act on all four internal items before kickoff.

Check W1 first: a booking over 100% appears in the resource plan weeks before it causes a missed date. If your current tool cannot show that, compare capacity planning software before the next kickoff.

Eight of the nine items score 12 or more, so eight get owners.

W1 has the highest score. The senior developer is booked at 48 hours a week against 40, which is 8 hours over. Over 4 weeks, that is 32 hours to move. The second front-end developer is booked at 70%, which leaves 12 hours a week.

Across weeks 3 to 6, that is 48 free hours, enough to take all 32.

W1 and T1, the highest-scoring weakness and threat, are where cost overruns would start. T2 is how unplanned pages turn into cost overruns, which is why its trigger is the first request.

You turn SWOT findings into strategies by pairing each internal item with an external one in a TOWS matrix. SO uses strengths to take advantage of opportunities, and WO takes advantage of opportunities to overcome weaknesses.

ST uses strengths to avoid external threats, and WT minimizes weaknesses and avoids threats. Each strategy pairs one internal item with one external item, which ties strengths and weaknesses to a named event.

Applied to the redesign, the four pairings turn the scored opportunities and threats into dated actions.

ST and WT are the two answers to external threats, and WT goes first because it changes the contract.

Copy this SWOT matrix into a project doc and replace each guidance line with items from your own project.

Fill one SWOT analysis matrix per project, so every item ties to a single SOW. An empty cell is fine: the SWOT framework does not require four lists of equal length. In Productive, keep the SWOT analysis template as a table in a project Doc.

Use these guiding questions to fill each quadrant:

Log every item here after the workshop, one row per item.

The most common SWOT method mistakes are company-level scope, misfiled factors, unsourced items, unranked lists, and findings nobody owns.

Items like “strong brand” or a competitive product analysis describe the company and change nothing on this project. Put the decision sentence from Step One at the top of the matrix. Delete any item that would not change that decision.

Filing late client copy under weaknesses hides who has to act. Apply the sorting test: the lateness belongs to the external factors. Weaknesses are internal factors, so the weakness is whatever in your SOW leaves the team exposed to it.

Project strengths without a source, like “experienced team”, give the session nothing to check. A sourced version reads: three CMS migrations in 12 months, each within 5% of estimate (closeout reports). The source rule from Step Two applies to every cell.

Leaving a flat list of strengths, weaknesses, and threats unranked means the team works on the easiest item first. Score every item as in Step Four, and give owners only to items at 12 or more.

Findings nobody owns turn into cost overruns nobody planned for. This happens when the matrix is presented at kickoff and never opened again. Apply the owner, date, and trigger rule from Step Five. Then run a five-minute SWOT review at each status meeting.

SWOT analysis has three limitations: it captures one moment, rests on judgment, and leaves cost and schedule unsized.

Use a different tool when the job is tracking, market context, or a go/no-go call:

For other options, browse a wider set of project management techniques.

The workshop takes 60 minutes. The PM also pulls the evidence pack beforehand, from documents the team already keeps.

Yes. Cut it to a 20-minute session with the PM and one delivery lead, and score only weaknesses and threats.

Share the opportunities and threats tied to client inputs, such as copy dates, approvals, and scope requests. That way, the client’s owners can act on them. Keep internal weaknesses, such as staffing, inside the team.

PMI’s PMBOK Guide lists SWOT analysis as a data analysis technique in the Identify Risks process. The scoring step matches qualitative risk analysis, and the risk register records the results.

A SWOT analysis changes the plan only when each item has a source, a score, and an owner. When bookings, budgets, and tasks are in separate tools, you rebuild the evidence pack by hand. All-in-one project management software keeps them in one system, so the evidence is current when a trigger fires.

If you want to see bookings, forecasts, and SWOT follow-up tasks together, book a Productive demo.