What to look for
- 01
Gather experiences across the team instead of starting with the loudest diagnosis.
- 02
Turn the discussion into a small set of follow-up actions.
Keep in mind
A retrospective needs enough trust for people to describe what happened. It does not replace a time-sensitive incident review or individual feedback.
Try this next
Schedule a retrospective around one finished piece of work and review the previous actions before adding new ones.
Get the planning & delivery templateNotes and exercises by Awesome CTO. The original work belongs to Atlassian Team Playbook.