Retrospective Template
A framework for team learning after projects, milestones, or sprints.
The Start-Stop-Continue Framework
| Category | Definition |
|---|
| START | In hindsight, what would have made the project go faster/smoother? |
| STOP | In hindsight, what did we do that we should not do in the future? |
| CONTINUE | In hindsight, what went well and we should keep doing (or double down on)? |
Template Structure
Reference Links
Links to relevant project docs, PRFAQs, etc.
Action Items
Capture these during the retro and assign owners + ETAs
- [Action item] (Owner: [Name], ETA: [Date])
START - What should we start doing?
| # | Project/Area | Who | What Happened | Remedy / Action Item | Priority |
|---|
| 1 | | | | | |
STOP - What should we stop doing?
| # | Project/Area | Who | What Happened | Remedy / Action Item | Priority |
|---|
| 1 | | | | | |
CONTINUE - What should we keep doing?
| # | Project/Area | Who | What Went Well | How to Double Down | Priority |
|---|
| 1 | | | | | |
Running the Retrospective
Before
- Schedule 60-90 minutes
- Share the framework in advance so people come prepared
- Assign a facilitator and note-taker
During
- Set context (5 min) - remind everyone of the project/sprint scope
- Individual reflection (10 min) - silent writing
- Share and cluster (20-30 min) - go around, group similar items
- Discuss top items (20-30 min) - prioritize by impact
- Commit to actions (10 min) - assign owners and dates
After
- Distribute notes within 24 hours
- Track action items to completion
- Reference in the next retro: "Did we actually change?"
Tips
- Blameless culture - focus on systems, not individuals
- Specific > vague - "We should communicate better" is useless; "We should post daily standups in Slack" is actionable
- Fewer, better actions - 3 implemented changes beat 10 forgotten ones
- Make it regular - retros work when they're a habit
The goal isn't to document. It's to learn and improve.