Start Stop Continue Retrospective Template and Facilitation Guide

Introduction

A good retrospective template gives the team enough structure to think clearly without forcing a predetermined answer. The format converts reflection into behavioral choices.

This guide explains the approach in practical terms: what it is, why it is useful, when to use it, how to apply it step by step, and which mistakes to avoid.

What is it?

Start Stop Continue is a three-column retrospective template. Start captures practices the team should introduce, Stop captures behaviors or processes that no longer help, and Continue captures strengths worth preserving.

Why is it useful?

The format converts reflection into behavioral choices. It is simple enough for new teams but broad enough to examine delivery, collaboration, tools, quality, and decision-making. The Continue column also prevents improvement conversations from focusing only on failure.

Benefits

• Easy to explain and quick to prepare.
• Balances new ideas, removal of waste, and protection of strengths.
• Produces action-oriented language.
• Works for sprint, project, leadership, and personal retrospectives.

When should you use it?

Use this template when a team is new to retrospectives, needs a broad process review, has adopted several recent practices, or wants a straightforward format after a complicated session. Rotate to a different format if the same cards repeat every sprint.

How to do it

1. Set the scope. Define the sprint, project phase, or team process being reviewed.
2. Collect Start ideas. Ask what new behavior, tool, agreement, or experiment could improve the next cycle.
3. Collect Stop items. Ask what creates waste, confusion, delay, risk, or unnecessary effort.
4. Collect Continue items. Ask what delivered value, protected quality, or improved teamwork.
5. Group and vote. Combine duplicates and prioritize the items with the greatest expected impact.
6. Convert choices into actions. Select one Start or Stop action and identify any Continue practice that needs explicit protection.

Real example

A design team added Start: include engineering in early concept reviews; Stop: presenting several nearly identical options; Continue: weekly customer-session clips. Voting prioritized early engineering review. The team scheduled a 20-minute feasibility check before high-fidelity work and kept sharing customer clips because they improved decision context.

Common mistakes

• Writing outcomes such as start delivering faster instead of behaviors.
• Treating Stop as a place to criticize individuals.
• Ignoring Continue items after the meeting.
• Creating one action from every high-voted card.

FAQ

Can Start Stop Continue be anonymous?

Yes. Anonymous input can improve honesty, particularly in teams with hierarchy or low trust.

What if an item appears in both Start and Stop?

Clarify the underlying behavior. The team may want to stop one version of a practice and start a more effective version.

How long should the session take?

A focused team can complete it in 45 to 60 minutes.

Conclusion

Start Stop Continue remains popular because it is clear, balanced, and practical. Keep cards behavioral, prioritize aggressively, and protect successful practices as deliberately as you change weak ones.

Call To Action

Create a Start Stop Continue board in SprintsPlans, collect feedback, vote anonymously, and assign the selected improvement before the meeting ends.