Which retro format fits the sprint you actually had

The format is the shape of the conversation

Every retro format is really a set of prompts, and the prompts decide what people talk about. Start / Stop / Continue steers toward concrete behavior changes. Mad / Sad / Glad opens the door to how the sprint felt. A Sailboat (wind, anchors, rocks) surfaces what's helping, what's dragging, and what risks lie ahead. Ask a team to fill in "Liked / Learned / Lacked / Longed for" and you'll get a different discussion than if you'd asked them to sort events onto a Timeline. None of these is better in the abstract — they're better or worse for a given sprint.

The Random Sprint Retro Format Generator carries a spread of these — Start / Stop / Continue, 4Ls, Sailboat, Mad / Sad / Glad, Plus / Delta, KALM, Rose / Thorn / Bud, DAKI, Timeline, 3 Little Pigs, Starfish, and Lean Coffee — each with a one-line structure and a short facilitation note. Below is how to think about reaching for a particular shape when the sprint calls for it.

After a rough sprint

When things went badly, the instinct is to jump straight to fixes — but a team that's frustrated needs to feel heard before it can problem-solve. Mad / Sad / Glad gives the emotional side room to breathe first, which defuses tension so the "what do we change" part lands. If the trouble was specific and sequenced — a bad deploy, a cascade of incidents — a Timeline Retro is powerful: laying events out in order lets the team see where things actually went sideways instead of arguing from memory. And if a rough sprint has people pointing fingers, Plus / Delta keeps it blessedly neutral: what worked, what we'd change, no blame framing at all.

After a smooth sprint

Good sprints are where retros quietly die — the board fills with "nothing to add" and everyone leaves early. That's exactly when a sharper format earns its keep. KALM (Keep / Add / Less / More) pushes past "it was fine" by forcing a judgment on what to dial up and down. Starfish does the same with five gradations (keep, more, less, start, stop) so a calm sprint still produces real signal. Rose / Thorn / Bud is a gentle way to make sure even a smooth sprint surfaces its one small thorn and, importantly, its buds — the early opportunities worth nurturing before they get buried under the next backlog.

At a milestone or for a bigger conversation

End of a quarter, a major release, or a project phase? Reach for a format that zooms out. The Sailboat is built for this — it explicitly asks about the goal on the horizon, the wind pushing you there, the anchors slowing you down, and the rocks ahead, which is a strategic conversation, not a housekeeping one. When the team has a long list of things to discuss and you don't want to pre-decide the agenda, Lean Coffee is ideal: the team brainstorms topics, dot-votes them, and time-boxes each, so the most important issues rise to the top democratically.

Let the draw decide — but keep the "no repeats" safety net

Here's the honest tension: deliberately matching a format to a sprint is a facilitator skill, and sometimes you genuinely know what the team needs. Other times you're staring at a normal sprint with no obvious shape, and overthinking the choice just delays the meeting. That's where a random draw shines — it breaks the default habit of always running Start / Stop / Continue and gives you a format you wouldn't have picked, which surfaces things your usual prompts never ask about.

A good rhythm is to let the generator draw by default, and only override it when a sprint clearly demands a specific shape — a rough one, a milestone, a team that's gone silent. When you do let it draw, turn on "No repeats until every format has come up." That way the tool cycles through the whole set before repeating any format, so your team builds real fluency across a dozen different lenses instead of bouncing between the same two. Once every format has been used, it resets and starts a fresh cycle.

There's a quiet compounding benefit to running the full rotation this way. The first time a team meets a new format, half the energy goes into understanding the prompts rather than answering them. By the second or third exposure, the structure is invisible and the conversation goes deeper, faster. A team that has genuinely worked through all twelve formats has, in effect, a toolbox — and the next time a sprint has an obvious shape, someone will recognize it and say "this feels like a Sailboat week" before you've even opened the tool. That instinct is the real goal; the randomizer is just the training wheels that get you there.

Run one that fits this week

Before your next retro, take ten seconds to name the sprint you actually had — rough, smooth, milestone, or just another Tuesday — and either pick the format that fits or let the draw pick for you. The Random Sprint Retro Format Generator gives you the structure and a facilitation note in one click, so you can spend your prep on the conversation instead of the template. While you're setting up the ceremony, the Standup Order Randomizer keeps your daily order from calcifying, the Breakout Room Assigner splits a big retro into small groups that actually talk, and the Demo Day / Sprint Review Order handles the running order for the review that comes before it.