7 Sprint Retrospective Templates Your Team Will Actually Use

If your team's last retrospective ended with the same three action items as the previous five — and none of them got done — your format is the problem. The template you use shapes what the team notices and what gets surfaced. Rotating formats keeps the conversation fresh.

1. Start, Stop, Continue

Best for: weekly check-ins, new teams, anyone who needs a low-friction format. Three columns: what should we start doing, stop doing, keep doing. Fast, simple, surfaces obvious wins and obvious problems. Goes stale after about 4 sprints in a row.

2. Mad, Sad, Glad

Best for: when team morale matters more than process. Cards go into emotional buckets, which surfaces frustrations that "what didn't go well" misses. Use it when you suspect there's something off but no one's saying it.

3. 4Ls (Liked, Learned, Lacked, Longed For)

Best for: end-of-quarter or end-of-project retros. Slower than Start/Stop/Continue but pulls out lessons learned and unmet expectations more reliably. "Longed for" is the secret weapon — it's where blocked aspirations show up.

4. Sailboat retrospective

Best for: teams stuck in a rut. Visual metaphor: the boat is the team, the wind pushes you forward (what's helping), the anchors hold you back (what's slowing you down), the rocks are upcoming risks, the island is your goal. The metaphor gets people thinking systemically instead of about isolated incidents.

5. Starfish (Keep, Less, More, Stop, Start)

Best for: mature teams refining established practices. Five categories instead of three lets you say "do less of this, more of that" without it being binary. Useful when nothing is broken but things could be better.

6. KALM (Keep, Add, Less, More)

Best for: teams that want a structured improvement loop without the emotional weight of Mad/Sad/Glad. It's a Starfish variant focused entirely on calibration. Less time on "what's broken," more time on "how do we tune what's working."

7. The 5 Whys retrospective

Best for: after a specific incident — production outage, missed deadline, customer escalation. Pick one event and ask "why" five times to drill into root cause. Don't run this as a regular sprint retro; save it for when something goes wrong.

How to actually run any of them

• •Silent brainstorm first (5 min) — everyone adds cards before anyone reads them
• •Group similar cards together (5 min) — the patterns matter more than individual cards
• •Dot-vote on what to discuss (3 min) — focus the conversation on what the team thinks matters most
• •Discuss top 3–5 items (20 min) — timebox each one
• •Choose 1–3 action items (5 min) — fewer is better; assign owners and dates

The action items rule

If your retros generate action items that don't get done, you're collecting commitments without accountability. Two fixes: limit action items to 1–3 per retro (you can do three small things; you can't do ten), and review the previous retro's action items at the start of the next one. If you didn't do them, that's the first conversation.

Rotate, don't optimise

Don't search for the "perfect" retro format. Rotate through 3–4 of these every couple of months. The novelty itself surfaces things a familiar format wouldn't — different prompts catch different problems.