Retrospective Techniques: 20 Formats Beyond Start/Stop/Continue

Start/Stop/Continue is not a bad retrospective format. It's a fine retrospective format used every Sprint for two years straight without variation. At that point it becomes furniture — present, unnoticed, serving no real function.

Every facilitation format has a lifespan. Familiarity breeds routine, and routine breeds autopilot. When a team knows exactly what's coming before the retrospective starts, the retrospective is no longer generating new insights — it's confirming existing ones.

The solution isn't to change formats for novelty's sake. It's to match the format to what the team actually needs right now: emotional processing, systemic analysis, creative problem-solving, or accountability. Here are 20 formats organised by what they're best at.

Formats for Emotional Processing

Use these when team morale is low, something difficult happened, or trust needs rebuilding before you can talk productively about anything else.

1. Mad Sad Glad

The simplest emotional retrospective. Three columns: Mad, Sad, Glad. Each person writes sticky notes for each category based on the Sprint. Quick to run, low-barrier, reveals what people are carrying before moving into analysis.

When to use: After a difficult Sprint, a production incident, a missed deadline, or when energy in the room is low. Good for new teams where psychological safety is still being established.

2. Heard Seen Respected

Slower and deeper than Mad Sad Glad. Three rounds: When did you feel heard? When did you feel seen? When did you feel respected? The third round is the most powerful — respect is often where professional boundaries are crossed without anyone naming it.

When to use: When team relationships are strained, when someone has been marginalised, or when interpersonal dynamics are affecting delivery but nobody's naming it.

3. The Sailboat Retrospective

Draws a sailboat with four elements: wind (what's propelling us forward), anchors (what's slowing us down), rocks under the surface (risks ahead), and an island (our destination/goal). The visual metaphor makes abstract team dynamics concrete.

When to use: When a team has been running the same text-based formats for too long. The image generates different conversations than columns of sticky notes. Works especially well with visual thinkers.

4. Hot Air Balloon Retrospective

