Retrospective templates
Retrospective templates Updated

Start Stop Continueretrospective template

When the team understands the problem but keeps circling the same options, Start Stop Continue gives the conversation somewhere to go. Each column asks for a decision about a behavior, meeting, or delivery practice.

Create account to use this template Compare all templates
Duration
30–40 minutes
Team size
3–12 people
Best for
Tuning team habits and turning ideas into direct process decisions
Start / Stop / Continue retrospective template preview

What each column means

Use the prompts to keep cards specific. The examples show the level of detail that makes discussion and voting useful.

Start

6

Which new behavior or practice would make the team's work easier?

  • Start refining risky stories before planning.
  • Start pairing when a service is unfamiliar.
  • Start setting aside one stand-up each week to check every open action item.
  • Start recording each decision beside the exact piece of work it affects.
  • Start inviting customer support to discovery reviews.
  • Start protecting two meeting-free focus blocks for the team to use every week.

Stop

6

Which habits create waste or confusion, and where could the team remove avoidable friction from its day?

  • Stop adding work after the team agrees on the sprint goal.
  • Stop holding decision-free status meetings.
  • Stop merging large changes before writing a rollout plan.
  • Stop assigning an action until it has a named owner and a date when the team will review it.
  • Stop responding to every message as if it were urgent.
  • Stop letting blocked work sit when a dependency needs escalating.

Continue

6

Which practices already help the team and need deliberate protection in the next iteration?

  • Continue sharing demos ahead of release.
  • Continue rotating incident lead duties across different members of the team.
  • Continue writing short decision records.
  • Continue pairing whenever a change brings risk that is unfamiliar to the team.
  • Continue asking for feedback while the solution is still rough.
  • Continue reviewing one action weekly.

30–40 minutes agenda

A complete path from framing the room to assigning one concrete follow-up.

  1. 01

    Frame the review

    Name the sprint or project being reviewed, restate the purpose of each column, and remind everyone to describe observable events.

    3 minutes
  2. 02

    Write observations silently

    Give everyone uninterrupted time to add one specific observation per card across every column.

    7 minutes
  3. 03

    Share and clarify

    Read the cards column by column and let authors add context without debating solutions yet.

    7 minutes
  4. 04

    Group and vote

    Combine cards that describe the same pattern, then vote for the themes that would most improve the next iteration.

    5 minutes
  5. 05

    Discuss the leading themes

    Explore causes, consequences, and tradeoffs behind the highest-voted themes while making space for dissenting evidence.

    10 minutes
  6. 06

    Commit to one change

    Turn the strongest insight into a small action with an owner, deadline, and signal the team can review next time.

    5 minutes

Use this format when

  • The team wants to make a few direct changes to how it works.
  • An earlier experiment has run long enough for the team to decide its next step.
  • The retro needs a short list of practical actions.

Choose another format when

  • The causes behind a sensitive problem still need more time before the team can name them.
  • People are likely to aim Stop cards at individuals.
  • The group needs space to process how the situation affected them before deciding what to change.

Facilitation tips

  • Write each card about a team behavior. Leave personal judgments out.
  • When someone suggests a new practice, ask which old habit will make room for it.
  • Give useful Continue cards enough time, even when complaints fill the board.
  • Choose changes the team can control.
  • Bring the chosen change back to the next retrospective and check what happened.

Useful variations

Personal Start Stop Continue

Ask each person to choose one working habit for themselves, then agree on one team action.

Meeting reset

Keep every card focused on recurring meetings: who attends, how people prepare, and which decisions get made.

Product delivery

Use the three prompts for discovery, handoffs, quality checks, and the release flow.

Before the retro

Recommended warm-up

This or That icebreaker game preview

This or That

Use a quick, low-pressure choice round before the retrospective begins.

Play the warm-up

Frequently asked questions

What is a Start Stop Continue retrospective?

Start Stop Continue is a three-column retrospective for deciding which practices to begin, remove, or preserve in the next iteration.

What are good Start Stop Continue examples?

A useful card names a behavior the team controls. Examples include starting risk reviews earlier, stopping mid-sprint scope changes, and continuing with small pull requests.

How many actions should the team choose?

Choose one or two changes, give each a clear owner, and leave enough room to follow through after the meeting. Long lists fade fast.

How long does this retrospective take?

Set aside 30 to 40 minutes for a team of three to twelve. That covers silent writing, voting, discussion, and choosing an action.

Related resources

Run this Start Stop Continue Retrospective

Open the ready-made columns, invite the team, collect observations, vote, and leave with an owned improvement.

Create account to use this template