Overview
The Start Stop Continue technique is a versatile way to gather feedback and drive continuous improvement. It originated in Agile software development, but is now used across industries to reflected on what‘s working, what to change, and what to introduce.
This article will provide an in-depth look at how Start Stop Continue retrospectives work, when to use them, what benefits they offer, and real-world examples. We‘ll also overview top Start Stop Continue templates and resources so you can easily apply this technique yourself.
By the end, you‘ll understand how to use Start Stop Continue retrospectives to boost team performance, smooth business transitions, improve marketing results, and more. So let‘s get started!
What is a Start Stop Continue Retrospective?
A Start Stop Continue retrospective is a structured meeting where team members reflect on a recent project or time period and provide feedback on:
- Start: New things to introduce going forward
- Stop: Things to eliminate that haven‘t worked well
- Continue: Successful elements to keep doing
This allows teams to course correct, build on proven tactics, and align everyone on where to focus efforts next. Retrospectives promote continuous improvement through candid, democratized inputs from all team members.
Why Use Start Stop Continue Retrospectives?
Here are the top reasons to use Start Stop Continue retrospectives:
Drive Product/Process Improvements
By spotlighting weak areas and better approaches, teams can refine workflows, boost quality, and enhance outputs. Over 75% of Agile software teams report improved project results after retrospectives. (Source: Scrum Alliance)
Inform Data-Based Decisions
With structured inputs on what has (and hasn‘t) worked, leaders make more informed, objective choices aligned to team insights.
Increase Employee Engagement
82% of employees feel more engaged when their feedback is regularly used to improve processes. Retrospectives provide that feedback channel. (Source: Officevibe)
Promote Continuous Learning
Analyzing wins and failures fosters a growth mindset and knowledge sharing. Teams constantly get better through regular self-assessment.
Enhance Team Relationships
Open conversations build psychological safety and trust. Retrospectives give a venue for teams to authentically connect.
Core Elements of a Start Stop Continue Retrospective
While formats vary, Start Stop Continue retrospectives have some core elements:
Participant Questions
Common questions for individuals to ponder:
- What went well?
- What could be improved?
- What should we do differently next time?
Start, Stop, Continue Columns
These drive the capture of feedback into categories:
- Start – new ideas
- Stop – eliminate elements
- Continue – repeat what works
Voting/Prioritization
Once ideas are gathered, the team votes to prioritize key items under each category. This focuses follow-up work on the high-impact changes.
Action Planning
Choose the top 1-3 items under Start and Stop columns. Define clear next steps, owners, and timelines to drive execution.
How to Run a Start Stop Continue Retrospective
Follow this step-by-step process:
1. Set Goals and Agenda
Be clear on objectives, frame the discussion scope, pick a template to capture inputs.
2. Gather Data
Have team quietly write sticky notes – one idea per note. Add notes to the relevant Start/Stop/Continue column.
3. Group and Summarize
As a team, group related notes together. Read out a summary for each group.
4. Vote on Priority Items
Each person votes on 1-3 priority items per column. Tally votes.
5. Discuss Top Items
Have an open discussion on the top voted Start, Stop, Continue items.
6. Create Action Plans
Decide on 2-3 top items per column to tackle. Define clear plans.
7. Close Meeting
Thank participants. Set next retrospective date. Follow up on action items.
When Should You Conduct Start Stop Continue Retrospectives?
Common occasions suited for Start Stop Continue retrospectives include:
After Completing Milestones – Reflect on what worked/didn‘t in the project.
Business Process Changes – Assess effectiveness of new tools, workflows.
Early Stage Products – Gather user feedback on prototypes/MVPs to refine.
Major Launches – Evaluate what succeeded or needs fixing for optimization.
Strategic Shifts – Understand needed adjustments in direction/operations.
Team Changes – Onboard new folks smoothly by learning past lessons.
Periodic Check-Ins – Foster continuous improvement with regular touch bases.
Real World Examples of Start Stop Continue Retrospectives
Here are some examples across different functions:
New Remote Team‘s Start Stop Continue
Start
- Virtual watercooler chat channel
- Remote working policies
Stop
- Onsite-optimized workflows
- Assumptions remote works less
Continue
- Using project management platforms
- Team meetings
E-Commerce Website Optimization
Start
- Heatmaps to ID navigation issues
- Exit intent popups
Stop
- Stock photos that lack diversity
- Overly promotional language
Continue
- Accurate product descriptions
- AI product recommendation engine
New Manager‘s Start Stop Continue
Start
- Anonymous feedback channel
- 1:1 career conversations
Stop
- Brushing issues under the rug
- Playing favorites
Continue
- Explaining why behind decisions
- Weekly team check-in calls
Start Stop Continue Retrospective Templates
Here are excellent (and free) Start Stop Continue retrospective templates to save prep time:
Simple formatting with columns plus starter sticky notes. Great for whiteboarding.
Robust template with areas for notes, voting, actions. Content outline view.
Digital canvas for gathering notes, voting, and more. Free version available.
Variety of fun, creative templates to engage teams. Has interactive games.
Key Takeaways and Next Steps
The Start Stop Continue retrospective technique drives continuous improvement through candid, constructive feedback. While born in software development, it now powers more aligned, higher performing teams across fields.
Hopefully this overview has shown you why Start Stop Continue retrospectives matter, when to use them, and how to apply in your unique context. Lean on the templates and examples to simplify your own implementation.
Most importantly, remember that listening and responding to employee feedback through these retrospectives builds trust and amplifies results over time. So carve out time to regularly start, stop and continue what matters!
Have you used Start Stop Continue retrospectives before? What key lessons or advice do you have? I‘d love to hear other real-world experiences or recommendations in the comments below!
