Your team finishes a hard stretch of work. A launch. A merger. A quarter that ran long. Someone books a retrospective. You sit in a room, open a template, and ask the usual questions. What went well? What did not? What do we change?
The notes look fine. The action items get written down. And three weeks later nothing is different.
The problem is rarely the exercise. The five exercises below are genuinely good, and your team could run any of them this week. The problem is when you run them — and that is the flaw every one of them shares. We will get to the fix. First, the exercises.
Five Team Retrospective Exercises That Work
Each of these gives the team a frame. The frame matters because a blank "how did it go?" produces blank answers. A good exercise pulls specific behavior into the open so the team can act on it.
Start-stop-continue. Three columns. Each person writes what the team should start doing, stop doing, and keep doing. Group the duplicates, talk through the biggest clusters, and turn the top one or two into a real action with an owner. It is the fastest exercise here and the easiest to run cold. Use it when you want speed.
The sailboat. Draw a boat. The wind in the sail is what pushed the team forward. The anchor is what held it back. The rocks ahead are the risks you can still see coming. The island is the goal. People add sticky notes to each part. This one is good for teams that talk in abstractions, because the picture forces them to be concrete about what actually slowed them down.
4Ls — liked, learned, lacked, longed for. Four quadrants. What did the team like about how it worked? What did it learn? What did it lack — a tool, a decision, a person in the room? What did it long for that was missing? The "lacked" and "longed for" quadrants are where the honest gaps show up, the things people felt but never said out loud during the work.
The timeline. Put the project on a wall as a line from start to finish. The team marks the key moments — the good calls, the stuck points, the moment the plan and reality first split apart. This is the exercise that surfaces facts people on the same team did not know about each other. It pairs well with a structured after action review template, which walks the same ground with four sharper questions and a commitment table at the end.
Mad-sad-glad. Three buckets for how the work felt. What made people mad, sad, or glad. It sounds soft. It is not. Emotion is data about where the team frayed, and naming it out loud is often the only way the quiet frustrations reach the table before they harden into resentment.
Any of these will give you a better retrospective than a blank-page conversation. Pick the one that fits your team and the time you have. Then notice what they all assume.
The One Flaw Every Retrospective Exercise Shares
Every exercise above runs after the fact.
By the time the team sits down, the work is done and the feelings have cooled. People do not recall the moment the decision went sideways. They recall a tidy summary of it. The sharp edges are gone. So the notes come out clean and the real insight — the one buried in how it actually felt when the pressure was on — never makes it onto the wall.
This is the gap between what a team writes about itself and what a team actually does. A calm room produces calm answers. The behavior you most need to fix only shows up when the stakes are live, and by retrospective day the stakes are a memory. You end up with action items built on what people half-remember, not on what happened.
You see this most clearly in the "stop" column of a start-stop-continue. Teams almost never name the real thing they should stop — the senior voice that shut down dissent, the decision made in a side conversation, the idea everyone killed in the first ten minutes. Not because they are hiding it. Because three weeks later the moment is fuzzy, and naming a fuzzy thing feels like an accusation. The norms a team agreed to in a kickoff are easy to write and hard to keep, which is exactly why team working agreements get tested by pressure, not by a meeting.
So the exercise is not broken. The timing is.
The Fix: Run the Retrospective While the Memory Is Hot
The most useful retrospective does not happen after the project. It happens while the team is still inside a high-pressure moment, then debriefs before the feeling fades.
That is what an immersive simulation does. In the Save the Titanic experience, your team becomes the senior officers on the ship in the minutes after the iceberg strikes. Limited time. Limited information. 2,200 lives on the line. For three and a half hours, the team makes real decisions under real pressure — and behaves the way it behaves at work, stripped of the professional polish.
Then you debrief, immediately, while the emotional memory is still fresh. The moment communication broke down, the moment a quiet officer got overruled, the moment the team rushed a call it should have slowed down on — everyone remembers exactly when it happened and how it felt. That specificity is the thing a cold retrospective can never reach.
Now run any of the five exercises against that. Start-stop-continue lands harder when the "stop" is a behavior the whole room just watched, not a vague memory from last quarter. The timeline writes itself, because the team lived the timeline an hour ago. Mad-sad-glad gets honest, because the emotion is still in the room.
This is why the after action review works best in real time rather than weeks after the fact. The exercise is the same. The freshness is what makes it true.
What Changes When the Read Is Real
ArcelorMittal ran 710 leaders through the experience in partnership with Duke Corporate Education and came out making decisions 30 to 40% faster. That speed did not come from a better retrospective template. It came from leaders who had just seen, under pressure, exactly how their team made decisions — and could repair it while the memory was sharp. Bell MTS moved from $800 million toward $1.4 billion in revenue in a single year on the back of leadership teams that could finally see and fix how they worked together.
Use the five exercises. They are good tools and your team should know them. Then fix the one flaw they share. Run the retrospective while the pressure is still on and the memory is still hot, and the action items stop being a tidy list nobody acts on — because the team is fixing what it just felt, not what it half-remembers.
Read next: After Action Review Template: How to Run an AAR That Changes Behavior