A few weeks ago I sat down for an interview. A CEO, hiring for an end-to-end operations leadership role, asked me a question that’s been sitting with me since.

He wanted to know how I’d stop his last improvement push from doing what the one before it did. And the one before that. Every initiative his business had tried, he said, faded out at almost exactly the same point: around six months after launch.

Not because the ideas were bad. Because nobody cared at the start. They just quietly stopped happening, the way a New Year’s resolution stops happening. One day nobody’s doing the new thing, and nobody remembers deciding to stop.

If that sounds familiar, you’re not doing anything wrong. You’re running into a pattern that shows up almost everywhere, in businesses of every size. I saw it inside major operations over 34 years, and I see it in small businesses now. The scale changes. The reason it dies doesn’t.

Reason 1: Too much rigor, not enough Monday morning

The first improvement push usually starts strong. Someone gets excited, brings in a framework, builds a plan with phases, milestones, and a name.

That’s also where it starts to die.

A framework built for a 500-person operation asks too much of a team that’s also answering the phones and shipping the orders. The forms take longer than the actual fix. The meetings multiply. Within a few weeks, keeping up with the new process becomes its own full-time job, on top of the one everyone already has.

People don’t abandon it because they stopped caring. They abandon it because it stopped fitting into an actual Monday morning.

Reason 2: No visibility, so no one notices it slipping

Here’s the quieter reason, and it’s the one most owners miss.

If nobody can see whether the new process is happening, nobody knows when it stops happening. A change lives in someone’s head, or in a document nobody opens again. There’s no simple way to check. Is this still how we do it, or did we drift back to the old way three weeks ago?

Compare that to something visible. A whiteboard. A shared checklist. A single number that goes up or down depending on whether the fix is holding. When there’s nothing to look at, slippage stays hidden until the old problem shows back up and everyone acts surprised.

Reason 3: Ownership dies with the person who introduced it

This is the one that ends most improvement pushes for good.

Someone champions the change. They’re enthusiastic, they chase people down, they keep it alive through sheer will. Then they get pulled onto something else, or they leave, or they just get tired of being the only one pushing it.

And the process goes with them, because it was never actually built into how the business runs. It was built into how hard one person was willing to work to keep it going.

A fix that depends on one person’s energy isn’t a fixed process. It’s a favour that person’s doing you, for as long as they’ve got the energy to keep doing it.

How this actually plays out

Here’s what it usually looks like in a business your size, start to finish.

Picture a 15-person service business. Jobs keep slipping. A client expects someone on-site Tuesday, and Tuesday comes and goes with nobody there. The owner’s had enough, and this is the year it gets fixed properly.

Week one, reason one shows up. The owner finds a scheduling methodology online, the kind built for operations with a dedicated planning department. It comes with a 12-step SOP and a colour-coded priority matrix. Before any job gets booked, there’s a form to fill in. The kickoff meeting goes well. Everyone nods.

By week three, the form takes longer to fill in than the job takes to book. The office manager already answers the phones and chases invoices. She starts booking jobs the old way, filling in the form afterward when she remembers. Nobody told her to. It’s just what fit into her Tuesday.

Month two, reason two shows up. Nobody’s tracking whether the new process is actually running. There’s no shared list, no single place to check. The owner assumes it’s working because nobody’s complained. The office manager assumes it’s fine because the jobs are still going out, mostly. Neither one can actually answer the question: is this happening the way we said it would?

Month five, reason three finishes it off. The owner, who pushed the whole thing through on personal energy, gets buried in a big contract and stops checking in. Nobody else ever owned it. Within a few weeks, the old habits are back in full, and the double-bookings start again, right on schedule for month six.

Here’s the same business doing it differently. Instead of the 12-step methodology, the owner picks one change. Every job gets logged on a single shared calendar the moment it’s booked, no exceptions, no form. That’s small enough to survive week one.

To make it visible, the calendar itself becomes the check. Anyone can look at it and see whether a job went in the right place. No separate audit needed. The evidence is sitting right there.

And ownership gets handed off on purpose. Before moving on to the next thing, the owner tells the office manager out loud, in a two-minute conversation. The calendar is hers to own now, not left for her to assume by default.

Six months later, it’s still how the business books a job. Someone specific owns it, everyone can see it, and it never asked more of week one than week one could give.

What to build instead

None of this means process improvement doesn’t work for a business your size. It means most of what gets tried wasn’t built to survive contact with a small team’s actual week.

Three things change that:

Keep it small enough to survive week one. One process, one change, tested for a short stretch before you add anything else. Call it a fix, not a program.

Make it visible to more than one person. If you can’t see whether the team is following a process, you can’t tell whether it’s working, and neither can anyone else. Visibility is what turns “I think we’re doing it” into “yes, we’re doing it.”

Hand off ownership on purpose. Before you call anything finished, name who owns it when you’re not watching. If the honest answer is “me,” it hasn’t actually landed yet.

That third one matters most for recurring problems. A fix that only holds while the owner is checking on it isn’t a fix. It’s a delay.

Common questions

Does this apply if my business is smaller than 15 people?

Yes, if anything, it gets simpler. The three reasons don’t care about headcount. A five-person team just needs a lighter version of the same fix: one visible change, with one named person keeping an eye on it. The framework problem actually hits smaller teams harder, since there’s nobody spare to carry the extra admin.

How long should I test a change before I know if it’s working?

Long enough to hit a genuinely bad week, not just a calm one. A few weeks usually does it. You’re not looking for perfection. You’re checking whether the change survives contact with the kind of week where everything’s on fire and it would be easiest to skip it.

What if it’s just me? I don’t have anyone to hand ownership to.

Then you own it, on purpose, out loud. Write it down somewhere you’ll actually see it again: “I own this, I check it every Friday.” That single sentence is the difference between a habit and a good intention. Solo owners fall into reason three just as often as teams do; they just call it “I got busy” instead of “the champion left.”

Do I need software or a system to make this work?

No. A whiteboard or a shared spreadsheet works fine, as long as more than one person can see it. Plain and visible beats fancy and hidden every time. Software can help later, but it’s not what makes a fix stick.

What if the team pushes back on a new process?

Most pushback isn’t really about the idea. It’s about the extra hour it adds to an already full day. Keep the change small enough that it doesn’t ask more of anyone’s week. Then let people see it working with their own eyes, instead of just hearing about it. Trust builds from what’s visible, not from what’s announced in a meeting.

Find out where yours would break first

You don’t need to guess which of these three is going to trip up your next fix. Most businesses have a pattern, and it usually shows up before you’ve even started.

The free Bottleneck Finder Assessment takes about three minutes. It shows you exactly where your business is losing time and money, right on screen, no waiting for a report.

Know where the leak is before you build anything to fix it. It’s the difference between a change that sticks and one you’ll be re-explaining to your team again in six months.

Richard Darby is the founder of Better Flow Systems. After 34 years of operational improvement work inside major organisations including GE, British Airways, and Nielsen, he now helps small business owners find bottlenecks, cut wasted time, and fix broken processes with simple, practical tools.