Gather feedback

Run a Team Retrospective to improve your processes

Copy this doc ☝️ and share it with your team to get started.

Steps to take when starting a retrospective. Add your feedback on the project below:

Step 1 (pre-work): Share this Playbook and the attached Coda document out to your team and explain the reason for running a retrospective in the customize section.

Step 2: Warm up the “room”. If your project was challenging, participants might feel nervous to talk about it. As you begin this Playbook, emphasize that the purpose is to understand how things went in a light, positive way.

Step three: Reflect on your project. Gather feedback from your team on possible missteps and how you can improve next time.

Step four: Identify top themes. For example, if you notice many points about working together, you could create a collaboration theme. Or if people are saying things felt rushed, you could create a timeline theme. If you notice the same themes repeatedly, set goals as a team and decide effective ways to manage them.

Step five: Decide on the next steps. After you’ve decided on your top three to five themes, ask the group to identify any to-dos or follow-ups. When you’ve got a good list, assign owners and due dates.

We recommend running a Retrospective with your team every couple of weeks or at the end of a project milestone.

You will only see your own feedback below. When you're finished go to

Review⁠

to see everyone else's.

⁠

Add what you could do next time

⁠

What we could do next time

What we could do next time

Thought

Type

Added by

There are no rows in this table

⁠

Add what went wrong

⁠

What went wrong

What went wrong

Thought

Type

Added by

There are no rows in this table

⁠

Add what went great

⁠

What went great

What went great

Thought

Type

Added by

There are no rows in this table

⁠

Need more context? Read up on how to hold a

sprint retrospective⁠

⁠

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.