“Stop, Start, Continue” has run team retrospectives for a decade. Keep what works, drop what doesn’t, try something new. It’s simple, it’s participative, and it’s had a good run in sprint reviews, quarterly check-ins, and performance conversations across our industry - including our own.
However, it was built for a world where the only lever a team had was human effort. It never asks the question that matters most today: which of these tasks shouldn’t need a person at all?
That’s the gap a fourth category closes. Stop, Start, Continue, Automate (SSCA) keeps the format everyone already knows, and adds the one question our industry can no longer afford to skip.
The Fourth Question
Stop, Start, Continue is a behaviour audit. It asks what a team should do differently. Automate is something else entirely - it’s a delegation audit. It asks which tasks are consuming time and attention without requiring judgement, and hands those to a tool instead.
Stop and Automate can look alike on paper - both remove work from someone’s plate. But they mean different things, and the difference matters more than it looks. Stop says the work has no value; walk away from it. Automate says the outcome still matters, but the manual labour behind it doesn’t need a person doing it. Confuse the two, and a team either keeps grinding through low-value work it should have automated months ago, or automates away the judgement calls - the client conversation, the design trade-off, the mentoring moment - that only a person could make well.
Getting that distinction right is, in our view, the single biggest reason this framework earns its place alongside the original three questions rather than replacing them.
If we’re telling clients to automate the inefficiency out of their operations, the same discipline should apply inside our own walls.
Why It’s Different Here
Our business is built on finding waste and automating it away - that’s what OneView does for enterprise IT spend, every day, for clients who trust us to see what they can’t. A software company selling that story owes it to its clients, and to its own people, to live it internally rather than just prescribe it externally.
It’s also no longer optional. AI-assisted development and intelligent tooling have moved from differentiator to baseline expectation - for the clients hiring us, and for the engineers and consultants choosing where to build their careers. People want to spend their time solving real problems, not doing by hand what an assistant could do faster and more reliably. Automate, done well, is as much a retention lever as it is an efficiency one.
This is where HR has a genuine stake in the conversation. Automation and AI adoption are usually driven bottom-up by the teams or top-down by leadership, with HR responding to the people impact after the fact - managing anxiety, redesigning roles, explaining decisions that were made. SSCA
changes that sequence. It gives HR a structured way to be present at the point where automation decisions are made.
Bringing It to Life
The diagram below is one way we’ve found useful for framing the four questions as a single, memorable exercise - something a team can genuinely run in twenty minutes, not a slide that gets shown once and forgotten.
Making It Work
Automate means removing tasks, not people.
- Sequence it deliberately. Continue first, to build confidence. Stop next, to surface friction. Automate follows - of everything just raised, what’s repetitive enough for a tool to handle? Start comes last, once the team has a clearer, freed-up sense of where its energy should go.
- Give every item an owner and a date. An automation idea with no owner is just a wish. A named owner and a timeframe - this quarter - is what turns the list into a plan.
- Show the payoff, visibly. When a team frees up capacity, put it back into work people can see and feel - upskilling, a more ambitious project, simply less overload. Silence after the exercise is what kills honest participation the second time round.
- Close the loop next time. Open the following session by reviewing what got automated, stopped, started, and kept since the last one. That’s what turns a one-off exercise into an operating rhythm.
Our People, Our Growth Mindset
The reason we’re bringing SSCA into our teams is the same reason we invest in our people’s growth in the first place: we believe capability compounds when people are given room to build it, and that room has to come from somewhere. Automating the repetitive is one of the most honest ways we know to create that room.
That means treating this as a growth conversation, not a productivity audit. When a team automates its way out of an hour of admin a week, that hour belongs to the person who used to spend it - for learning a new skill, taking on a project, or simply working at a more sustainable pace. A growth mindset isn’t a slogan on a wall; it shows up in whether freed-up time actually gets reinvested in people, or quietly disappears into someone else’s workload.
The Takeaway
Stop, Start, Continue made sense when human behaviour was the only variable in team performance. It isn’t anymore. Automate isn’t a trend bolted onto an old framework - it’s the recognition that a company built on eliminating waste for its clients owes itself, and its people, the same discipline.
It’s a small change to a familiar format. The value comes from asking it every time - and from making sure the time it frees up goes back to the people who earned it.