Retrospective Templates
Retrospective templates that move teams from reflection into action
Strong retrospectives do three things well: they capture honest input, make themes visible, and narrow the conversation toward the smallest next action worth taking. These templates are built for that flow rather than for endless sticky-note sprawl.
Works for 30, 45 and 60 minutes
Better than free-form venting
Easy transition into prioritization
Useful for product, engineering and ops teams
Template table
Five retrospective structures that hold up under real team pressure
| Template | Best when | Core prompts | Recommended MentorSparks flow |
|---|---|---|---|
| Start / Stop / Continue | The team needs a simple reset with clear behavioral outcomes | What should we start? stop? continue? | Whiteboard capture, cluster notes, then ranked voting on changes |
| Mad / Sad / Glad | Emotional texture matters because the last sprint or project was intense | What frustrated us? disappointed us? energized us? | Anonymous board first, then facilitator-led synthesis |
| Keep / Drop / Try | You want lighter language than start-stop-continue while keeping action bias | What should we keep? drop? try next? | Board, quick poll on theme importance, then final vote |
| 4Ls | The team needs both learning and emotional reflection | What did we like, learn, lack, long for? | Whiteboard groups followed by action selection |
| Timeline retro | You need shared memory before diagnosing what happened | What happened, when did it shift, where were the turning points? | Board-based timeline, then discussion and ranked priorities |
Time-boxes
What to do in 30, 45 or 60 minutes
30-minute retro
Choose one simple structure, gather short notes fast, cluster only the obvious patterns, and end with one ranked action. This format works when the team already shares context.
45-minute retro
Add more room for clarification and discussion. This is the sweet spot for most delivery teams because it supports note capture, pattern review and a visible decision close.
60-minute retro
Use the extra time when the team needs a timeline, a more emotional structure, or deeper discussion about what should change across multiple workflows.
Facilitator notes
How to keep a retro from becoming another complaint meeting
Signal safety first
- Use anonymous input when the team is tense or the hierarchy is visible.
- Ask for observations before explanations so the room builds a shared picture first.
- Cluster similar notes out loud to make synthesis transparent.
- Close with one or two next actions, not a long wish list.
Keep the flow tight
- Whiteboard first for idea capture.
- Discussion second to interpret the patterns.
- Collective Voting last to decide what earns follow-through.
- Use Session Control if the retro sits inside a longer meeting block.