Crafting Actionable Start Stop Continue Questions and Prompts

Overview

How It Works

Step-by-Step

1. Step 1: Define the Feedback Scope and Context

   Before writing a single question, define precisely what you're gathering feedback on. Is it a two-week sprint? A quarterly project? A team's meeting culture? A manager's leadership style? Write a one-sentence scope statement: "We're gathering feedback on [specific subject] during [specific timeframe]."

   This scope statement becomes the anchor for every prompt you write. Without it, your questions will drift toward generality, and your participants will answer different implicit questions—one person thinking about last week, another about the entire quarter.

   For team retrospectives, the scope is usually the most recent sprint or iteration. For performance reviews, it might be a quarter or a specific initiative. For personal development using Start Stop Continue, define the life domain (career growth, health habits, relationship patterns).

   Tip: Write your scope statement at the top of your question draft document and reference it before finalizing each prompt. If a question doesn't clearly relate to the scope, rewrite or cut it.

2. Step 2: Identify 2-3 Focus Areas Within Your Scope

   Within your defined scope, identify the specific domains where feedback will be most valuable. These might be communication practices, technical workflows, decision-making processes, meeting formats, or collaboration patterns.

   Choose focus areas based on where you've noticed friction, where recent changes have been made, or where the team has expressed uncertainty. You don't need to cover everything—targeted feedback on two or three areas produces better outcomes than shallow feedback on ten.

   For example, if your scope is "Sprint 14 of the checkout redesign project," your focus areas might be: (1) code review turnaround time, (2) cross-functional handoffs between design and engineering, and (3) standup meeting effectiveness.

   Tip: If you're unsure which focus areas matter most, run a quick async poll asking the team: "What topic would be most valuable to discuss in our retro?" This also increases buy-in for the session itself.

3. Step 3: Draft Start Questions That Surface Opportunities

   Start questions should unlock new possibilities. The best Start prompts reference a known gap, an aspiration, or an unmet need—and ask respondents to propose a specific new behavior or practice to address it.

   Use this formula: "What's one [new practice/behavior/tool] we could start doing to improve [specific focus area]?"

   Examples for a sprint retrospective:

   • "What's one practice we could start in code reviews to reduce the back-and-forth cycle?"
   • "Name a communication habit we could adopt to make cross-team handoffs smoother."
   • "What's something another team does well that we should start trying?"

   Notice how each question names the domain (code reviews, handoffs), implies a problem worth solving, and asks for a concrete practice rather than an abstract idea. Avoid Start questions that are so open-ended they invite wish lists ("What should we start?") or so narrow they have only one answer.

   Tip: Add the phrase "one thing" or "one practice" to force respondents to prioritize rather than listing everything they can think of. Prioritized feedback is inherently more actionable.

4. Step 4: Draft Stop Questions That Depersonalize Problems

   Stop questions are the most psychologically loaded category. Asking "What should we stop doing?" can feel like an invitation to complain or blame. The key is to focus on practices, processes, and habits—never on individuals.

   Use this formula: "What's one [process/practice/habit] that's not serving us well in [specific focus area] that we should stop or change?"

   Examples:

   • "What's one meeting ritual that's taking more time than the value it adds?"
   • "Which recurring task in our deployment process feels unnecessary or redundant?"
   • "What's a communication pattern in our async channels that creates more noise than clarity?"

   The word "serving" is powerful in Stop prompts because it frames the practice as something that once had value but may have outlived its usefulness. This reduces defensiveness—especially when someone on the team originally introduced the practice being questioned.

   Always depersonalize: "What process should we stop?" is safer than "What is someone doing that they should stop?"

   Tip: If your team is new to retrospectives or has low psychological safety, soften Stop questions further: "What's one thing we could do less of?" or "What could we experiment with removing for one sprint?"

5. Step 5: Draft Continue Questions That Reinforce Specific Wins

   Continue questions are often treated as the easy category, but vague Continue prompts produce vague answers ("Keep up the good work!") that don't help anyone. The best Continue questions reference a specific recent positive behavior or outcome and ask whether it should be sustained.

   Use this formula: "What's one thing we did well in [specific focus area] during [timeframe] that we should make sure to keep doing?"

   Examples:

   • "Which aspect of our pair programming sessions this sprint was most valuable and should continue?"
   • "What's one thing about how we handled the production incident last week that we should replicate?"
   • "Name a collaboration practice between design and engineering that's working well right now."

   The power of Continue prompts is that they surface tacit knowledge—practices the team is doing well but hasn't consciously recognized. When someone names a specific positive behavior, it becomes visible and repeatable rather than accidental.

   Tip: Reference a specific event or achievement in your Continue questions. "What worked well about how we handled X?" outperforms "What's going well?" every time because it grounds the answer in shared experience.

6. Step 6: Apply the Specificity Test to Each Question

   Before finalizing your questions, run each one through the specificity test. Read the question and imagine the most generic possible answer someone could give. If a one-word or cliché answer would technically satisfy the question, it's not specific enough.

   For example, "What should we start doing?" could be answered with "Communicate better." That answer is useless. But "What's one new practice we could adopt to reduce miscommunication during sprint planning?" can't be answered with a cliché—it demands a concrete suggestion.

   For each question that fails the test, add one or more of these constraint levers:

   • Temporal anchor: reference a specific sprint, week, or quarter
   • Domain scope: name the specific workflow, meeting, or process
   • Quantity limit: ask for "one thing" instead of open-ended lists
   • Behavioral framing: ask for a practice, habit, or action rather than a quality or feeling

   Tip: Have a colleague read your questions and attempt to answer each one in under 30 seconds. If they struggle to think of a specific answer, the question needs more constraint. If they immediately answer with something actionable, the question is ready.

7. Step 7: Sequence and Balance Your Final Question Set

   Arrange your final prompts in an intentional order. Research on feedback psychology suggests starting with Continue questions (positive reinforcement), then moving to Stop questions (problem identification), and ending with Start questions (forward-looking solutions). This sequence builds psychological safety before asking people to name problems, and ends on an energizing note.

   Balance the number of questions across categories. A typical session uses 2-3 questions per category, for 6-9 total prompts. More than that leads to survey fatigue and shallow answers. If you have multiple focus areas, you might have one question per category per focus area.

   Finally, review the full set for tone consistency. All questions should feel equally weighted—avoid making your Stop questions dramatically more pointed than your Continue questions, as this signals that the session is really about airing grievances.

   Tip: For recurring retrospectives, rotate your focus areas each session rather than asking the same questions every time. Keep a question bank organized by focus area so you can quickly assemble a fresh set.

Examples

Best Practices

• Always anchor questions to a specific timeframe and domain—"during our last sprint" or "in our design review process"—to prevent respondents from answering about different contexts.

• Limit each prompt to asking for one item ("Name one practice...") rather than open-ended lists, which forces prioritization and produces more actionable feedback.

• Use behavioral language (practices, habits, actions, processes) rather than abstract language (culture, vibe, morale) to ensure responses describe something the team can actually change.

• Rotate your question focus areas between sessions so teams don't experience prompt fatigue and so you systematically cover different aspects of team performance over time.

• Test your questions with one trusted teammate before the session to verify they're clear, specific enough, and don't accidentally lead toward a predetermined answer.

• Include at least one Continue question that references a specific recent achievement—this grounds the positive feedback in reality rather than generic encouragement.

Common Mistakes

Frequently Asked Questions