SWOT Retrospective Template for Team Planning

A SWOT retrospective turns a well-known strategy tool on the team itself. Strengths and weaknesses are about the team today: what it's good at and where it struggles. Opportunities and threats come from outside: changes in the product, the company or the tools that could help or hurt. Use it to plan a quarter, not to review a sprint.

The four columns

Inside vs outside. Most SWOT mistakes mix these up. "We have no load tests" is a weakness, not a threat; the team can fix it. "Traffic will double after the partner launch" is outside the team's control: an opportunity or a threat to prepare for. When in doubt, ask: could we change this on our own?

Where it comes from. SWOT's origin is disputed. It's often credited to Albert Humphrey of the Stanford Research Institute (SRI), based on an account he wrote that SRI's alumni newsletter published in 2005; in it, he names Robert Stewart as the research team's leader. A 2023 history in Long Range Planning by Richard Puyt, Finn Birger Lie and Celeste Wilderom traces the method to Stewart's group at SRI and its 1965 "SOFT" approach (satisfactory, opportunities, faults, threats), later relabeled SWOT. Harvard's 1965 textbook Business Policy: Text and Cases described the four parts without the acronym, which is why some accounts credit Harvard.

When to use it (and when not to)

Use it when:

• a quarter is starting and the team is setting goals or OKRs
• the team's scope is changing: a new product area, a merger, a new stack
• leadership asks what your team needs

Pick something else when:

• you're reviewing one sprint. SWOT is too broad for two weeks of work; use What Went Well or Start Stop Continue.
• one project is about to start. A pre-mortem finds that project's risks more sharply than a general Threats quadrant.
• you need to review the last quarter. Run a quarterly retrospective first, then a SWOT to plan the next one.

How to run it live (45 minutes)

1. Start with what's still open. Check Previous Retro and Old / Unresolved Items in the Action Items panel; items unresolved for months are often weaknesses in disguise. Then name the horizon: "the next quarter".
2. Write silently. Set the shared timer for 10 minutes and ask for at least one note per quadrant. The outside quadrants fill slowly; prompt with the company roadmap and vendor announcements.
3. Sort inside from outside. Read Weaknesses and Threats together and move any note the team could fix on its own into Weaknesses. Then drag duplicates together.
4. Vote within quadrants. Set four votes per person and ask for one in each quadrant, so Opportunities don't lose to a long Weaknesses list. Sort by Most Votes.
5. Discuss across quadrants. Which strength helps us take this opportunity? Which weakness makes this threat worse?
6. One action per quadrant. Use a strength, fix a weakness, pursue an opportunity, hedge a threat. Four actions, each with an owner.

How to run it async over a sprint

Opportunities and threats turn up all quarter, in all-hands meetings, vendor emails and other teams' plans. An open board catches them as people notice.

1. Two weeks before quarterly planning: start the retro with SWOT (Try a different format in Start New Retro) and post the horizon as the first note: "Next quarter: what's true about us, and around us?"
2. During the sprint: add notes as you notice them. A deprecation email is a threat; another team's new API is an opportunity.
3. Mid-sprint: the facilitator checks the balance. If Strengths or Opportunities is empty, ask everyone for one.
4. Three days before: the facilitator moves misplaced notes and groups duplicates; everyone votes.
5. The day before: read the CarrotIQ summary of each quadrant. Together they make a one-page team SWOT for leadership.
6. Planning day: a 25-minute call to pick one action per quadrant, or a written round where owners accept by end of day.

To share the result, export the board as a PDF. More in how to run an async retrospective.

12 example prompts

Strengths

1. What do other teams come to us for?
2. What can we do faster than anyone else in the company?
3. What would we miss most if it disappeared tomorrow?

Weaknesses 4. Where does work depend on one person? 5. What part of the code do we avoid touching, and why? 6. Which skill do we keep borrowing from other teams?

Opportunities 7. What's changing in the company that we could use? 8. Which new tool or platform could save us real time? 9. What are customers asking for that nobody owns yet?

Threats 10. What's coming that we can't control? 11. Which dependency would hurt most if it changed? 12. What could pull people off the team this quarter?

For more question sets, see 60 sprint retrospective questions.

Facilitator tip and a common pitfall

Tip: fill the outside quadrants with outside information. Teams know their own strengths and weaknesses, but rarely the company roadmap or vendor timelines. Before the retro, ask the product or engineering manager to add three opportunity or threat notes from leadership meetings.

Pitfall: four lists and no decisions. A SWOT board looks finished once all four quadrants are full, and many teams stop there. A threat nobody hedges is just worry. If time runs short, cut discussion, not decisions.

How AI helps with this format

On Pro AI (and during the free trial), CarrotIQ takes care of the admin:

• Group names. Drag "only one person knows billing" onto "billing PRs wait for one reviewer" and CarrotIQ names the group, for example "Billing Knowledge Silo".
• Summaries. The Sprint Summary summarizes each quadrant and the board: a short team SWOT for the planning doc.
• Suggested action items. CarrotIQ Suggest drafts an action from the notes, weighting the most-voted ones. Run it after the vote, then edit and assign.

Example action items

One per quadrant, each tied to the quarter.

During the quarter, the Previous Retro tab lists these, and Old / Unresolved Items catches anything still open. See retrospective action items that actually get done.

Use this template in Retro Rabbit

1. Start a 14-day free trial. No card is needed.
2. For one retro, click Try a different format in Start New Retro and pick SWOT: it applies to that retro only, and your Team Room keeps its usual columns. To make it the room's format, choose it under "Browse all formats" when you create your Team Room, or later in the Team Room's Settings.
3. Two weeks before quarterly planning, post the horizon as the first note and ask people to add opportunities and threats as they hear of them.

See pricing for plans.

Related formats

• Quarterly retrospective: look back at the quarter before planning the next
• OKR retrospective: check progress on the goals the SWOT shaped
• Pre-mortem template: sharper risk-finding for one project
• Sailboat: a lighter mix of help, drag, risks and a goal
• More formats in Kickoff and planning
• All retrospective templates