Start Stop Continue: A Simple Framework for Actionable Team Feedback
Start stop continue is a structured feedback and retrospective framework that organizes insights into three categories: things to start doing (new beneficial actions), things to stop doing (ineffective practices to eliminate), and things to continue doing (effective behaviors to maintain). Teams collect input from all participants, discuss and prioritize items in each category, then convert them into concrete action items for the next cycle.
Overview
The start stop continue framework is one of the most widely adopted retrospective and feedback methods in modern teamwork. Its power lies in radical simplicity: by asking participants to sort their observations into just three buckets — Start, Stop, and Continue — it transforms unfocused discussion into a clear, actionable improvement plan. Originally popularized in agile software development retrospectives, the method has since spread to performance reviews, team meetings, personal development, and organizational change initiatives across every industry.
The framework works because it balances forward-looking ambition (Start) with honest self-assessment (Stop) and positive reinforcement (Continue). Unlike open-ended feedback sessions that can spiral into complaint forums or vague aspirations, start stop continue forces specificity. Each item naturally implies an action: adopt a new practice, abandon a harmful one, or deliberately sustain something that's working. This structure makes follow-through measurable and accountability straightforward.
Whether you're a Scrum Master running a sprint retrospective, a manager conducting a quarterly review, or an individual reflecting on personal habits, start stop continue provides a shared vocabulary for improvement. It's low-friction enough for a 15-minute standup exercise and robust enough to drive strategic team transformation over multiple cycles. When combined with prioritization and ownership assignment, it becomes a lightweight continuous improvement engine.
In Hamster Studio, teams can run start stop continue sessions with AI-assisted facilitation — automatically categorizing feedback, identifying patterns across multiple retrospectives, and generating suggested action items. This turns a simple exercise into a compounding knowledge system where every cycle builds on the last.
How It Works
Step 1: Set the Context and Ground Rules
Open the session by defining the scope — what time period, project, or topic the team is reflecting on. Establish ground rules: all feedback should be specific and behavioral (not personal attacks), every voice matters equally, and the goal is improvement rather than blame. Allocate a clear timebox for the entire exercise (typically 30-60 minutes for a full team retrospective).
Step 2: Silent Brainstorming
Give each participant 5-10 minutes to independently write down items for each of the three categories: **Start** (what should we begin doing?), **Stop** (what should we cease doing?), and **Continue** (what should we keep doing?). Use sticky notes, a shared digital board, or a start stop continue template. Silent generation prevents groupthink and ensures introverted team members contribute fully.
Step 3: Share and Cluster
Have each participant share their items with the group. As items are shared, cluster related or duplicate items together on the board. This naturally reveals themes — if five people independently say 'stop having status meetings without agendas,' that's a clear signal. The facilitator should read items neutrally and ask clarifying questions without debating merit at this stage.
Step 4: Discuss and Clarify
Walk through each cluster and open brief discussion. The goal is shared understanding, not consensus on every point. Clarify vague items into specific, observable actions. For example, transform 'start communicating better' into 'start posting daily async standup updates in our team channel by 10am.' Timebox discussion to prevent any single topic from consuming the session.
Step 5: Prioritize with Dot Voting
Give each participant 3-5 votes (dot stickers or digital votes) to distribute across all items in any category. Participants vote for the items they believe will have the highest impact. This democratic prioritization prevents the loudest voice from dominating the action plan and surfaces the issues the team collectively cares most about.
Step 6: Assign Owners and Define Actions
For the top-voted items (typically 2-4 per category), convert each into a concrete action item with a specific owner and a deadline or review date. 'Start doing code reviews before merging — Owner: Sarah — Starting next sprint' is actionable. 'We should do better code reviews' is not. Document these commitments where the team tracks their work.
Step 7: Close and Commit
Summarize the agreed action items aloud so the entire team hears the commitments. Thank participants for their candor. Schedule the next start stop continue session and note that the first agenda item will be reviewing progress on today's action items. This closing ritual reinforces that the exercise has real consequences and builds trust in the process.
Step 8: Follow Up in the Next Cycle
At the beginning of the next session, review the action items from the previous round. Did we actually start the things we committed to? Did we successfully stop the practices we identified? Are we still continuing the effective behaviors? This accountability step is what transforms a one-off exercise into a genuine continuous improvement system.
When to Use
- At the end of an agile sprint or project milestone when the team needs a structured way to reflect on what worked, what didn't, and what to try next.
- During performance reviews or 1-on-1 meetings where a manager and direct report want to move beyond vague feedback toward specific behavioral changes and reinforcements.
- When a team is experiencing friction or declining performance and needs a low-stakes, inclusive format to surface issues without blame.
- As a regular cadence exercise (weekly, biweekly, or monthly) for teams committed to continuous improvement and want a lightweight framework that doesn't require specialized training.
- When onboarding new team members or forming a new team, as an icebreaker exercise that simultaneously establishes norms for open communication and iterative improvement.
When Not to Use
- When the team lacks psychological safety — if people fear retaliation for honest feedback, the 'Stop' category will be empty or sanitized, and the exercise produces misleading results.
- For deeply complex or systemic organizational problems that require root cause analysis. Start stop continue surfaces symptoms and quick improvements but doesn't replace frameworks like fishbone diagrams or Five Whys for diagnosing underlying issues.
- When there's no intention or capacity to act on the outputs. Running the exercise without follow-through breeds cynicism and makes future retrospectives less effective as participants learn their input is ignored.
- In situations requiring anonymous 360-degree feedback across large organizations. The framework works best in small-to-medium groups (3-12 people) with shared context. Scaling it to hundreds of participants without modification dilutes its effectiveness.
Skills in This Method
Facilitating Start Stop Continue Retrospectives
How to plan, run, and timebox an effective Start Stop Continue retrospective session with your agile team, from setting ground rules to closing with action items.
Using Start Stop Continue in Performance Reviews and 1-on-1 Meetings
How to adapt the Start Stop Continue framework for individual performance conversations, manager check-ins, and self-reflection outside of team retrospectives.
Running Start Stop Continue as a Team Icebreaker Activity
How to use a lightweight Start Stop Continue exercise as a warm-up or icebreaker to build psychological safety and normalize giving feedback in new or forming teams.
Categorizing and Prioritizing Feedback Items
How to sort, group, and dot-vote on collected Start, Stop, and Continue items to identify the highest-impact actions the team should commit to next.
Building Start Stop Continue Templates and Worksheets
How to design reusable templates, worksheets, and digital boards (Miro, Google Docs, Notion) that structure the feedback collection and make sessions efficient.
Writing Effective Start Stop Continue Feedback
How to write clear, specific, and constructive feedback items in each category—avoiding blame, staying behavior-focused, and making each item immediately actionable.
Crafting Actionable Start Stop Continue Questions and Prompts
How to write and select targeted questions for each Start, Stop, and Continue category that elicit specific, constructive, and actionable feedback rather than vague responses.