Why retros are not just for scrum teams
"Retrospective" got attached to agile software teams because Scrum baked it in at the end of every sprint. But the underlying meeting - a structured conversation about what happened, what mattered, and what to change - has nothing to do with sprints or tickets. Any group that does work together can run one.
A marketing team can retro a campaign launch. A finance team can retro the quarter close. A leadership team can retro an offsite. An ops team can retro a week of on-call. The trick is to pick a format that fits the cadence, the size of the group, and how senior or junior the room is - not to copy a sprint retro template verbatim and feel like it doesn't quite fit.
Rule of thumb. If the team did a thing together and the thing has a beginning and an end (a project, a quarter, a week of incidents, a launch), a retrospective is probably worth 45 minutes of everyone's time. The cost is small; the cost of not learning the lesson is much larger.
Picking a format: size and seniority
Three variables dominate format choice:
- Team size. 3–5 people: any format works, even unstructured. 6–10: you want columns to focus the discussion. 11+: you need a format that supports parallel writing and voting, or you split into rooms.
- Seniority mix. Mixed-seniority rooms benefit from silent writing formats so juniors aren't anchored on whatever the senior says first. All-leadership rooms can usually skip silent writing and go straight to discussion.
- Familiarity with each other. A team that runs retros every two weeks can use rich formats (Sailboat, KALM); a team that has never retroed before should start with something simple (Start/Stop/Continue, Went Well / To Improve).
| Team type | Size | Recommended formats |
|---|---|---|
| Small project team | 3–6 | Start/Stop/Continue, 4Ls, Rose/Thorn/Bud |
| Cross-functional launch | 6–12 | Mad/Sad/Glad, Sailboat, KALM |
| Leadership / offsite | 4–8 | Lean Coffee, Plus/Delta, Future-perfect |
| Quarterly review | 8–20 | Timeline, Highlights/Lowlights, Pre-mortem |
| Ops / on-call | 4–10 | DAKI, Incident lookback, Five Whys |
| Remote-only team | any | Anonymous Mad/Sad/Glad, Async written retro |
Warm-ups (any team, 5 minutes)
Warm-ups exist for one reason: get every voice in the room before the discussion starts. If someone hasn't spoken in the first five minutes, they probably won't speak for the rest of the hour. These work for any team type.
01 One-word check-in
Each person writes a single word describing how they feel about the period being reviewed. Read them aloud in a round. No discussion. Sets the emotional temperature of the room without any one person dominating.
02 Weather report
Each person picks a weather icon (sunny, partly cloudy, stormy, foggy) and one sentence on why. Lower-stakes than naming a feeling directly; works particularly well with senior rooms who don't like touchy-feely prompts.
Classic formats that work everywhere
03 Start / Stop / Continue
The simplest retrospective format ever invented, and the one you should default to if a team has never retroed. Three columns; people write cards into each. Discuss in vote order. Pick one action per column.
When to use: first retro with a team, leadership retros where time is tight, ops teams reviewing a process change.
Try Start/Stop/Continue now →04 Mad / Sad / Glad
People write cards into each of three emotional columns. Surfaces how the team felt about the period, not just what happened. Especially useful after a stressful launch or a tough quarter.
When to use: after a high-pressure stretch, when you suspect there's unspoken frustration in the room.
Try Mad/Sad/Glad now →05 4Ls - Liked, Learned, Lacked, Longed For
Four columns. "Liked" captures wins; "Learned" captures new knowledge; "Lacked" captures gaps the team felt; "Longed For" captures aspirations. Better than Start/Stop/Continue for project wrap-ups where learning matters as much as action items.
When to use: end of a discovery sprint, end of an R&D project, after a learning-heavy quarter.
06 Rose / Thorn / Bud
Rose = something that went well. Thorn = something painful. Bud = something with potential, not yet flowering. Particularly nice for leadership and people-team retros - the metaphor is softer than Mad/Sad/Glad.
07 Starfish
Five spokes around a central star: Keep doing, More of, Less of, Stop doing, Start doing. Wider than Start/Stop/Continue without jumping all the way to KALM. A safe default when you want richer categories but don't want to teach the team a new metaphor.
08 KALM - Keep, Add, Less, More
"Keep" what's working; "Add" what's missing; do "Less" of what's dragging us down; do "More" of what's working. KALM frames the conversation as dial-tuning rather than binary keep-or-kill, which works well with experienced teams who don't want to oversimplify.
Project wrap-up formats
When a project ends - not a sprint, the whole project - the retrospective question shifts from "what should we change next sprint?" to "what should the next project inherit from this one?" These formats lean into that.
09 Sailboat
Draw a sailboat. Wind in the sails = what propelled the project forward. Anchors = what slowed it down. Rocks ahead = risks the next project should watch for. Island = the goal you were heading to. Especially good for cross-functional launch teams that need a shared picture of the journey.
10 Timeline retrospective
Draw a horizontal timeline of the project. Each person adds events they remember - wins, setbacks, decision points - onto the line. Then the team discusses clusters: where did energy concentrate? Where did things stall? Excellent for long projects where the beginning has been forgotten.
11 Highlights & Lowlights
Two columns. Each person nominates the top two highlights and top two lowlights of the project, with a single sentence of context. Surfaces the team's shared narrative quickly - useful before a public retrospective writeup or executive readout.
Quarterly & leadership formats
Quarterly retros are usually with a more senior, more time-pressed audience. The format needs to respect time, push fast to decisions, and avoid feeling like a feelings-fest. These three deliver.
12 Plus / Delta
Two columns. Plus = what we want to keep doing. Delta = what we want to change. That's it. Plus/Delta is the format leaders reach for when they have 20 minutes and want zero ceremony. The constraint forces sharper answers.
13 Lean Coffee retrospective
The room generates topics, dot-votes them into order, then discusses each top-voted topic for a fixed 5 or 8 minutes. After the timer, the group votes thumbs-up (keep talking), thumbs-down (move on), or sideways (one more minute). Brilliant for leadership rooms because it lets the most important topics rise without a facilitator imposing them.
14 Future-perfect / Pre-mortem of next quarter
Half retro, half kick-off. Imagine it's the end of next quarter and everything has gone perfectly. What happened? What did we stop doing? Who did we hire? Then invert: imagine everything went wrong - what was the cause? Combines learning from the past with explicit planning for the future. Very effective at leadership offsites.
Ops, on-call & incident-style retros
Ops teams retro differently because the work is reactive: incidents, tickets, alert volume, on-call load. Idea-generation matters less; the focus is system improvement.
15 DAKI - Drop, Add, Keep, Improve
Sharper than KALM for ops teams: Drop something entirely (an alert, a meeting, a check), Add something missing (runbook, automation, training), Keep what works, Improve what almost works. Decision-oriented language pushes to action.
16 On-call lookback
Three columns specifically for the previous rotation: pages that fired, pages that should have fired but didn't, and pages that fired but shouldn't have. Drives concrete alert-tuning actions and surfaces silent failures.
17 Five Whys on the worst week
Pick the single hardest event of the period. Ask "why?" five times in a row, each answer feeding the next question. Forces the group past the symptom into the root cause. Best with a small group; gets unwieldy past six people.
18 Async written retro
No live meeting. Open a board with the prompts your team needs (Went Well / To Improve / Actions works fine), give people 24 hours to add cards in their own time zone, then another 24 hours to vote and comment. The facilitator turns the top-voted items into action items in a follow-up thread. Better than a 30-minute call wedged across three time zones, and the writing tends to be sharper than live talk.
Facilitation tips that travel across teams
- Silent writing first. 5–7 minutes of silent card writing before any discussion. Stops the loudest voice from anchoring the room.
- Mask cards during writing. Other people should see that someone is writing, not what. Eliminates groupthink before it starts. Retro Harbour does this by default.
- Dot-vote before discussing. Voting before discussion makes the team focus on what most people care about, not what the first speaker raised.
- Cap action items at three. Five action items mean none of them get done. Two or three real ones with owners and dates beats ten aspirational ones every time.
- Own the action item language. "Improve docs" is not an action; "Adam writes the on-call runbook by Friday" is.
- Read last retro's actions first. Start by checking what got done from the previous retro. Without this loop, retros become venting sessions.
Running it online with Retro Harbour
Every format above maps cleanly onto a real-time retrospective board. Retro Harbour ships with the most common formats as one-click templates - Start/Stop/Continue, 4Ls, Mad/Sad/Glad, Sailboat, KALM, Went Well / To Improve, Starfish, Rose/Thorn/Bud, Lean Coffee, DAKI - and lets you rename columns to build any of the others (Plus/Delta, on-call lookback, Highlights/Lowlights) in seconds.
Cards are masked during writing so juniors aren't anchored on what seniors said. Voting is anonymous. The whole board exports to Markdown when you're done so you can drop it straight into a wiki or ticket. No sign-up required for participants - share one link and the team is in.
Pick any format above and run it now
Free, real-time, no sign-up. Share a link, run a better retro.