Meetings

Sprint retrospective template

What went well, what didn't and what to try next, ending in two or three owned actions.

Use this template Draft a variant with AI

🔁

Retro: sprint 25

Everyone writes notes alone for 5 minutes, then we group them and vote. Three votes each.

Check last retro's actions

Ben: cap work in progress at two tickets per person

Lea: write a definition of done for design tickets (carried over)

What went well

CSV export shipped two days early

Pairing on the billing bug cut the fix from a week to two days

Fewer meetings on Wednesdays, people noticed

What didn't go well

Three tickets came back from QA because acceptance criteria were vague (4 votes)

Staging was down for most of Tuesday

We started the pricing test before the tracking was checked

Ideas

Write acceptance criteria as a to-do list inside each ticket (5 votes)

A short staging health check after every deploy (3 votes)

Rotate who runs the retro

Actions

Lea: add an acceptance criteria checklist to the ticket template, by Monday

Ben: staging smoke test script in the deploy pipeline, this sprint

Sam: runs the next retro

Mood

Average 3.8 out of 5, same as last sprint

This is the page you get. Every block and row is editable.

What it is

A retrospective looks back at a sprint or project and decides what to change. Everyone writes notes alone first, so the loudest voice doesn't set the agenda. Then the team groups notes, votes and agrees on two or three actions with owners. The first thing on the next retro is checking whether those actions happened.

When to use it

At the end of every sprint or project phase
After a launch that felt harder than it should have
When the same problems keep coming back

How to use it

01
Check last time's actions
Start by ticking off or carrying over the previous retro's to-dos. If nothing changed, say so.
02
Collect notes in silence
Share the page with edit access and give everyone five minutes to add bullets under each heading.
03
Vote and decide
Add the vote count in brackets. Turn the top ideas into to-dos with a name and a date.
04
Summarise for others
Select the page and use Ask AI to summarise it in five lines for people who weren't there.

Or have the AI draft your version

"Draft a retrospective page in the start, stop, continue format for a marketing team after a product launch, with a section to review last retro's actions and a mood check."

Draft a variant with AI

All templates

🧯
Post-mortem: invoice emails delayed
Blameless. We look at how the system let this happen, not at who pressed the button.
Summary
For 3 hours and 20 minutes, invoice emails queued but did not send. 1,840 invoices went out late. No data was lost.
Impact
1,840 invoice emails delayed by up to 3 hours 20 minutes
37 support tickets
No duplicate or lost invoices
Timeline
08:12 Deploy 4.1.3 goes out with a new email provider setting
08:15 Email queue starts growing
10:40 Support notices tickets about missing invoices, pages on-call
11:05 On-call finds the setting points to the sandbox account
11:20 Rollback to 4.1.2
11:32 Queue drained, all emails sent
Root cause
The production and sandbox email keys share one variable name in two config files. The deploy read the wrong file. Nothing alerted on a growing queue, so we found out from customers.
What went well
Rollback took 15 minutes
Queued emails were kept and sent, nothing had to be re-created
What didn't
2 hours 25 minutes between the problem starting and anyone knowing
Actions
Ana: alert when the email queue is over 200 for 10 minutes, by Friday 23 October
Malik: one config file per environment, rename the sandbox variable
Rosa: template reply for support when emails are delayed
Tobias: email affected customers with an apology
Docs
Incident post-mortem
A blameless write-up of an incident: timeline, impact, root cause and actions that stop a repeat.
Projects
Sprint board
Tickets for the current sprint on a board from backlog to done, with points, type and assignee.
Draft your own with AI
Describe the page you need in one sentence. The AI writes it, and you edit it like any other page.
How the AI works

🔁Sprint retrospective template

Check last retro's actions

What went well

What didn't go well

Ideas

Actions

Mood

What it is

When to use it

How to use it

Check last time's actions

Collect notes in silence

Vote and decide

Summarise for others

Or have the AI draft your version

Related templates

🧯Incident post-mortem

🏃Sprint board

Draft your own with AI

Cookies and storage

Sprint retrospective template

Incident post-mortem

Sprint board