Skip to content
Gallery
Retrospective Template: How to run an inclusive meeting in 30 minutes
Share
Explore

icon picker
Retrospective Template: How to run an inclusive meeting in 30 minutes

Copy this template certified by Product School to collect feedback after a launch and ensure that everyone's voice is heard.

What is a retrospective meeting?

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.
Copy doc

Retrospective Checklist

(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.

Meeting timer
Type /timer to keep your retrospective meeting on track.
Set timer for:
00
10
minutes
1
Start timer
Reset
There are no rows in this table

Time left:
0:00
10 MINS

1. Add individual feedback


What went well
Needs improvement
Category
Idea
Author
Upvote
Add action item

5 MINS

2. Reveal feedback and vote on topics to discuss

show everyone’s answers

15 MINS

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.

Action Items
Done
Task
Feedback item
Assignee
Due Date
Send Slack
1
Need better tools for staging environment
Tighter integrations
BD
Buck Dubois
3/8/21
Slack assignee
2
Mobile app click path needs adjustment
Tighter integrations
JB
James Booth
2/8/21
Slack assignee
3
Set up new cadence for communicating out tooling updates
Better tooling
PR
Polly Rose
3/9/21
Slack assignee
4
Do analysis of all tools
Better tooling
FM
Felix Marlin
2/8/21
Slack assignee
5
Keep staging and prod more in sync
Better tooling
AD
Adam Davis
2/28/21
Slack assignee
There are no rows in this table


Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
CtrlP
) instead.