Building a Start Stop Continue Template That Teams Actually Use
This skill teaches you how to design reusable start stop continue templates, worksheets, and digital boards in tools like Miro, Google Docs, and Notion so your feedback sessions are structured, efficient, and consistently produce actionable outcomes.
To build a start stop continue template, create three clearly labeled columns or sections—Start, Stop, and Continue—with guiding prompts in each. Add fields for contributor names, dates, and priority votes. Design it in your team's preferred tool (Miro, Google Docs, or Notion) with clear instructions, and include a summary section for capturing action items after discussion.
Outcome: You can create polished, reusable templates that reduce session prep time to near-zero and guide participants to submit higher-quality feedback every time.
Prerequisites
- Basic understanding of the Start Stop Continue framework
- Familiarity with at least one digital collaboration tool (Miro, Google Docs, or Notion)
Overview
A well-designed start stop continue template is the difference between a productive retrospective and a disorganized brainstorm that trails off without action items. Templates remove friction: participants know exactly where to write, what kind of input is expected, and how their feedback will be processed. Without a template, facilitators waste time explaining the format, participants second-guess what to share, and the resulting notes are scattered across sticky notes and chat threads.
This skill covers the structural elements every effective start stop continue template needs—regardless of whether you're building it as a printable PDF, a shared Google Doc, a Notion database, or a Miro board. You'll learn how to choose the right format for your team's context, add prompts that elicit specific and actionable feedback, and build in mechanisms for prioritization and follow-through.
Once you've built your template library, you can pair it with skills like facilitating Start Stop Continue retrospectives and crafting actionable feedback prompts to run sessions that consistently produce real improvements.
How It Works
The core principle behind an effective start stop continue template is structured divergence followed by convergence. In the divergence phase, the template gives each participant a private, clearly delineated space to brainstorm items across all three categories. The structure—separate columns, rows, or sections for Start, Stop, and Continue—prevents the common failure mode where feedback blurs together or stays vague.
In the convergence phase, the template provides mechanisms for grouping similar items, voting on priorities, and recording action items with owners and deadlines. This is where most homemade templates fail: they capture input but don't guide the team toward decisions.
The template also serves a psychological function. By providing guiding prompts and example items, it lowers the activation energy for participation. People who might freeze when asked "What should we stop doing?" can respond to "Name one recurring task or meeting that no longer delivers value." The template does the facilitation scaffolding so the human facilitator can focus on discussion quality.
Finally, a reusable template creates institutional memory. When every retrospective uses the same structure, it becomes trivial to compare feedback across sprints, quarters, or project phases—turning individual sessions into a longitudinal improvement system.
Step-by-Step
Step 1: Choose Your Medium Based on Team Context
Before designing anything, decide where your template will live. This choice should be driven by three factors: how your team already collaborates (use the tool they're already in daily), whether the session is synchronous or asynchronous, and how many participants will contribute simultaneously.
Miro or FigJam works best for synchronous sessions with 4-15 people who benefit from visual clustering and real-time collaboration. Google Docs or Sheets is ideal for asynchronous collection or smaller teams who prefer linear formats. Notion excels when you want a persistent database that accumulates feedback across multiple sessions and supports filtering and tagging.
For hybrid teams, consider a two-tool approach: collect feedback asynchronously in a Notion form or Google Form, then display and discuss it live on a Miro board.
Tip: Don't introduce a new tool just for retrospectives. The best template is one that lives where your team already works—adoption beats aesthetics every time.
Step 2: Design the Three-Column Core Structure
Every start stop continue template needs three clearly separated sections. Label them Start (new actions to begin), Stop (current practices to eliminate), and Continue (effective behaviors to maintain). Use color coding consistently: green for Start, red for Stop, and blue or yellow for Continue is the most intuitive convention.
Within each section, include:
- A one-sentence definition of the category (e.g., "Things we're not doing today that could improve our work")
- 2-3 guiding prompts specific to your team's context
- Individual contribution areas (one per participant for async, or a shared sticky-note zone for sync sessions)
Keep the layout balanced. A common design mistake is making the Start column visually dominant, which unconsciously biases participants toward generating new ideas rather than reflecting on what to stop or continue.
Tip: In Miro, use frames to create the three sections and lock the structural elements so participants can only add sticky notes, not accidentally move the template.
Step 3: Add Guiding Prompts to Each Section
Generic categories alone produce generic feedback. The prompts you embed in each section are what transform surface-level input ("communicate better") into specific, actionable items ("start posting standup updates in Slack by 9:30 AM").
For the Start section, use prompts like: "What's one practice you've seen another team do that we should try?" or "What tool, process, or habit would help us hit our next milestone?"
For the Stop section: "What recurring activity feels like it wastes the most time?" or "What are we doing out of habit that no longer serves our goals?"
For the Continue section: "What's working so well that we'd notice immediately if it stopped?" or "What recent decision or change has had the most positive impact?"
You can explore prompt design in depth with the sibling skill on crafting actionable Start Stop Continue questions and prompts. The key here is to bake 2-3 prompts directly into the template so they're visible when participants start writing.
Tip: Rotate prompts every 3-4 sessions to prevent "prompt fatigue" where participants start ignoring them. Keep a prompt library in a separate document.
Step 4: Build in Prioritization and Voting Mechanisms
Collecting feedback is only half the job. Your template must include a built-in way to surface the most important items from what could be dozens of contributions.
In Miro, enable the voting plugin and add a voting zone where grouped items can receive dots. In Google Sheets, add a "Votes" column and instruct participants to place a number (or use conditional formatting to highlight high-vote items). In Notion, add a "Priority" select property with options like High, Medium, and Low, or use a number property for dot-voting.
Allocate a fixed number of votes per person—typically 3-5 dots total across all three categories. This forces participants to make tradeoffs and signals what genuinely matters versus what's mildly annoying.
Tip: Cap votes at 3 per person for teams under 8 people and 5 for larger groups. Too many votes dilutes the signal.
Step 5: Include an Action Items Section
The single most critical differentiator between templates that drive change and templates that get forgotten is a dedicated action items section. Place it prominently—either below the three columns or as a separate page/frame that participants can see during the convergence discussion.
Each action item should capture four fields:
- What: a specific, concrete action (not a theme)
- Who: the person responsible (singular owner, not "the team")
- By When: a deadline or next checkpoint date
- Status: Not Started / In Progress / Done
In Notion, this naturally becomes a linked database. In Google Sheets, it's a separate tab. In Miro, use a table frame. The point is that action items are structured data, not free-text notes buried in a paragraph.
Tip: Pre-fill the action items section with any unresolved items from the previous session. This creates accountability and continuity between retrospectives.
Step 6: Add Session Metadata and Instructions
A reusable template should be self-documenting. At the top, include fields for:
- Session date
- Sprint/period being reviewed
- Facilitator name
- Participants (list or count)
- Time allocated
Below the metadata, add a brief instruction block (3-5 sentences) explaining the process: how long participants have for individual brainstorming, how voting works, and what happens with the results. This is especially important for asynchronous templates where there's no facilitator to explain the rules in real time.
For Miro boards, place instructions in a "Start Here" frame with an arrow pointing to the first section. For Google Docs, use a highlighted callout box at the top. For Notion, use a toggle block that expands to show instructions.
Tip: Write instructions assuming someone is using the template for the first time. Your future self—or a new team member—will thank you.
Step 7: Test, Iterate, and Templatize
Run your template through at least one real session before declaring it "done." Pay attention to where participants get confused, where the flow breaks down, and whether the action items section actually gets used during the convergence phase.
After the session, ask two questions: "Was anything in the template confusing?" and "Was anything missing?" Common first-iteration fixes include adding more specific prompts, increasing the size of contribution areas (people always need more space than you think), and repositioning the action items section so it's visible during discussion without scrolling.
Once refined, save it as a proper template: in Miro, publish it to your team's template library; in Google Docs, save it to a shared drive template folder; in Notion, turn the page into a template within a database. Clear all session-specific content but keep the structure, prompts, and instructions intact.
Tip: Create a "template changelog" note that records what you modified after each session. Over 3-4 iterations, you'll converge on a design that fits your team perfectly.
Examples
Example: Miro Board for a Sprint Retrospective
A Scrum team of 8 engineers runs biweekly retrospectives. The Scrum Master wants a reusable Miro board that supports anonymous input, live clustering, and clear action tracking.
Create a Miro board with four frames arranged left to right: Instructions (rules, timing, vote allocation), Start (green frame with prompts like 'What engineering practice should we adopt next sprint?'), Stop (red frame with prompts like 'What process adds overhead without proportional value?'), and Continue (blue frame with prompts like 'What shipped well this sprint that we should keep doing?'). Lock all frames and labels. Enable the Miro voting plugin with 3 votes per person. Add a fifth frame called Action Items with a table: columns for Action, Owner, Due Date, and Status. At session start, set a 7-minute silent timer for individual sticky note creation, then facilitate grouping and voting. After voting, the top 3 items become action items filled out live. Duplicate the board as a template and clear sticky notes after each session while archiving the completed version to a 'Past Retros' folder.
Example: Google Docs Template for Async 1-on-1 Prep
A manager uses the Start Stop Continue framework in monthly 1-on-1s with each of their 5 direct reports. They need a lightweight template that both parties fill out before the meeting.
Create a Google Doc with a header section for date, employee name, and review period. Below, add three tables—one per category—each with two columns: 'Your Items' and 'Manager Items.' Add 2 prompts per category tailored to individual performance (e.g., Start: 'What skill or project would you like to take on?'; Stop: 'What's draining your energy without clear impact?'; Continue: 'What part of your current role do you find most fulfilling and effective?'). At the bottom, add an Action Items table with columns for Action, Owner, and Target Date. Share the doc 48 hours before the meeting with a note asking the report to fill in their column. During the 1-on-1, review both columns side by side and negotiate action items together. Save completed docs in a shared folder for reference in future reviews. This workflow connects naturally with using Start Stop Continue in performance reviews and 1-on-1 meetings.
Example: Notion Database for Quarterly Team Reflection
A product team of 12 people wants to run quarterly retrospectives where feedback accumulates over time and trends can be tracked across quarters.
In Notion, create a database called 'SSC Feedback' with these properties: Category (select: Start, Stop, Continue), Feedback Item (title), Submitted By (person), Quarter (select: Q1 2025, Q2 2025, etc.), Votes (number), Status (select: New, Discussed, Action Created, Resolved), and Related Action (relation to an Action Items database). Create a linked view filtered to the current quarter with three board views grouped by Category. Add a template button for each category that pre-fills the Category property and includes a prompt in the description field. During the quarterly retro, team members add items throughout the final week of the quarter. In the live session, the facilitator switches to a table view sorted by Votes descending and works through the top items. Resolved items from previous quarters remain in the database, allowing the team to filter by quarter and see how feedback themes evolve over time.
Best Practices
Use consistent color coding across all your templates (green = Start, red = Stop, blue = Continue) so participants build visual muscle memory and can orient themselves instantly in any session.
Design for the least engaged participant: keep instructions visible, prompts specific, and the contribution mechanism as low-friction as possible (e.g., one click to add a sticky note, not five).
Build anonymity options into your template design—Miro's anonymous voting, Google Forms for collection, or Notion's anonymous submission workaround—especially for teams where psychological safety is still developing.
Keep the template to one screen or one page wherever possible. If participants need to scroll or navigate between frames to see all three categories, they'll disproportionately contribute to whichever section is visible first.
Include a "parking lot" section for feedback that doesn't cleanly fit Start, Stop, or Continue. This prevents awkward debates about categorization and ensures no input gets lost.
Archive completed templates rather than overwriting them. A history of past retrospectives is invaluable for tracking whether action items actually led to change over time.
Common Mistakes
Creating a beautiful template with no action items section, treating the session as a venting exercise rather than a decision-making process.
Correction
Always include a structured action items section with fields for owner, deadline, and status. If your template doesn't produce commitments, it's a survey, not a retrospective tool.
Making the template too complex with dozens of fields, sub-categories, and rating scales that overwhelm participants before they write a single item.
Correction
Start minimal: three sections, 2-3 prompts each, a voting mechanism, and action items. Add complexity only after running 2-3 sessions and identifying specific gaps.
Using the same generic prompts for every session regardless of context, leading to stale, repetitive feedback after the third or fourth use.
Correction
Customize prompts to the specific sprint, project phase, or team challenge. Maintain a rotating prompt library and swap in fresh questions every few sessions. See the sibling skill on crafting actionable feedback prompts for guidance.
Building a synchronous-only Miro board for a distributed team across multiple time zones, resulting in low participation from anyone who can't attend the live session.
Correction
For distributed teams, design an asynchronous-first template (Google Form → Sheet, or Notion database) with a defined submission window, then use a shorter synchronous session only for discussion and prioritization.
Not locking the template structure in collaborative tools, allowing participants to accidentally move, resize, or delete frames and columns.
Correction
In Miro, lock all structural elements and only allow sticky note creation. In Google Docs, use protected ranges for headers and instructions. In Notion, use locked database properties.
Other 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.
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.
Frequently Asked Questions
What's the best tool for a start stop continue template?
There's no single best tool—it depends on your team's workflow. Miro and FigJam are best for synchronous visual sessions, Google Docs or Sheets work well for async or small-team use, and Notion excels when you want to track feedback across multiple sessions over time. Use whatever tool your team already opens daily.
Can I use a start stop continue template for individual self-reflection?
Absolutely. Simplify the template to a single-user format with three sections and an action items list. A Google Doc or Notion page works well for personal use. Add date fields and review your entries monthly to spot patterns in what you consistently want to start or stop.
How often should I update my start stop continue template?
Review your template after every 3-4 uses. Rotate prompts to prevent fatigue, adjust section sizes based on where participants write the most, and refine the action items structure based on whether commitments are actually being followed through.
Should the start stop continue template allow anonymous feedback?
For teams still building psychological safety, anonymous input significantly improves honesty—especially in the Stop category. Miro supports anonymous sticky notes, and you can use Google Forms feeding into a shared sheet. As trust grows, you can transition to attributed feedback.
How many prompts should I include in each section of the template?
Include 2-3 prompts per section. Fewer than two leaves participants staring at a blank space; more than four feels prescriptive and overwhelming. Choose prompts that are specific to your current project phase or team challenge rather than generic questions.
What's the difference between a start stop continue template and a retrospective template?
A start stop continue template is a specific type of retrospective template that uses the three-category framework from the Start Stop Continue method. Other retrospective formats include Mad Sad Glad, 4Ls, and Sailboat. The SSC format is popular because its categories map directly to concrete behavioral changes.