Planning

Retrospective template

What went well, what to improve and action items

Preview of the Retrospective template

What’s inside

Nodes
10
Packs
BoardsCore
Category
Planning

Works on the Free plan: 15 diagram nodes + 150 notes, text, stickers & mind map topics per diagram.

A retrospective is a short meeting where a team looks back at a sprint or a project and decides what to change. This template opens a board with three columns, what went well, what to improve, and action items, with three sample notes in each, from a shipped feature to slow CI builds.

Notes stay in their columns, the column under the cursor lights up as you drag, and the board grows as the team adds observations. Because the board autosaves and keeps revisions, the action items are still there at the next retro, which is usually where follow-through breaks down.

When to use it

  • Closing a sprint, a release, or an iteration with the team.
  • Reviewing a project, launch, or incident once it is finished.
  • Collecting feedback after a workshop, a course, or an event.
  • Checking how a new process or team setup is working out.

How to use it

  1. Ask everyone to add notes to the first two columns, one observation per note, before discussing them.

  2. Group similar notes, talk through the biggest themes, and mark the ones to act on with a sticker or a stamp.

  3. Write at most three action items, each with an owner and a date.

  4. Share the board link with the team, and open it again at the start of the next retrospective.

Questions

Can we use start, stop, continue instead?

Yes. The Boards pack in the library also includes start, stop, continue, the 4Ls, and mad, sad, glad as ready-made boards, so you can change the format from one retro to the next.

How do we keep action items from being forgotten?

Keep the list short, give every item an owner, and begin each retro by reviewing the previous board. Revision snapshots show how the list changed over time.

Related templates

Related use case

Retrospective boards

Open a canvas in a minute

Sign in with Google or GitHub. Free for a single seat. Upgrade when the team joins.