How to Run a SWOT Analysis for a Project
A SWOT analysis helps a project team separate what it controls from what it does not, surface risks early, and turn discussion into owned next steps. This guide explains the four quadrants, when the exercise is worth doing, and how to move from brainstorm to action plan.
What a SWOT analysis is
SWOT stands for Strengths, Weaknesses, Opportunities and Threats. It is a strategic planning exercise, usually shown as a four-part matrix, for examining a project, business plan, content strategy or individual capability.
Internal factors are largely within your control, such as skills, assets, resources and competitive advantages. They map to Strengths and Weaknesses. External factors sit outside your control, such as market shifts, economic changes or major events. They map to Opportunities and Threats.
In project management the value is practical: naming risks and growth areas early lets the team shape a plan that improves the chance of success, rather than discovering the same issues mid-delivery.
The four quadrants, with project examples
Strengths: internal factors that support success. Examples include prior experience with a similar application, clear client decision authority, leadership backing for a digital strategy, contingency in the budget, a fully staffed content team, detailed product specifications, or a completed brand redesign.
Weaknesses: internal gaps that could hinder success. Examples include a team that has never worked together, new client leadership, staff split across two projects, missing content or media resources, many stakeholder layers, limited funding with a spend-by date, legal review for all content, or mismatched project tools. Agree in advance which weaknesses are appropriate to raise with a client and which to handle internally, so expectations about availability and response time are clear.
Opportunities: external possibilities that could help or rescue the project if acted on. Examples include moving an experienced team member onto the project, opening new revenue channels, securing a vendor discount or additional grant, hiring client-side support, meeting real users at a conference, or generating new leads. Keep these concrete and realistic, using your strengths and weaknesses as prompts.
Threats: external factors that could damage success. Examples include a competitor launching a similar product faster, a recently released and potentially buggy codebase, an unresponsive vendor, a team member on leave for three months, blocked access to stakeholders, or no access to users.
Why teams use it
Done well, the exercise can: surface weaknesses and gaps early so they can be addressed proactively; start the project on a positive note by recognising strengths and opportunities; give client expectations another chance to emerge before they become late scope changes; reveal possible phase-two work and new revenue; create a shared way to raise red flags without one person always delivering bad news; and build open, collaborative communication between delivery and client teams.
The benefit depends on how the analysis is run and, crucially, what happens afterwards.
When to skip it
Consider skipping it when: you cannot bring together a diverse stakeholder group from both sides; either side cannot be honest about weaknesses and threats; resources are too limited to act on what you uncover; you are repeating familiar work for a repeat client with no new problem or revenue stream; or scope and goals are unclear, in which case definition workshops should come first. In those conditions a SWOT tends to be vague or unactionable.
Eight-step workshop checklist
- Set the goal. State why you are doing the analysis and what decision it should inform, so you can choose the right approach and participants.
- Choose stakeholders. Aim for a diverse group across levels and organisations who will participate fully, honestly and constructively. Around ten or fewer participants usually keeps focus.
- Pick a tool. A classic matrix in a document or slides suits a single meeting. For remote or async input, use a shared board or whiteboard so ideas can be added before, during and after the session and later converted into tasks.
- Prepare people in advance. Share the goal, why each person was chosen, how the session will run, what preparation is expected and how long it will take, access to the tool, what happens next, and thanks for their time and input.
- Run the workshop. Brainstorm specific items in each quadrant, keeping the format simple rather than over-explaining internal versus external theory. Pre-fill two or three items per box to start discussion; if the room stalls, allow ten minutes of silent thinking. Starter prompts include: What do customers value? What expertise and in-house resources exist? What advantages do we hold? Where are knowledge gaps or hard limits? What resource or tool changes would help? What are competitors doing? Do we depend on vendors or untested tools?
- Prioritise and confirm. Rank items, focusing especially on opportunities and threats. Ask which items would affect the project most, which you can actually act on, and which need more budget. Then clean up the document and circulate it for confirmation.
- Build an action plan. Start with internal factors you control — maximising strengths and mitigating weaknesses — then agree responses to external opportunities and threats with your main stakeholder. Give every action an owner and deadline, and report progress back.
- Revisit. Check the analysis during and at the end of the project to see what was achieved and what can still be addressed.
Worked example: marketing website build
A new marketing website with a large lead-capture component connected to Salesforce illustrates how the quadrants interact. Strengths include several completed Salesforce integrations, top-priority status with permission to pause other work, a core team that has done a redesign before, strategists available for discovery, and an approved new brand with assets ready.
Weaknesses include little user data, an immovable timeline, a team new to working together, recent changes in the top three leadership roles, no imagery for a key feature until launch, and a Microsoft-only document workflow for a Google-accustomed team.
Opportunities include the Salesforce contractor offering to scale up, funding already identified for two further phases, other developers who can cover builds except the integration, a previous revenue-generating resource library that could be reused, and evidence that 75% of visitors do not go beyond the homepage.
Threats include internal disagreement over lead-capture workflow, first-time Salesforce use by the client, a competitor's new website, a four-month launch date against an estimated six months of work, a post-holiday launch, and a development team finishing another project that often misses deadlines.
A matrix presents this clearly in a meeting, but a board format makes prioritisation, ownership, deadlines and notes easier to manage afterwards. Use the matrix to decide, then convert the priorities into tracked tasks.
Templates
Choose the format that matches how you will use the findings: a planner with example questions to guide discussion, an editable one-page matrix document for the workshop, or a presentation format for sharing final findings with the team or stakeholders. {{OWNER_TEMPLATE_FILES}}
| Quadrant | Control | Question to ask | Example from the website project |
|---|---|---|---|
| Strengths | Internal | What can we rely on? | Several completed Salesforce integrations |
| Weaknesses | Internal | What gaps could hinder us? | Little user data collected yet |
| Opportunities | External | What could help if we act? | Contractor offers to scale up team |
| Threats | External | What could hurt us? | Four-month date versus six-month estimate |
Illustrative example only; adapt items to your own project.
Frequently asked questions
What is the difference between internal and external SWOT factors?
Strengths and weaknesses are internal and largely within your control; opportunities and threats are external and largely outside it. That distinction helps you decide what to act on directly and what to plan around.
When should a team skip a SWOT analysis?
Skip it when you cannot gather a diverse stakeholder group, participants cannot be candid about weaknesses and threats, you have no capacity to act on findings, the work is a familiar repeat with no new problem, or scope is so unclear that definition work should come first.
Should I use a matrix or a board for a SWOT analysis?
A matrix works well for discussion and presentation. A board or task list works better when you need owners, deadlines, notes and follow-up tracking for each prioritized item.