Start, Stop, Continue: Turn Feedback into Focused Team Action
Start, Stop, Continue helps managers turn vague performance feedback into practical, forward-looking guidance that motivates teams and clarifies priorities.
Topic: Communication
Why It Matters
Feedback conversations often fail not because managers lack good intentions, but because the structure is wrong. Without a clear framework, discussions drift toward generalities. Positive observations get buried under criticism. Team members leave unsure what they are supposed to do differently, and the person giving feedback is often equally unclear about what they have actually asked for.
Start stop continue feedback is a structured approach designed to solve this problem directly. It divides feedback into three clear prompts: behaviours to begin adopting, behaviours to discontinue, and behaviours to sustain. Applied in team retrospectives, one-to-one reviews, project post-mortems, or leadership development programmes, it turns what might otherwise be a shapeless conversation into a focused list of agreed actions.
Before reading further, it is worth asking whether this tool fits your current situation. Do your feedback conversations tend to end without a clear set of actions, leaving participants uncertain what to change? Are you looking for a method that encourages candid peer input without requiring a formal HR process or extensive facilitation experience? Have you recently completed a project or significant phase of work and want to capture lessons while they are still fresh? If one or more of these describes your situation, this framework is a practical starting point.
Origin and Underlying Logic
At its core, start stop continue is a structured behavioural feedback method. The underlying logic is that feedback anchored in specific, observable actions is more likely to be absorbed and acted on than feedback that addresses general impressions or character traits. Behavioural specificity reduces defensiveness, increases clarity, and makes it easier for the recipient to translate the observation into a concrete next step.
The framework's roots are most visible in agile software development, where it became a staple of sprint retrospectives, but the principles it draws on are older. Structured reflection practices, and the idea that reviewing behaviour under three distinct lenses produces better outcomes than unstructured discussion, have featured in management development and organisational psychology for decades.
Related frameworks include the 4Ls retrospective (Liked, Learned, Lacked, Longed for), the DAKI method (Drop, Add, Keep, Improve), and the broader tradition of after-action reviews used in military and consulting contexts. Start stop continue occupies a useful middle ground: more structured than an open debrief, simpler to facilitate than more complex retrospective formats.
Structure and Application
The start stop continue feedback framework is built around three prompts, each targeting a different dimension of behaviour or practice.
The Start prompt asks what should be adopted that is not currently being done. This is the aspirational, forward-looking element. It captures new practices, habits, or skills that would add value if introduced, and gives participants a constructive way to express dissatisfaction with the status quo without framing it as personal criticism.
The Stop prompt asks what should be discontinued because it is not working, is consuming resources without return, or is actively creating problems. This is typically the most sensitive element of the session. It benefits from careful facilitation to ensure contributions stay focused on behaviours and outcomes rather than personalities.
The Continue prompt asks what is currently working well and should be protected. This anchors the session in genuine recognition, prevents the discussion from skewing entirely negative, and surfaces practices the team may be taking for granted.
The framework can be applied at the individual level in a one-to-one review, at the team level as a structured retrospective, or at the organisational level during strategy or leadership reviews. The format it takes in practice varies: a three-column whiteboard in a workshop setting, a structured form collected in advance of a meeting, or an anonymous digital survey that feeds into a facilitated discussion. In all cases, the visual or physical representation is a table with three columns, one for each prompt, which makes it easy to group themes, spot patterns, and move toward action.
The most valuable first step is to run the exercise on a recently completed piece of work, starting with your own written responses across all three prompts before asking your team to contribute. Beginning with your own input sets a tone of reciprocity and ensures the session opens with something concrete rather than a blank page. What you choose to put in the Stop column, and how you frame it, will set the tone for everything that follows. That question, and the facilitation decisions it requires, is what the deep dive addresses in detail.
FAQ
Q: What is the start stop continue feedback framework?
A: Start stop continue is a structured feedback method organised around three prompts: what should we start doing, what should we stop doing, and what should we continue doing. It is used in team retrospectives, one-to-one reviews, and project debriefs to convert general observations into specific, actionable feedback. Its value lies in the balance it enforces: every session surfaces positives alongside areas for improvement.
Q: How does start stop continue differ from other retrospective formats?
A: Compared to formats such as 4Ls or DAKI, start stop continue is the most direct and the easiest to introduce with teams that are new to structured feedback. Every contribution maps clearly to one of three categories without ambiguity, which lowers the facilitation burden considerably. Teams that want greater nuance, for example separating incremental improvements from wholesale changes, may find value in more differentiated formats once they are comfortable with the basics.
Q: Does start stop continue work for small teams?
A: It works well for teams of almost any size, though the approach to collection and discussion may need to adapt. With very small teams of three to five people, an open conversation is usually sufficient. With larger groups, collecting written responses before the facilitated session produces more candid and varied input, and prevents the discussion from being shaped by whoever speaks first.
Q: How do I know whether start stop continue is the right tool for my situation?
A: The framework fits best when there is a specific window of work or behaviour to reflect on, when you want the feedback to be balanced rather than purely critical, and when you need a structure that can run comfortably within an hour. It is less well suited to sensitive one-to-one conversations where individual accountability needs to be addressed privately, or to settings where the team lacks sufficient psychological safety to share candid feedback openly.
Q: How often should a team run start stop continue?
A: Most teams benefit from running it at natural pause points: the end of a project phase, the close of a quarter, or after a significant event. Running it too frequently reduces the quality of contributions, as participants struggle to identify meaningful changes over short intervals. For teams in active delivery, every four to eight weeks tends to be the right cadence.