Stop / Keep / Start Retrospective

What is Stop / Keep / Start?

Stop / Keep / Start is a lightweight retrospective format that organizes team feedback into the three values from the Stop / Keep / Start preset:

The format is popular because it is easy to explain and hard to overcomplicate. Instead of asking a broad question like “How did things go?”, the facilitator gives the group three practical lenses for improvement.

For example:

• Stop: “Starting meetings without a clear decision goal.”
• Keep: “Sharing customer feedback before planning.”
• Start: “Writing one decision owner for every action.”

You may also see the same method called Start / Stop / Continue, Stop / Start / Continue, or Keep / Stop / Start. In most facilitation contexts, these are naming and ordering variants of the same basic activity.

When to use it

Use Stop / Keep / Start when you want a team to reflect quickly and leave with concrete next steps.

It works well for:

• sprint retrospectives,
• project debriefs,
• workshop or training evaluations,
• quarterly team check-ins,
• process improvement conversations,
• remote and hybrid team retrospectives,
• new teams learning how to reflect together.

It is especially useful when the group needs a balanced conversation. The Stop column surfaces friction, the Keep column protects what is already working, and the Start column turns the session toward experiments and decisions.

Adapt the format when the group needs deeper emotional processing, when there is unresolved conflict, or when leaders are asking for feedback but are not prepared to act on it. In those cases, spend more time on psychological safety, choose a more diagnostic retrospective format, or reduce the scope of the conversation.

How to run it

A simple Stop / Keep / Start retrospective usually takes 20–45 minutes.

Tools and setup

You can run this retrospective with almost any shared surface. The tool matters less than the structure: three clear columns, quiet writing time, a way to review the board together, and a place to capture actions.

Low-tech and general-purpose tools

For an in-person session, a physical whiteboard and sticky notes work well. For remote or hybrid groups, you can use three columns in a shared document, a spreadsheet, a generic online whiteboard, or a collaborative workshop board.

Set up columns labeled Stop, Keep, and Start. Give participants a short timebox to add notes, then review the board, optionally vote on priorities, discuss, and select actions.

The format is simple; the facilitation challenge is follow-through. In remote or larger groups, the board can become messy, duplicate cards take time to organize, and action items can disappear after the meeting unless someone captures owners and review dates carefully.

Using Stormz

Stormz is designed to make this retrospective quick to launch and easy to facilitate, while still giving you powerful controls when the conversation gets complex.

You can start from the Stop / Keep / Start preset in a quick launch flow, open the workshop, and invite participants with a join link or QR code. People can contribute in parallel, and Stormz keeps the cards organized in the right columns from the start.

For remote and hybrid sessions, Stormz also supports Zoom-based contribution through Meeting Bot. When chat capture is enabled, participants can add ideas from the Zoom chat without opening Stormz, which is useful when you want very low-friction participation in a webinar, training, or large meeting.

The biggest facilitation benefit is what happens after cards arrive. AI auto-tagging can detect recurring themes automatically, and the Tag cloud view gives you a fast debrief surface: open a theme, read the matching cards, and connect the discussion back to participants’ own words.

Stormz also helps you control the rhythm of the activity. You can run everything at once, or use the Kanban view to fold columns so the group focuses on Stop first, then Keep, then Start. If there are too many topics to discuss, you can create and start a Dot Voting session so participants distribute their dots and the group can prioritize together.

This makes Stormz especially useful when the retrospective is remote, hybrid, or large, including sessions with hundreds of participants. The facilitator does not have to spend the session sorting cards manually. Stormz handles the structure, AI helps surface the patterns, and the group can spend more time on the conversation that matters.

Facilitation tips

Variations

• Start / Stop / Continue: the most common naming variant. “Continue” plays the same role as “Keep.”
• Stop / Start / Continue: starts with friction, then moves quickly toward new behaviors and useful practices.
• Keep / Stop / Start: starts with what is working, which can create a more positive tone before discussing friction.
• Sequenced prompts: run one column at a time instead of opening all three at once. This is useful when the group needs more focus or when the facilitator wants to shape the emotional arc of the discussion.
• Deeper prompt version: add sub-questions under each column. For example, under Stop you might ask about meetings, decisions, delays, handoffs, or unclear responsibilities. Use generic prompts when they fit, or write context-specific prompts for the workshop.
• Personal Stop / Keep / Start: each person chooses one personal behavior to stop, keep, and start.
• Project debrief: focus the prompts on a completed project, launch, training, or client engagement.
• Meeting retrospective: use the three columns to improve a recurring meeting.
• Action-first version: require every final Start card to include an owner and review date.
• Prioritized version: add dot voting after discussion when there are too many themes to address.

Common mistakes

• Treating Stop as a place to collect complaints without making decisions.
• Spending the whole session on problems and skipping what the team should keep doing.
• Accepting vague cards without asking for concrete examples.
• Creating too many Start actions at once.
• Skipping quiet writing time and letting the loudest voices set the agenda.
• Voting too early, before people understand the cards.
• Letting the facilitator interpret the board for the team.
• Ending without owners, deadlines, or a follow-up review.
• Reusing the same format every time until the team stops paying attention.

Source note

Stop / Keep / Start is a common retrospective and feedback format with no single confirmed originator for the team-retrospective version. It is closely related to the widely used Start / Stop / Continue format and to the Stop / Keep Doing / Start feedback model sometimes attributed to Phil Daniels through later sources.

This article treats those variants as part of the same practical facilitation family while avoiding a definitive origin claim.

FAQ