THE GUIDE
How to run a team retrospective that leads to change
A retrospective is a short, regular meeting where the team looks back at a project or period and agrees what to change. The format matters less than two things: people feel safe being honest, and the meeting ends with a few actions that actually happen.
A simple 60-minute retro
- Set the scene (5 min): remind everyone the aim is to improve how you work, not to blame.
- Add notes in silence (10 min): everyone writes on their own first, so quiet voices are heard.
- Group and vote (10 min): each person has 5 votes.
- Discuss the top items (25 min): start with the most-voted.
- Agree actions (10 min): two or three, each with an owner.
Which format to choose
- Start, stop, continue: simple and good for any team.
- Went well, to improve, ideas: balanced, good after a project.
- Mad, sad, glad: brings out feelings after a hard period.
- 4Ls (liked, learned, lacked, longed for): good for learning-heavy work.
Frequently asked questions
Notes never show names. In a small team people may still guess, so set the tone: the aim is to fix how you work, not to find who is to blame.
Yes. Sign in, create an edit link and send it to the team before or during the meeting.
Every two to four weeks for project teams, and after any big launch or incident.
One-minute lessons on this
TOPIC 28Why hiding your own mistakes teaches your team to hide theirs
TOPIC 23Why silence in a meeting is not the same as agreement
TOPIC 38Why the loudest voice in the meeting usually wins
TOPIC 06Why vague feedback leads to the same mistakes again
TOPIC 42