Similar to Sailboat but with different metaphor: hot air (what lifts us), sandbags (what weighs us down), clouds (obstacles ahead), sunshine (what we're aiming for). The sandbag framing is often more concrete than "anchor" — it names specific things the team can cut loose.

When to use: Interchangeable with Sailboat. Prefer Hot Air Balloon when the team needs to name things they want to consciously drop — the "cutting the sandbag" image is powerful.

Formats for Systemic Analysis

Use these when the team keeps encountering the same problems, surface-level fixes aren't working, or you need to understand root causes rather than symptoms.

5. Five Whys Retrospective

Structure the entire retrospective around root cause analysis. Identify two or three significant issues, then run the 5 Whys on each: Why did this happen? Why? Why? Why? Why? By the fifth why, you're usually at a systemic cause rather than an individual failure.

When to use: When the team is confident about what the problems are but keeps implementing solutions that don't stick. The issue is almost always that the real cause hasn't been named.

6. Timeline Retrospective

Draw a timeline of the Sprint on the board. Each team member adds significant events, moments of high or low energy, and key decisions. The result is a shared picture of the Sprint's emotional and factual history — which often reveals patterns invisible when looking at just the start and end states.

When to use: After complex Sprints with many moving parts. Particularly valuable when different team members had very different experiences of the same Sprint.

7. Starfish Retrospective

Five categories: Keep Doing (working well, maintain), Less Of (doing too much, reduce), More Of (promising, increase), Stop Doing (not working, eliminate), Start Doing (should try, not doing yet). More nuanced than Start/Stop/Continue because "Less Of" and "More Of" acknowledge gradients rather than binary switches.

When to use: For teams that find Start/Stop/Continue too blunt. The gradient categories generate more precise action items.

8. DAKI Retrospective

Drop, Add, Keep, Improve. Similar to Starfish but with an explicit "Improve" category that makes enhancement — not just addition or elimination — a first-class citizen.

When to use: When the team has specific things working at 70% that could be pushed to 90% with small changes. The "Improve" category unlocks different conversations than "More Of."

9. Force Field Analysis

Identify one specific goal or change you want to make. Then map: driving forces (what's pushing you toward it) and restraining forces (what's pushing you away). The exercise reveals why changes that seem obvious still don't happen — the restraining forces are usually bigger than they appear.

When to use: When a specific improvement isn't happening despite repeated agreement. The force field reveals the resistance that keeps pulling the team back to the status quo.

10. Speed Car Retrospective

Racing car metaphor: engine (what powers us), parachute (what slows us down), road (path ahead), bridge-out (risks). The car framing makes the question "what's slowing us down?" feel mechanical rather than personal — which makes it easier to answer honestly.

When to use: For teams where the Sailboat feels stale, or where there are significant performance/speed concerns. The racing car frames the conversation around momentum.

Formats for Action and Accountability

Use these when the team generates great insights but follow-through is weak, or when you need to produce high-quality action items rather than good conversation.

11. 4Ls Retrospective

Liked, Learned, Lacked, Longed For. The "Lacked" and "Longed For" categories are more specific than "what could be better" — Lacked identifies specific missing resources or information, while Longed For surfaces unexpressed wishes that often reveal underlying needs.

When to use: When you want richer data than positive/negative. The "Longed For" category often produces the most interesting and actionable insights.

12. The Speedboat

Similar to Sailboat, but focused on speed to a destination. The boat represents the team, and items attached to it are anchors slowing progress toward the release or goal. Teams estimate how many knots each anchor is costing them — the numerical estimate creates prioritisation conversations that sticky notes alone don't.

When to use: When teams have many complaints and need help prioritising which to address first. The "how much is this costing us?" frame creates better prioritisation than voting alone.

13. What? So What? Now What?

A Liberating Structures format with three rounds: What happened (factual observations), So What (interpretation and significance), Now What (concrete next steps). The structure prevents teams from jumping straight from observation to action without the interpretation step.

When to use: For teams that either spend too long on data without reaching decisions, or jump to decisions without understanding the data. The three phases enforce a productive sequence.

14. Working Agreements Review

Not a traditional retrospective format, but deeply useful: review the team's existing working agreements explicitly. Which ones are we honouring? Which have we let slide? Which no longer serve us? Which do we need but don't have?

When to use: Every 3–4 Sprints, or immediately after a sprint where interpersonal friction affected delivery. Working agreements drift without review.

Formats for Creative Problem-Solving

Use these when the team is stuck in established patterns and needs new thinking, or when you want to approach familiar problems from an unfamiliar angle.

15. Pre-Mortem Retrospective

Imagine the project or next Sprint has failed. It's 6 months in the future. The product is cancelled, the team disbanded. What went wrong? Working backwards from hypothetical failure surfaces risks and assumptions the team is too close to see clearly.

When to use: At the start of a new project, before a high-stakes release, or when the team feels overconfident. The failure frame gives people permission to voice concerns they'd otherwise suppress as "too negative."

16. The Worst Possible Idea Retrospective

Use Worst Possible Idea to generate the opposite of your intended outcome. What would make the next Sprint a complete disaster? Then reverse each answer. The reversal process often produces better ideas than straightforward brainstorming because it bypasses the internal censor.

When to use: When the team is generating the same ideas every Sprint and nothing is sticking. The reversal unlocks creative thinking that feels blocked in the standard format.

17. Lean Coffee Retrospective

No pre-set agenda. Team members propose topics at the start of the session, dot-vote on priority, then discuss in order with strict timebox (8 minutes per topic) and a democratic extend/close vote. Lean Coffee gives team members control over the agenda, which increases ownership.

When to use: When you want maximum team ownership of the agenda, or when the facilitator doesn't know what's most urgent and wants the team to decide. Works especially well for async-first or fully remote teams.

18. Circles and Soup

Three concentric circles: what we control (take direct action), what we influence (can advocate or persuade), what we can only accept (beyond our influence). Teams place their issues in the appropriate circle and focus action items only on the inner two. The "soup" framing helps teams stop generating action items about things they can't change.

When to use: When the team spends retro time complaining about things outside their control. Circles and Soup redirects energy toward what the team can actually do.

Formats for Distributed or Async Teams

Use these when the team is partially or fully remote, spread across time zones, or where synchronous time is limited.

19. Async Retrospective with Live Synthesis

Team members submit retrospective inputs via a shared form or doc over 24–48 hours before the live session. The facilitator synthesises themes. The live session starts from a shared picture rather than building one from scratch — which saves 20–30 minutes and produces richer patterns.

When to use: For any remote team. Async input is less subject to anchoring bias and safer for teams with lower psychological safety, because it's easier to write something difficult than to say it in front of the group.

20. Anonymous Input Retrospective

Use a tool that allows anonymous contributions (Google Forms, EasyRetro with anonymous mode, Mentimeter). Display responses without attribution. Discuss patterns rather than individual comments.

When to use: When psychological safety is low, when there's significant hierarchy in the room (manager and reports together), or when you suspect the team is self-censoring. The data will be significantly different from named input.

Choosing the Right Format for Your Team

Team state	Recommended format
New team, building safety	Start/Stop/Continue, Mad Sad Glad
Recurring unsolved problems	5 Whys, Force Field Analysis
Low morale or difficult Sprint	Heard Seen Respected, Hot Air Balloon
Needs fresh energy	Speed Car, Worst Possible Idea
Weak action follow-through	DAKI, Working Agreements Review
Many concerns, hard to prioritise	Speedboat (with effort estimates)
Remote or distributed	Async input + Lean Coffee
Overconfident or high-stakes	Pre-Mortem

The best retrospective format is the one your team is willing to engage with honestly. Start there. Build from there.

Rotate formats every 3–4 Sprints at minimum. When teams can predict exactly what's coming before the retro starts, the retro has stopped generating new information. Surprise is not a gimmick — it's how you keep the feedback loop alive.