Template · Retro
The retro your team actually does.
Three prompts. Five minutes. One clean digest grouped by Keep / Stop / Start, with action items pulled out and assigned. No 60-minute Zoom, no whiteboard with sticky notes nobody reads.
What people answer
The prompts.
- 01
What should we keep doing?
- 02
What should we stop doing?
- 03
What should we start doing?
- 04
An action item you'll own (optional)
Who it's for
Teams that want a real retro cadence (every sprint, every cycle) without the meeting cost that makes them skip every third one.
What gets posted
The digest.
One message in your team channel. Read it on your own time. No meeting, no scroll-back, no follow-up DMs.
Sprint Retro — Sprint 24
Keep
- PR pairing on Tuesdays — Alex, Riley, Jamie all flagged it
- Async design doc reviews — caught 3 issues before code
Stop
- Wednesday sync — 3 people said it has no purpose
- Reactive Slack-firefighting after 5pm — Casey
Start
- One-paragraph design doc for any PR > 300 lines
- Rotating on-call for support tickets — Riley to draft
Action items
- Riley · Draft on-call rotation by Wed
- Sam · Kill the Wednesday sync, replace with async digest
- Alex · Write the design-doc template
Common questions
The stuff people ask.
How often does it run?
Default is every other Friday. You can switch to weekly or monthly per meeting in the dashboard.
Can people skip?
Yes, same as standup — one click in the DM. Skip is honest data, not silence.
What about action items — do they get tracked?
Each person can flag one action item they own. Action items appear in the digest as a checklist with the owner's name. They surface again in the next retro digest as a follow-up reminder.
Or try another
Same shape. Different meeting.
Ready when you are