Performance reviews and team retrospectives work best when feedback is clear, balanced, and easy to act on. The Start, Stop, Continue framework helps managers, employees, and teams turn observations into practical next steps by separating feedback into three simple categories: what should begin, what should end, and what should keep going.
TLDR: The Start, Stop, Continue method helps teams improve performance by making feedback specific and action oriented. For example, a product team might decide to start weekly risk reviews, stop adding last minute scope changes, and continue using sprint demos to align stakeholders. In one common scenario, a team that reduces recurring meeting time by 25% and increases written updates can save several hours per person each month. The framework is useful for both individual performance reviews and group retrospectives because it encourages balanced, constructive discussion.
What Is the Start, Stop, Continue Framework?
The Start, Stop, Continue framework is a feedback model used to identify behaviors, habits, and processes that need attention. It is especially effective because it avoids overly vague feedback such as “communicate better” or “be more proactive.” Instead, it pushes reviewers and teams to define specific actions.
- Start: New behaviors, systems, or routines that could improve performance.
- Stop: Ineffective habits, blockers, or practices that reduce productivity or morale.
- Continue: Strengths, successful routines, or positive behaviors that should be maintained.
In a performance review, the model helps an employee understand what growth looks like in practical terms. In a retrospective, it helps a team agree on changes without turning the conversation into blame.
How to Use These Examples Effectively
These examples can be adapted for managers, direct reports, project teams, or cross functional groups. The most useful feedback is specific, time based, and connected to outcomes. For instance, “Start sharing weekly project risks by Friday afternoon” is stronger than “Start communicating more.”
Reviewers should also balance the three categories. If a review contains only “Stop” items, it may feel discouraging. If it contains only “Continue” items, it may lack growth direction. A balanced discussion builds trust while still encouraging improvement.
20 Start, Stop, Continue Examples
1. Communication
- Start: Sharing project updates before stakeholders ask for them.
- Stop: Relying on informal chats for decisions that affect the whole team.
- Continue: Summarizing key decisions in writing after important meetings.
2. Meeting Effectiveness
- Start: Sending agendas at least 24 hours before recurring meetings.
- Stop: Inviting people who do not need to contribute or make decisions.
- Continue: Ending meetings with clear owners and deadlines.
3. Time Management
- Start: Blocking focused work time for high priority tasks.
- Stop: Switching between too many tasks without completing key deliverables.
- Continue: Prioritizing work based on business impact and urgency.
4. Collaboration
- Start: Involving relevant teammates earlier in the planning process.
- Stop: Working in isolation on tasks that require shared input.
- Continue: Offering help when colleagues face blockers.
5. Leadership
- Start: Delegating responsibilities with clearer expectations and success criteria.
- Stop: Making decisions without explaining the reasoning behind them.
- Continue: Creating space for team members to share ideas and concerns.
6. Problem Solving
- Start: Bringing two or three possible solutions when raising a problem.
- Stop: Waiting too long to escalate risks that may affect deadlines.
- Continue: Using data and customer feedback to guide decisions.
7. Accountability
- Start: Tracking commitments in a shared system visible to the team.
- Stop: Missing deadlines without early communication.
- Continue: Taking ownership when mistakes occur and correcting them quickly.
8. Customer Focus
- Start: Reviewing customer comments before planning new improvements.
- Stop: Assuming internal preferences reflect customer needs.
- Continue: Responding to customer issues with empathy and urgency.
9. Innovation
- Start: Testing small experiments before committing to large changes.
- Stop: Rejecting new suggestions because they differ from the usual process.
- Continue: Sharing lessons learned from experiments, even when they fail.
10. Quality of Work
- Start: Using a checklist before submitting final deliverables.
- Stop: Rushing work through review without verifying accuracy.
- Continue: Maintaining strong attention to detail on client facing materials.
11. Cross Functional Alignment
- Start: Confirming shared goals with partner teams before execution begins.
- Stop: Creating timelines without checking other departments’ constraints.
- Continue: Keeping stakeholders informed at major milestones.
12. Team Morale
- Start: Recognizing contributions more consistently during team meetings.
- Stop: Allowing unresolved tension to affect group discussions.
- Continue: Celebrating meaningful wins, not only major launches.
13. Remote Work Habits
- Start: Setting clear availability hours and response expectations.
- Stop: Scheduling calls across protected focus time without a clear reason.
- Continue: Using written updates to keep distributed teammates aligned.
14. Learning and Development
- Start: Creating a quarterly skill development goal.
- Stop: Postponing training because urgent tasks always take priority.
- Continue: Applying new knowledge directly to active projects.
15. Decision Making
- Start: Defining who owns a decision before discussion begins.
- Stop: Reopening decisions repeatedly without new information.
- Continue: Documenting tradeoffs so future teams understand the context.
16. Feedback Culture
- Start: Giving feedback closer to the moment when behavior occurs.
- Stop: Saving all feedback for formal review cycles.
- Continue: Framing feedback around behaviors rather than personality traits.
17. Project Planning
- Start: Identifying risks and dependencies during kickoff.
- Stop: Committing to deadlines before estimating the full scope.
- Continue: Breaking large projects into smaller, trackable milestones.
18. Productivity
- Start: Reviewing weekly priorities every Monday morning.
- Stop: Treating every request as equally urgent.
- Continue: Protecting time for high value work that supports strategic goals.
19. Conflict Resolution
- Start: Addressing disagreements directly and respectfully before they grow.
- Stop: Discussing frustrations with uninvolved colleagues instead of the right person.
- Continue: Looking for shared goals when opinions differ.
20. Performance Growth
- Start: Setting measurable goals that connect individual work to team outcomes.
- Stop: Measuring performance only by activity rather than impact.
- Continue: Reviewing progress regularly and adjusting goals when priorities shift.
Best Practices for Reviews and Retrospectives
For performance reviews, managers should prepare examples in advance and connect feedback to observable behavior. A strong review might include one or two points in each category, followed by a short action plan. This keeps the discussion focused and prevents the employee from feeling overwhelmed.
For team retrospectives, facilitators should ask participants to write their Start, Stop, Continue ideas privately before discussion begins. This reduces groupthink and gives quieter team members equal space. After ideas are shared, the team should vote on the most important items and choose only a few actions to implement before the next review cycle.
The framework works best when it becomes a habit. Teams that revisit their commitments regularly are more likely to see measurable improvement than teams that treat retrospectives as one time conversations.
FAQ
What is a Start, Stop, Continue example?
A Start, Stop, Continue example is a piece of feedback divided into three actions. For instance, an employee may be asked to start sharing weekly updates, stop delaying risk communication, and continue producing accurate reports.
How many items should be included in a performance review?
Most reviews work best with one to three items in each category. Too many points can make the feedback difficult to remember and act on.
Can Start, Stop, Continue be used for teams?
Yes. It is commonly used in retrospectives because it helps teams identify process improvements, remove blockers, and reinforce behaviors that already work well.
How can feedback stay constructive?
Feedback should focus on specific behaviors, outcomes, and future actions. It should avoid personal labels and include examples that show why the change matters.
How often should teams use this framework?
Many teams use it monthly, quarterly, or at the end of major projects. The right timing depends on the pace of work and how often the team needs to adjust its process.
