Different Ways to Run a Retrospective Meeting: Tools, Formats, and Practical Approaches for Teams
A practical guide to retrospective formats, facilitation approaches, and tools for sprint reviews, incidents, team health checks, and distributed teams.
A retrospective is one of the simplest and most valuable habits a team can build. The idea is straightforward: pause after a sprint, project, launch, incident, or busy period; reflect on what happened; and agree on a small number of improvements.
In Scrum, the Sprint Retrospective is specifically described as a time for the team to plan ways to increase quality and effectiveness (Scrum.org).
Not every retrospective should look the same. A team coming off an incident needs a different conversation than a team celebrating a smooth launch.
Start with the purpose, not the template
The best retrospective format is the one that helps the team have an honest conversation and leave with a useful next step. Esther Derby and Diana Larsen's Agile Retrospectives: Making Good Teams Great centers retrospectives on continuous learning and improvement (Agile Alliance).
A useful structure for most retrospectives is:
- Set the stage.
- Gather data.
- Generate insights.
- Decide what to do.
- Close the retrospective.
Retromat uses a similar five-phase approach and can generate activity combinations for each phase (Retromat).
Create psychological safety first
A retrospective only works if people feel safe enough to tell the truth. Google's Project Aristotle identified psychological safety as one of the most important team dynamics (Google re:Work).
A practical way to set this tone is to open with the Retrospective Prime Directive: assume everyone did the best they could with the information, skills, resources, and situation they had at the time (FunRetrospectives).
Keep discussion centered on systems, communication, process, and constraints rather than personal blame.
Open a retrospective board template →
1. What went well / didn't / should change
This classic format is often best for new teams: simple, fast to explain, and easy to run in person or remotely.
- What went well?
- What did not go well?
- What should we try next?
EasyRetro includes this pattern as a baseline template (EasyRetro templates).
Best for: new teams, shorter retros, and low-friction facilitation.
Watch out for: vague actions. Replace “communicate better” with specific experiments and owners.
2. Start / Stop / Continue
Start/Stop/Continue is beginner-friendly and naturally balanced because it reinforces what to keep, not only what to fix.
Best for: recurring sprint retrospectives and lightweight process improvement.
Watch out for: stale answers if used every sprint forever.
Good tools: sticky notes, SharedBoards.io, Trello, Miro, Parabol, TeamRetro.
3. 4Ls: Liked, Learned, Lacked, Longed For
4Ls is useful when a team is learning: onboarding, running experiments, or adopting a new process.
- Liked: what people appreciated
- Learned: what they discovered
- Lacked: what was missing
- Longed for: what they wish existed
Best for: learning-focused teams and experimentation phases.
Watch out for: “Longed for” turning into an unbounded wish list.
4. Sailboat retrospective
Sailboat adds a visual metaphor that helps teams discuss momentum, risk, and direction, not only tactical sprint issues.
Miro's retrospective templates include visual formats like this (Miro templates).
Best for: strategy retrospectives, uncertainty, and cross-functional work.
5. Mad / Sad / Glad
Mad/Sad/Glad focuses on emotional data, which can reveal burnout, frustration, and morale issues that process-only formats miss.
- Mad: frustrations
- Sad: disappointments
- Glad: wins and positive signals
Best for: stressful sprints and morale recovery periods.
6. 1-2-4-All for inclusion
1-2-4-All is a Liberating Structures technique: think alone, discuss in pairs, then groups of four, then share with all (Liberating Structures).
It works well when a team has dominant voices, hierarchy, or uneven participation.
7. Data-driven retrospectives
Memory and opinion are useful but incomplete. Add evidence like cycle time, escaped bugs, incident count, PR review time, or sprint spillover.
Recent research notes teams often collect project data but underuse it in retrospectives (arXiv).
Use data to ask better questions, not to punish people.
8. Team health checks
Health checks surface gradual problems like declining trust, overload, and delivery confidence. TeamRetro supports private feedback, trends, and action planning (TeamRetro health checks).
9. Asynchronous retrospectives
Distributed teams can collect feedback before the meeting, then use live time to discuss top themes and assign actions.
- Open the board 24-48 hours in advance.
- Allow private or anonymous note collection.
- Group similar notes.
- Vote on priority themes.
- Discuss top themes live.
- Assign owners and due dates.
Parabol and Retrium both support this workflow (Parabol, Retrium).
10. Blameless postmortem retrospectives
For outages, failed launches, or high-impact incidents, use a blameless postmortem style: timeline, impact, detection, response, contributing factors, and follow-up actions.
Atlassian describes this as learning-focused incident review without “the blame game” (Atlassian).
Choosing the right retrospective tool
Simple collaboration tools
Shared docs, spreadsheets, and lightweight boards work well when the facilitator is strong and the format is simple.
Visual whiteboarding tools
Whiteboarding tools are best when you need visual clustering, metaphors, or workshop-style facilitation.
Dedicated retrospective tools
Dedicated tools usually add anonymity, voting, timers, templates, action tracking, and history.
Activity libraries
Use Retromat and FunRetrospectives when your format is getting stale and you need fresh facilitation patterns.
How to end with action instead of talk
The most common failure mode is leaving with too many vague actions. Choose one to three improvements only.
- An owner
- A deadline
- A clear next step
- A way to know whether it worked
Replace “improve code reviews” with a measurable experiment for the next sprint.
When your team has agreement on the next 1-3 actions, capture them on a board immediately with owners and due dates so momentum does not fade after the meeting.
Use the Start / Stop / Continue board now →
Final thoughts
A retrospective is not just another meeting; it is a team's operating system for improvement. The format can be simple or creative, synchronous or asynchronous, emotional or data-driven.
What matters most is psychological safety, an honest conversation, and a small experiment that improves the next cycle of work.