What is the Start Stop Continue Retrospective?
Start Stop Continue is a retrospective format built on three questions: what should your team start doing, what should it stop doing, and what should it keep doing? Every answer is a behavior someone can act on, so the meeting ends with a short list of changes instead of a long list of complaints. Teams use it in agile retrospectives because it needs almost no explanation. Everyone adds ideas to three columns: things to begin (Start), things to drop (Stop) and things that are working and worth keeping (Continue). The structure keeps the conversation on what people actually do, which makes it easy to turn the top items into actions with an owner. It works best when you want concrete changes out of the meeting, with the wins on the table next to the problems. The Continue column is the one teams rush, and it's the one that stops a good habit from quietly disappearing. You'll also see this exercise written as "Stop Start Continue." It's the same thing: the three categories are identical and you can run them in whichever order your team prefers. Some facilitators lead with Stop to clear away what isn't working before deciding what to begin. Others lead with Start to keep the tone forward-looking. Either way, you finish with a short list of behaviors to begin, end and keep. Start Stop Continue is useful well beyond the sprint retrospective. Because it produces specific, behavior-level feedback, teams use the same Start Stop Continue template for peer feedback, manager one-on-ones, project post-mortems and personal goal-setting. In a one-on-one, for example, a report might ask their manager to "start sharing the weekly priorities earlier," "stop scheduling reviews on Friday afternoons" and "continue the open Q&A at standup." The free template above gives everyone a private space to add ideas before the team groups them, votes and agrees on actions together.
Start Stop Continue Retrospective Format
Start
What should we start doing?
This column is for new ideas and improvements. Ask the team where current processes have gaps and which opportunities you've missed. Small fixes and larger strategic changes both belong here.
Stop
What should we stop doing?
This column identifies practices that aren't adding value or are causing problems. Help the team be specific about behaviors to eliminate, and encourage constructive rather than personal criticism.
Continue
What should we continue doing?
This column is for practices that are working. Help the team name what's going well and should be kept, so a good habit doesn't quietly disappear while you focus on the problems.
When to use this retrospective
- When you want a short list of specific actions out of the retro
- During a period of change, to decide which practices to keep and which to drop
- With a new team that needs a simple, familiar way to give feedback
- When discussions keep drifting into the abstract and you need behaviors the team can act on
Suggested icebreaker questions
- What's one positive change you've noticed in our team over the last month?
- If you could instantly implement one improvement to our team's way of working, what would it be?
Want a warm-up your team plays, not just answers out loud? Browse free icebreakers →
Ideas and tips for your retrospective meeting
- Start with the Continue column so the team names what's working before it gets to the problems
- Ask for specific behaviors. "Communicate better" is a wish; "post a summary after every client call" is something you can do
- Give each column real time. If Stop takes the whole meeting, the team leaves with nothing to keep
- Talk about behaviors and practices, not individuals
- Cap the actions at two or three so they actually get done
- Check the last retro's actions at the start of the next one to see what changed