Retrospective Meetings
A retrospective is where a team pauses to ask 'how are we working, and how could we work better?' Here are the formats that keep retros honest and useful instead of a box-ticking ritual.
What a retrospective is
A retrospective (or "retro") is a regular meeting where a team reflects on how it has been working and agrees concrete improvements. It's most associated with agile and the end of a sprint, but any team benefits from the habit. The focus is the process, not the work itself — and crucially, not blame.
Why retros matter
Without a deliberate pause, teams repeat the same friction indefinitely. A good retro converts vague frustration into a small number of specific changes, and — just as importantly — checks whether last time's changes actually stuck.
Popular formats
- Start, Stop, Continue — what should we start doing, stop doing, and keep doing? Simple and fast.
- 4Ls — Liked, Learned, Lacked, Longed for.
- Mad, Sad, Glad — surfaces the emotional temperature, good for tense periods.
- Sailboat — what's the wind (helping), the anchor (holding back), the rocks (risks)?
Rotate formats so the retro doesn't become rote.
How to run one
- Set the stage — remind everyone it's blameless and about improving the system.
- Gather input — give people quiet time to write notes first, so the loudest voice doesn't dominate.
- Group and discuss the themes.
- Decide on one to three concrete actions with owners — not ten.
- Review last retro's actions at the start of the next one.
Remote retros
For distributed teams, a shared digital board where everyone adds notes at once works well — it gives remote participants an equal voice. The same principles as inclusive meetings and hybrid meetings apply.
Anti-patterns to avoid
- Turning it into blame instead of improving the process.
- Generating a long wish-list no one ever acts on.
- Letting the same person dominate — write first, talk second.
- Never following up on agreed actions.
Frequently Asked Questions
A regular meeting where a team reflects on how it has been working and agrees specific improvements. It focuses on the process rather than the work, and it's deliberately blameless — the aim is to improve the system, not to point fingers.
Start-Stop-Continue is the simplest; 4Ls (Liked, Learned, Lacked, Longed for), Mad-Sad-Glad, and Sailboat are popular alternatives. Rotate them so the retro stays fresh rather than becoming a rote ritual.
Typically 45–90 minutes depending on the length of the period being reviewed. The key is to leave with one to three concrete, owned actions rather than a long list nobody acts on.