Start

What should we start doing?

Regular knowledge sharing sessions to spread expertise across the team
Using a shared calendar for tracking team member availability
Breaking down large tasks into smaller, manageable chunks
Stop

What should we stop doing?

Scheduling meetings without clear agendas
Starting new tasks before completing current ones
Making decisions without consulting all stakeholders
Continue

What should we continue doing?

Our weekly team lunches that help us bond
Rotating meeting facilitators to develop leadership skills
Pair programming sessions for complex features

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

Frequently asked questions

Is it "start stop continue" or "stop start continue"?
They're the same exercise. The three categories are identical and the order is only a matter of preference: some facilitators lead with "Stop" to clear away what isn't working, while others lead with "Start" to keep the tone forward-looking.
What are examples of start, stop, and continue?
"Start" items are new behaviors to begin, for example "start writing a short agenda before each meeting." "Stop" items are unhelpful behaviors to end, such as "stop merging code without a review." "Continue" items are working habits to keep, like "continue the daily 15-minute standup."
How do you run a start stop continue retrospective?
Create three columns (Start, Stop and Continue) and give everyone a few minutes to add ideas privately, so nobody is anchored by the first voice in the room. Group similar items, vote on the ones that matter most, and turn the top two or three into actions with an owner. TeamRetro runs the whole flow, from private brainstorming to voting and action items, with the free template above.
When should you use start stop continue?
Use it when you want concrete, action-oriented feedback instead of an open-ended discussion. It suits regular sprint retrospectives, new teams that need a simple format and periods of change, and it works outside retros for peer feedback, one-on-ones and project post-mortems.
What is Start Stop Continue feedback?
Start Stop Continue is a feedback method that sorts comments into three lists: behaviors to start, behaviors to stop and behaviors to continue. Teams use it in retrospectives, and it works as well for individual and peer feedback. Continue matters most, because people find it easy to name what isn't working and hard to name what is.
Can you use Start Stop Continue for one-on-ones or personal feedback?
Yes, and it transfers to a one-on-one better than most retrospective formats. Each of you brings one thing you want the other to start, one to stop and one to continue, kept to observable behaviors. A one-way Start Stop Continue is a performance review wearing a retrospective's clothes.
What are examples of Start Stop Continue feedback for a manager?
Start: "sharing the reasoning behind a priority change, not only the decision." Stop: "moving our one-on-ones when something urgent comes up." Continue: "sending the written Friday update, because it saves us a meeting." Each names something the manager does and can change, which is what makes it usable. "Be more supportive" is a wish, not feedback.
Ready to run this retrospective?Try this retrospective live