A retrospective meeting, commonly called a “retro”, is a team meeting that looks back at recent events to examine what went well and opportunities for improvement. Product managers often run retro meetings at the end of a planning cycle or after a big product launch. Retros are also a great opportunity to measure the success of a project or feature launch based on metrics that were set before the work began.
It’s also important to capture everyone’s honest feedback and reduce group think bias as much as possible. This doc is designed to do just that. The meeting starts with an individual reflection. Then, when the team is ready to discuss, each person’s feedback is revealed. The end result is a set of action items assigned that will put the feedback into practice.
To start designing an inclusive retrospective meeting, copy this doc and follow the checklist below.
(10 mins) Add feedback individually. Leave the “show everyone’s answers” box unchecked to reduce group think bias
(5 mins) Reveal feedback and vote on topics to discuss
(15 mins) Discuss feedback and add action items
(After the meeting) Send action items to individuals with the push of a button.
Type /timer to keep your retrospective meeting on track.
Set timer for:
There are no rows in this table
1. Add individual feedback
What went well
Add action item
2. Reveal feedback and vote on topics to discuss
show everyone’s answers
3. Discuss feedback 👆 and add action items 👇
🍒 Bonus: Slack the task to each assignee with the push of a button! Note: You need to first connect your Slack workspace with this doc.
Need better tools for staging environment
Mobile app click path needs adjustment
Set up new cadence for communicating out tooling updates