Start Stop Continue retrospective: template and examples
A simple Start Stop Continue template for team retrospectives — with filled-in examples and a step-by-step facilitation guide.
Many retrospectives end with broad discussion and very little change. A Start Stop Continue template helps teams turn team feedback into concrete next steps in about 30 minutes. It helps people see what to add, what to remove, and what is already working.
What is Start Stop Continue?
Start Stop Continue is a retrospective format built around three simple prompts. It helps a team decide what to begin doing, what to remove, and what is already worth keeping. That gives a team retrospective more structure than open discussion and usually takes less time than other formats. It is simpler than 4Ls, and it also moves faster than Mad Sad Glad. This makes it useful for an agile retrospective, though it works just as well for product, marketing, ops, and client teams.
Column | Question | Focus |
|---|---|---|
Start | What should we start doing? | New practices that would help the team |
Stop | What should we stop doing? | Things that slow the team down or cause friction |
Continue | What should we keep doing? | Practices that are working well |
For agile teams, Start Stop Continue works well as part of the sprint retrospective.
Start Stop Continue retrospective template
Use the structure below for your next retrospective. This works as a retro template when the team needs something quick and easy to fill in together. It also works as a Start Stop Continue retrospective template when you want a repeatable format without extra setup.
START | STOP | CONTINUE |
|---|---|---|
What new practices should we adopt? | What is slowing us down or causing friction? | What is working well and should be kept? |
1. | 1. | 1. |
2. | 2. | 2. |
3. | 3. | 3. |
Action items → | Action items → | Keep doing → |
Keep the first pass short. Three notes per column are usually enough, and the meeting only becomes useful when the Start and Stop notes turn into real action items.
Start Stop Continue examples
The two options below show how a Start Stop Continue retrospective template can work for different teams without turning into vague process talk.
Example 1: Software team (end of sprint)
START | STOP | CONTINUE |
|---|---|---|
Writing acceptance criteria before sprint planning | Holding daily standups for 30+ minutes | Pairing on complex tasks |
Sharing a weekly team update doc | Adding tasks mid-sprint without discussion | Friday demo sessions |
Defining “done” for each task upfront | Skipping retrospectives when we’re busy | Slack thread for blockers |
Example 2: Marketing team (monthly review)
START | STOP | CONTINUE |
|---|---|---|
Creating a content brief before writing | Reporting on vanity metrics (impressions only) | Weekly content calendar review |
A/B testing email subject lines | Last-minute design requests to the team | Cross-posting to LinkedIn after publish |
Documenting campaign results in one place | Chasing approvals over Slack DMs | Monthly competitor review |
These Start Stop Continue examples work because the notes are specific enough to act on. “What went well” only helps when the answer points to something the team can keep doing on purpose.
How to run a Start Stop Continue retrospective
If you are wondering how to run it, keep the session simple and time-boxed. This retrospective format works best when the team moves through the steps in order and leaves with a short list of action items.
- Set the stage (5 min) — explain the format and remind the team that the conversation is about process, not people. Anonymous input often works better for Stop items.
- Individual brainstorm (10 min) — everyone writes their ideas silently. Three to five notes per column is usually enough.
- Share and group (10 min) — read the notes aloud and group similar items together. Do not start discussing them yet.
- Vote on priorities (5 min) — give each person three votes. The highest-voted items should be addressed first.
- Define action items (10 min) — for each top item, decide who will do what by when. If there is no owner, it probably will not happen.
For Start Stop Continue for remote teams, use a shared board or document so everyone can add notes at the same time. That supports continuous improvement and also works asynchronously.
How to run Start Stop Continue in Vaiz
You can run this retrospective in Vaiz in two simple ways — with a board or with a document. Check below how every option works.
Option 1: Board with three columns
Create a board with Start, Stop, and Continue. Team members add cards during the retro, then the top items become action tasks with owners and due dates — right on the same board.
Option 2: Document
Create a document in Vaiz, paste the three-column template above, and fill it in collaboratively during the meeting. Action items can be converted into tasks linked to the document.
Conclusion
Start Stop Continue template works because it stays concrete. Teams are often quick to add new habits, though the Stop column is usually where the real progress begins. The key part is follow-through. Turn the top notes into action items with owners, or the retro becomes just another conversation.