6 Myths About Start-Stop-Continue Reviews, Tested One by One

6 Myths About Start-Stop-Continue Reviews, Tested One by One

Few planning habits are as widely praised and as poorly understood as the small-business retrospective. After a product launch, a seasonal promotion or a quarter of client work, someone suggests sorting events into what to start, what to stop and what to continue. The idea is simple, so people assume they already know how it works. Often they do not. This article tests six common beliefs about start-stop-continue reviews against how the method actually behaves in a working team, quoting no statistics that cannot be traced.

Myth 1: a retrospective is only for software teams

The format became popular in software, but nothing about it is technical. It needs a stretch of work with a visible beginning and end, a few people who lived through it, and a page divided into three columns. A shop that has just finished a holiday rush qualifies. So does a freelancer wrapping up a client project, or a two-person agency that has just migrated its invoicing.

The evidence for portability is in the structure itself. Each column asks a question anyone can answer from direct experience: what should we add, what should we drop, what should we keep. None of those questions requires specialist vocabulary.

Another sign that the format travels well is how easily it adapts to scale. A solo operator can run it as a private notebook page, while a larger group can run it across several sub-teams and merge the results afterwards. The three questions stay the same; only the number of voices changes.

Myth 2: you need a long meeting and a facilitator

Small teams routinely believe a review means booking a room for half a day. The opposite tends to hold. A short session with a hard time limit tends to produce sharper entries, because participants have no room to wander into storytelling. A quarter of an hour up to half an hour covers most small projects, and a written version collected beforehand can replace the meeting altogether when people are in different time zones.

If someone needs to guide the conversation, it does not have to be an outsider. Rotating the role keeps the ritual light and spreads ownership of the follow-up.

It is also worth remembering that a shorter session is easier to repeat. A review that feels like a burden gets skipped after the second round, and a skipped review teaches nothing. Consistency beats depth here, so design the ritual to be small enough that nobody dreads it.

Myth 3: the Stop column is for blaming people

This myth does the most damage because it makes participants defensive. A well-run Stop column lists practices, not people. “Approving work in chat threads with no summary” is a practice. “Someone keeps forgetting to summarise” is an accusation dressed up as an entry. The first can be fixed by changing a routine; the second can only be resented.

Try handing an entry to someone who joined last week; if it is unclear to them, it is probably unclear to everyone. If it only makes sense with a name attached, rewrite it until the subject is the process.

Myth 4: positive findings are a waste of space

The Continue column is often rushed or skipped because it feels like congratulation. Yet it performs a protective function. Teams that only record problems tend to overhaul everything after a rough stretch, including the habits that were quietly carrying them. Naming a working routine on paper makes it harder to discard by accident during the next round of changes.

Consider how this plays out with money. A guide such as this article about hunting down spending leaks and stretching runway makes a point many owners miss: the monthly check that catches leaks is itself the thing to continue, even in months when it finds nothing.

That distinction between practices and people also changes the quality of the Start column. Entries such as “write a one-paragraph summary after every client call” are concrete and checkable, whereas “communicate better” is a wish. The same standard should apply to all three lists.

Myth 5: more entries mean a better review

It is natural to assume thoroughness equals quality, but the data from lived experience points the other way. A page with twenty items per column rarely produces twenty changes. It produces a document nobody reopens. Limiting each column to three entries forces a ranking conversation, and that conversation is where the real learning sits, because the team has to explain why one change matters more than another.

A practical rule is to collect freely, then vote or discuss until only three per list remain. Park the rest in a “later” note. If an item keeps resurfacing across several reviews, promote it; persistence is a better filter than enthusiasm in the moment.

Myth 6: once the lists are written, the work is done

The page is not the outcome. The outcome is a changed routine. Many teams write thoughtful lists and then watch them gather dust, because nobody owns the first step. Attach each entry to a concrete action, a person responsible for it and a date for checking whether it happened. Then, at the next review, begin by reading last time’s lists and marking each entry done, dropped or still open.

This follow-through is also where the method connects with broader planning. If your business is preparing a larger programme of work, a roadmap like the one in this write-up on staging a digital growth plan in phases becomes more realistic when each phase ends with a short review that feeds the next one.

One more point on ownership: when several people share the follow-up, it is worth writing the owner’s role next to each entry rather than leaving it implied. “Whoever handles invoicing” is clear enough in a small business, and it holds up through holidays and staff changes far better than a casual “I’ll look into it”.

Why these beliefs persist

All six beliefs treat the retrospective as a ceremony rather than a tool. Ceremonies need the right setting, the right people and the right tone. Tools only need to be used. When you drop the ceremony, three things remain: a bounded stretch of work, an honest conversation about it, and a short list of changes with owners.

A note on gathering ideas from outside your field

It helps to look at how people in other fields organise their learning and their communities. One example is an aviation discovery website with a forum and a blog among its sections. Browsing a site like that shows how a topic gets split into areas that each serve a different question, which is much the same instinct behind sorting a review into three columns. Treat it as inspiration for structure, nothing more.

Running your first review without the myths

Pick a recent piece of work that finished cleanly. Give the team a week’s notice so entries can be thought through instead of improvised. At the session, spend five minutes on Start, five on Stop and five on Continue, then ten on choosing three from each and naming an owner for every choice. Write the result in a place the team already looks every day, not in a document that lives in a forgotten folder.

Finally, schedule the next review before you leave the room. A habit that is easy to postpone is a habit that will be postponed, whereas a date in everyone’s calendar turns the retrospective into part of how the work gets done. Give it a few rounds and your own team’s results will say more than any broad assertion, the ones above included.