Best Retrospective Formats & Templates

Run the same three retrospective questions every sprint and even a great team starts to go quiet. Changing your retrospective format is one of the easiest ways to keep people engaged and uncover different insights. This guide compares the most popular retrospective formats and templates, explains how each one works, and helps you pick the right one for the moment.

Why your retrospective format matters

A format is simply the structure you use to collect and organize feedback — the prompts, columns, or metaphor that frames the conversation. The right format guides discussion without forcing it, surfaces different kinds of feedback, and keeps the meeting from turning into a routine venting session. There is no single best format; the aim is to match the format to what your team needs right now.

Start / Stop / Continue

One of the simplest and most widely used retrospective formats. The team brainstorms around three prompts: what should we start doing, what should we stop doing, and what should we continue doing? It is quick to explain, easy for newcomers, and naturally balances positive and negative feedback.

Start

Daily 15-min sync

Code review checklist

Stop

Long unstructured meetings

Skipping tests under pressure

Continue

Friday demos

Async standup updates

Best for

New teams, short sprints, and anyone running their first few retrospectives. It is the dependable default you can always fall back on.

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

The 4Ls format asks the team to reflect on four areas: what they Liked this sprint, what they Learned, what they Lacked, and what they Longed for. It reaches beyond process tweaks to capture growth, skill development, and aspirations.

LikedWhat went well

Smooth sprint planning

Great team communication

LearnedNew skills & knowledge

How to use the new CI pipeline

LackedGaps & blockers

Clear product requirements

Longed ForAspirations & wishes

More time for refactoring

Best for

Teams that want a richer conversation and care about learning and team development, not only process fixes.

Mad / Sad / Glad

An emotion-led format that asks team members how they felt during the sprint — what made them mad, what made them sad, and what made them glad. By starting from feelings rather than process, it surfaces morale and friction issues that more clinical formats can miss.

Best for

Teams experiencing tension or low morale, and retros where you want to understand the human side of the sprint, not just the tasks.

Lean Coffee

Lean Coffee is a structured-but-democratic agenda format. There is no preset topic list — instead, participants propose topics, vote on which matter most, and discuss them in timeboxed rounds until the time runs out. It works with any of the prompt-based formats above.

Best for

Teams that have many things to discuss and want the group to decide priorities together. Great for experienced teams that find fixed formats too rigid.

Sailboat

A visual metaphor format. The team imagines their project as a sailboat: the wind is what propels it forward, the anchor is what holds it back, rocks are risks ahead, and the island is the goal. People place notes in each zone. The metaphor makes abstract issues tangible and encourages creative thinking.

Best for

Re-energizing a team that is bored of standard formats, and for retros focused on strategy, risks, and momentum rather than day-to-day process.

How to choose the right retrospective format

No format is universally best. Pick based on your team size, how long you have, and what you want to get out of the session. A few rules of thumb:

• New team or short on time? Start with Start / Stop / Continue.
• Want richer feedback? Try 4Ls.
• Sensing tension or low energy? Reach for Mad / Sad / Glad.
• Too many topics to cover? Use Lean Coffee to prioritize.
• Need a fresh spark? Run a Sailboat retrospective.
• Change formats every few sprints so retros never feel stale.

Make any format work

The format is a starting point, not a rigid script, and the best facilitators adapt in the moment. A handful of practices help no matter which template you choose, and they tend to matter more than the format itself:

• Collect notes before the meeting so discussion starts immediately rather than from a blank board.
• Timebox each stage and move on even when conversation is still flowing.
• Group similar notes into themes before voting, so the team sees patterns instead of scattered complaints.
• Limit action items to the few the team can realistically own next sprint.
• Review last sprint's action items at the start of every retro so nothing gets dropped.
• Rotate who facilitates so the whole team learns to lead the conversation.

Remember that every retrospective format shares the same goal: honest reflection that leads to real improvement. If a format is not producing that, switch it up next sprint. The best format is simply the one your team will actually engage with, and that often changes as the team matures.

Run any of these formats with MiniRetro

MiniRetro ships with several of these retrospective formats built in — pick a template, and the board is ready in an instant. Your team adds notes, groups and votes on themes, and walks away with clear action items. No setup, no awkward tooling — just share a link and start the conversation.