Five Retrospective Formats to Break Your Team Out of the Round-Robin Rut
The Sprint Retrospective is, per the Scrum Guide, where the Scrum Team inspects how the last Sprint went — people, interactions, process, tools, Definition of Done — and plans improvements for the next one. It is the engine of continuous improvement. Yet many teams run the same "what went well / what didn't / what to change" three columns Sprint after Sprint until people answer on autopilot and nothing actually changes.
By late 2021, with most teams still distributed across kitchens and home offices, the problem got worse. A bored retrospective over video, where two people talk and the rest mute themselves, is barely a retrospective at all. The fix is not more discipline; it's variety. Rotating the format keeps people engaged and surfaces issues a stale template never would.
Techniques worth rotating in
Sailboat. Draw a boat. The wind is what propels you, the anchors are what hold you back, the rocks are risks ahead, and the island is your goal. It reframes the Sprint visually and naturally pulls out risks the three-column format tends to miss.
Start, Stop, Continue. Three prompts that force concrete behaviour rather than vague sentiment. "Stop pulling in unrefined items" is more actionable than "planning felt rough." Fast, and excellent for remote teams short on time.
Glad, Sad, Mad. An emotion-led check-in that gives space to interpersonal and morale issues that process-only formats bury. Use it when the team feels tense but no one is naming why.
4 Ls — Liked, Learned, Lacked, Longed for. Balances the positive with honest gaps. "Lacked" and "longed for" invite people to ask for support without it feeling like blame.
The 5 Whys on one problem. Instead of skimming ten issues, pick the single most painful one and ask "why" five times to reach a root cause. Depth over breadth — ideal when the same complaint keeps recurring.
Make remote retrospectives actually work
Use a shared digital board so everyone writes at once instead of waiting their turn — silent generation beats serial round-robin every time.
Have people add notes silently for a few minutes before any discussion, so the loudest voice doesn't anchor the room.
Rotate the facilitator; a Scrum Master who runs every retro the same way gets the same answers.
Keep it psychologically safe — the goal is the system, not blame. People stop being honest the moment a retrospective is used against them.
The part most teams skip
A retrospective that ends with twelve sticky notes and no decisions is theatre. The Scrum Guide is clear that the team should identify the most impactful improvements and address them as soon as possible — many teams add at least one to the next Sprint Backlog so it competes for real capacity. Pick one or two changes, not ten. Make them specific and owned. And begin the next retrospective by checking whether the last change actually happened. That single habit — closing the loop — is what separates teams that genuinely improve from teams that just hold meetings about improving.
The format is only a tool to get honest input. What turns a retrospective into momentum is following through on the small number of changes you commit to, Sprint after Sprint.
If your retrospectives generate lots of notes but little change, XNM's program & project delivery advisory can help your teams turn inspection into improvements that actually stick.