Goal of a retrospective
The goal is to learn what worked, what did not, and what to change — then commit to specific experiments with owners.
Before the meeting
- Frame it as improvement, not blame
- Collect any data or metrics in advance
- Keep it to the team that did the work
Retrospective agenda (90 minutes)
- 0:00–0:10
Welcome and safety
Frame the goal and ground rules.
- 0:10–0:25
Silent reflection
Individual start/stop/continue notes.
- 0:25–0:45
Sharing and clustering
Group themes on a shared board.
- 0:45–1:10
Root-cause discussion
Dig into the top two or three themes.
- 1:10–1:25
Experiment selection
Pick 1–3 small experiments to try.
- 1:25–1:30
Owners and follow-up
Assign owners and set the next check-in.
Common mistakes
- Blame replacing learning
- The same issues repeating with no action
- Experiments with no owners
- No follow-up date
After the meeting
Record the experiments, owners and the next check-in. At the next retrospective, start by reviewing whether the experiments worked.
Key takeaway
A retrospective earns its place only if it ends with a few real experiments and owners who will run them.