Retrospectives are considered the heart of agile work — and at the same time, they're the practice that most often decays into routine. Many teams know only one format: what went well, what didn't, what to take forward. After ten rounds, the answers become interchangeable, actions diluted, and energy in the room measurably drops. Yet the retrospective holds the team's greatest lever: here patterns become visible, assumptions get tested, and agreements are made that separate stagnation from real change. This article introduces six formats with different strengths — from quick health checks to deep cultural dialogue. You'll learn when each format fits and how to run retros so the outcomes last beyond the session.
DEFINITION
A retrospective is a structured team meeting aimed at reflecting on the team's own way of working and deriving concrete improvements. It differs from a review (outcome focus) and a debrief (event focus) by its process focus: how do we work, and how do we want to work?
Squad Health Check
The Squad Health Check is a format Spotify made famous: the team jointly rates 10 to 12 dimensions of their way of working — from mission to pace to fun — on a simple traffic-light scale. Its strength is speed: a health check takes 45 to 60 minutes and immediately produces a visual overall picture. The format becomes especially valuable when repeated regularly, because trends over time become visible: is mission clarity improving? Is pace tipping into the red? Health checks suit teams that have worked together for a while and want an overview before going deep. They're less suitable for acute crises or young teams still negotiating their norms.
View DetailsPRO TIP
Run health checks quarterly and document results as a time series. The real insight isn't in the current number but in the trend. A team showing red on pace three quarters in a row has a structural problem — not a bad day.
Liberating Structures
Liberating Structures isn't a single method but a collection of 33 small formats that systematically change the dynamics of meetings. Particularly suitable for retrospectives are Troika Consulting (peer consulting in groups of three), What, So What, Now What? (observation, interpretation, action in three rounds), and 15% Solutions (small changes anyone can implement immediately). The strength of Liberating Structures is that everyone on the team gets a voice — including the quiet ones. Standard retros often suffer from two or three dominant voices filling the room. Liberating Structures structurally break this pattern by alternating between solo work, pairs, small groups, and plenary.
View DetailsAgile Health Radar
The Agile Health Radar is an assessment tool that visualizes a team's agile maturity on multiple axes: team culture, delivery capability, technical excellence, product understanding. Unlike the Squad Health Check, the radar goes deeper into individual dimensions and provides concrete development guidance. It suits teams already using agile methods and planning their next maturity step. Typical use contexts are coaching engagements, where the agile coach needs an objective picture before and after their work. The radar doesn't replace ongoing retrospectives but complements them as a periodic deep check.
View DetailsWorking Agreements
Working Agreements aren't a retro method in the narrow sense, but the most important retro outcome of all: written, team-agreed arrangements about how to work together. A retro cycle that doesn't end in a new or adjusted agreement has wasted its potential. Working Agreements make implicit expectations explicit: when is Slack fine? Who takes review load? How do we handle interruptions? Their strength lies in their testability — at the next retro you check whether they held or need adjustment.
View DetailsTeam Model Canvas
The Team Model Canvas is a structured framework teams use to make their mission, goals, roles, rules, and context visible. For retrospectives it's especially valuable when the team has fundamental questions about itself — after a reformation, after restructuring, or when direction has become unclear. Unlike a health check or classic retro, the Team Model Canvas climbs one level higher: it doesn't ask 'what's running?' but 'who are we and what for?'. Such a deep retro takes three to four hours and often changes more than ten classic retros in a row.
View DetailsMeeting Canvas
The Meeting Canvas is a preparation tool that answers a simple question: why this meeting, for whom, with what outcome? For retrospectives it's gold because the most common retro disease is unclear objectives. A team that unreflectively runs the same format every week loses the retro's power. The Meeting Canvas forces the facilitator to decide consciously before each retro: is today about mood, process, alignment, conflict? The right format follows from the answer — not the other way around.
View DetailsCAUTION
The most common retro trap: actions get decided but not implemented because no one owns them. Every retro action needs a named owner and a target date. Without that, the retrospective remains a ritual without effect.
The six formats aren't interchangeable. Squad Health Check and Agile Health Radar are measurement instruments for regular bearings. Liberating Structures is a method toolbox for varied execution. Working Agreements are the outcome that good retros lead to. Team Model Canvas is the deep tool for fundamental questions. Meeting Canvas is the preparation tool for making the right choice. Those who internalize this distinction have a retro year that looks different every quarter and still feels coherent.
KEY TAKEAWAY
The best retro isn't the most colorful one but the one that fits the team's current question. Choose the format from the question, not from the need for variety.
CONCLUSION
Retrospectives aren't a mandatory appointment but the structural moment where teams change their own work. The classic what-went-well format is a solid starting point but becomes shallow after a few weeks. Those who take their team seriously invest in a repertoire: a measurement instrument for overview, a method toolbox for variety, a deep tool for fundamental questions, and always the discipline to turn insights into binding agreements. Then retros become what they should be: the lever for real change.