Project & Team Retrospectives Built-in template: Stop, Start, Continue

Team Retrospective Questions (Stop, Start, Continue Format)

Running async team retrospective questions before a live retro meeting prevents groupthink—so the loudest voice in the first five minutes doesn’t set the entire agenda. Evaluation Guru maps team retrospectives to our built-in 3-question Stop, Start, Continue template, collecting anonymous written answers (with minimum-3 suppression) or 3-minute video reflections into a three-column report.

Setup time
Under 2 minutes
Response mode
Written or 3-min video
Anonymity rule
Min 3 responses
Respondent login
Never required

When to use this template

When to use asynchronous team retrospective questions

Collect individual Stop, Start, Continue answers 24 hours before your live retrospective so everyone reflects independently first.

1

Post-launch or end-of-quarter project retrospectives

Gather honest input from engineers, designers, product managers, and stakeholders after a major release before memories fade.

2

Consulting & agency client delivery retros

Invite both internal delivery team members and client counterparts to share what to stop, start, and continue before the next phase kicks off.

3

Leadership team offsites facilitated by a coach

Have every executive submit anonymous Stop, Start, Continue responses ahead of a quarterly offsite so the facilitator walks in with real themes.

Recommended campaign setup

Who the feedback is about
Team lead, project lead, fractional executive, or the team’s shared operating rhythm
Who to invite
4 to 15 team members and cross-functional contributors
Rater count & anonymity
4 to 15 team members (minimum 3 completed responses required for anonymous mode)
Recommended cadence
End of sprint/quarter, post-launch, or ahead of a team offsite

Sample Questions (10 included)

10 team retrospective questions (Stop, Start, Continue)

Evaluation Guru runs this workflow on the built-in 3-question Stop, Start, Continue template. The retrospective questions below are prompts to guide your respondents—facilitators can add context or paste 3–4 of these specific prompts into the campaign description and personal note to focus the team on a recent project or quarter.

  1. 1Stop · Process drag

    “What recurring meeting, handoff step, or approval ritual should we STOP doing because it adds delay without improving quality?”

    Why it works: Targets concrete workflow waste rather than interpersonal blame.

  2. 2Stop · Focus & scope creep

    “Where should we STOP context-switching or pulling unplanned work into the middle of a cycle?”

    Why it works: Surfaces hidden interruptions that derail delivery.

  3. 3Stop · Handoff blind spots

    “What communication assumption should we STOP making between engineering, product, and client-facing roles?”

    Why it works: Helps cross-functional teams pinpoint where expectations silently diverge.

  4. 4Start · Early risk discovery

    “What is one practice we should START doing in the first 48 hours of a project to surface risks earlier?”

    Why it works: Produces a specific pre-mortem or kickoff habit the team can adopt immediately.

  5. 5Start · Async clarity

    “How should we START documenting or sharing decisions so people who weren’t in the room can move fast?”

    Why it works: Essential for remote and hybrid teams where tribal knowledge slows people down.

  6. 6Start · Tighter feedback loops

    “What check-in or demo habit should we START running to get stakeholder feedback before work is 90% done?”

    Why it works: Prevents late-stage rework and scope surprises.

  7. 7Start · Leadership clarity

    “What should leadership START doing to make trade-offs and top priorities clearer when timelines slip?”

    Why it works: Gives the team a constructive channel to ask for clearer prioritization.

  8. 8Continue · Winning habits

    “What collaboration habit worked really well this cycle that we should CONTINUE doing every time?”

    Why it works: Ensures the team codifies what went right instead of only cataloging problems.

  9. 9Continue · Team culture

    “How did teammates support each other during crunch moments that we should CONTINUE recognizing and repeating?”

    Why it works: Builds morale by surfacing quiet acts of teamwork.

  10. 10Continue · Operating rhythm

    “Which part of our planning or delivery rhythm gave you the most clarity and momentum—and why should we CONTINUE it?”

    Why it works: Protects the rituals that actually help the team ship.

Practical Facilitation Guide

Tips for running high-signal team retrospectives

How you frame the invitation, protect respondent anonymity, and follow up before the deadline matters just as much as the questions you ask.

Minimum-3 anonymity protection

When Anonymous Feedback is enabled, Evaluation Guru enforces a minimum of 3 completed responses before unlocking the report, hides individual completion statuses, and shuffles written answers.

1. Use minimum-3 anonymity so quieter teammates speak up

In a live room, junior teammates rarely contradict a vocal senior lead. Collecting anonymous written responses in Evaluation Guru first—protected by our minimum-3 response suppression and shuffled quote order—puts every perspective on equal footing.

2. Close the form 2 hours before the live meeting

Set your deadline and send a quick one-click reminder the day before. Reviewing the report for 10 minutes before the call lets you pin the top 2–3 quotes in each column.

3. Keep written mode for anonymous retros, or use video for named leadership retros

For anonymous team retros, written mode keeps everyone unidentifiable. For named leadership offsites where directors want to share fuller context, enabling 3-minute browser video works great.

4. Leave the meeting with at most two "Start" commitments

A retrospective that produces 12 action items produces zero change. Use the deterministic recurring themes in the Evaluation Guru report to pick one habit to stop and one habit to start.

2-Minute Setup

How to run an async team retrospective in Evaluation Guru

Set up your pre-retro pulse in 2 minutes and review the three-column report live with your team.

  1. 1

    Create the campaign with the Stop, Start, Continue template

    Name the project or team lead as the subject, select the built-in Stop, Start, Continue template, and add your retro focus in the description.

  2. 2

    Turn on Anonymous Feedback for psychological safety

    Enable Anonymous Feedback so team members can name tough process or leadership bottlenecks honestly—knowing results only unlock once 3+ teammates submit.

  3. 3

    Send unique links 48 hours before the retro meeting

    Paste your team’s email addresses to send one-click links, or copy each person’s unique invitation link to share directly.

  4. 4

    Walk through the Stop, Start, Continue report together

    Open the three-column Stop, Start, Continue report view (with deterministic recurring themes and pinned quotes) or share the report link to drive your live retro discussion.

FAQ

Frequently asked questions

How does Evaluation Guru display Stop, Start, Continue retrospective results?

The report organizes responses into three dedicated columns—Stop, Start, and Continue—showing response counts, deterministic recurring themes, and individual quotes that the organizer can pin to the top.

What is the minimum rater count for an anonymous team retrospective?

At least 3 completed responses are required. Evaluation Guru’s minimum-3 anonymity rule suppresses all answers until 3 team members finish the form.

Do team members need an Evaluation Guru login to submit retro feedback?

No. Every invited teammate gets a unique one-time invitation link that opens directly in their browser with zero sign-up required.

Which built-in template does this page map to?

It maps to Evaluation Guru’s built-in 3-question Stop, Start, Continue template.

Ready to send this feedback round?

Set up Stop, Start, Continue in under 2 minutes. Invite respondents with one-click links, collect written or 3-minute video answers, and share a clean report.