Unstick a Project with Stop / Start / Continue. When projects stall, more brainstorming adds noise. Stop/Start/Continue forces subtraction first.
The onboarding portal that stopped moving
A mid-size ops team had run the same onboarding portal project for eleven weeks. Demos happened. Slides updated. Nothing shipped. The project lead scheduled a Stop, Start, Continue review—not another brainstorm, a subtraction meeting.
Stop: weekly all-hands demo prep that consumed six hours across three people. Start: one thirty-minute customer interview block per week with notes in a single doc. Continue: the automated welcome email sequence that already worked. The insight was not new technology; it was calendar truth. Demos were theater; interviews were missing.
Within seven days, the interview block appeared on three calendars and demo prep came off the recurring invite. That is the bar for this review format: something actually leaves or enters the calendar, or you held a feelings meeting.
Eleven weeks earlier, the team had tried a “reset brainstorm” that produced seventeen new feature ideas and zero calendar changes. Stop, Start, Continue worked because it forced subtraction first. The portal shipped six weeks later—not because they worked harder, but because they stopped paying for demo theater and started buying customer signal.
Running Stop, Start, Continue with the actual team
Three columns on one page—Stop, Start, Continue. Silent write for five minutes: each person adds sticky notes or bullets without debate. Then read Stop first. Subtraction before addition prevents the review from becoming a wish list.
Rules that keep it honest:
- If Stop is empty, force one Stop before any Start is allowed.
- Limit Starts to one or two. More than two means redesign everything and finish nothing.
- Continue needs a plain definition of done, not nostalgia for busywork.
Facilitator job: translate vague Stop items into calendar edits. “Less process” becomes “remove Tuesday status readout.” “More focus” becomes “protect Tuesday 9–11 for build.” Vague columns recreate the stuck project in a new font.
Invite only people who can change the calendar—not observers who will nod and leave without authority. If a Stop requires executive approval, put “request cancel of exec staff meeting readout” on the Start column with the requester named. Honesty about authority prevents fake Stops that everyone applauds and nobody executes.
What changed on the calendar within a week
Starts get time blocks within seven days—not “next sprint,” seven days. Stops remove recurring load from the calendar or report list: cancel the invite, archive the dashboard nobody opens, end the duplicate Slack channel. Continues stay only if they still connect to the outcome statement on the project note.
Publish the three columns the same day so the team can object while context is warm. Celebrate Continue explicitly so people do not hear the review as only criticism. Morale is part of execution, not a separate program you schedule later.
Revisit in two weeks. Strike Starts that never began—either they were not real or the blocker was mislabeled. Returning Stop items mean the Stop was never real; assign the person who controls the invite or the automated report, not the person who complained loudest.
When the review fails and how to recover
The review fails when Continue is ninety percent of the board. That signals fear of subtraction. Run a forced Stop round: each person must remove one recurring obligation or report line. The review fails when Starts are all verbs without owners. Every Start needs a name and a calendar block, not “team.”
Recovery is smaller, not longer. Schedule a thirty-minute follow-up with only Stop and Start columns—drop Continue. Ship one calendar change before talking about vision again. Stuck projects often need less brainstorming and more subtraction. Stop, Start, Continue is a knife; use it like one.
Another failure mode: the review happens once and never again. Attach the next review date to the project note when you publish columns. Without a return date, the format becomes a one-time vent session that politely preserves the mess.
Success signal: the project note’s outcome statement gets shorter because scope matches reality. Failure signal: the Continue column grows every review while shipping dates slide. If Continue grows twice in a row, run a forced Stop round before any new Starts are allowed—same rule as the first meeting, still non-negotiable.
A second case: the report nobody reads
A customer success team maintained a forty-page weekly metrics deck. Stop, Start, Continue surfaced the truth: managers skimmed two charts; nobody read narrative slides. Stop: narrative sections and duplicate charts. Start: one-page exception list with owner names. Continue: the two charts that actually triggered conversations.
Within a week, deck prep dropped from six hours to ninety minutes. CS reps got Friday afternoons back for customer calls—the work the deck was supposed to support. Continue items still mattered; they were the only metrics tied to decisions. Everything else was vanity weight.
This case shows the format works beyond software projects. Any recurring artifact—reports, standups, email digests—can be reviewed with the same three columns. Ask: what calendar or artifact would change if we were serious?
Facilitators should timebox the review itself: forty-five minutes maximum. Longer reviews drift into storytelling. Silent write, read Stop, negotiate Starts, assign calendar edits, publish—done. Respect the knife metaphor: quick cuts, not slow sawing.
Remote teams can use a shared doc with three columns instead of a wall. Same rules: silent write, Stop first, calendar edits before celebrating Continue. Publish a screenshot in the project channel so absent stakeholders see what changed—not what was discussed.
Pick one stuck project today
Choose a project that has consumed meetings without shipping. Fill Stop, Start, Continue on one page, publish it, and put every Start on the calendar before you log off. If nothing on the calendar changes, run the review again with subtraction only. General productivity guidance for everyday teams—not executive coaching or a promise of project outcomes.