A retrospective is one of the most powerful team development tools available — if it leads to action. Use this planner to structure a retro that generates real learning and real change.
Celebrate real successes — specific behaviours, decisions, or outcomes that made a positive difference. Avoid vague answers like "the team" or "communication."
| # | What went well (be specific) | Raised by |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | ||
| 5 | ||
| 6 |
Name problems honestly — without blame. Focus on systems, processes, and behaviours, not people. Ground rules: no defensiveness, no interrupting, no justifying.
| # | What didn't go well (be honest) | Raised by |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | ||
| 5 | ||
| 6 |
Turn insight into intention. These are your candidate actions — vote on the top 3 to turn into commitments.
| # | What we would do differently | Votes |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 | ||
| 5 |
| # | Action (specific, measurable) | Owner | Due Date | How We'll Know It's Done |
|---|---|---|---|---|
| 1 | ||||
| 2 | ||||
| 3 |