Change without the growing pains

I’ve never met an owner who was afraid of technology. I’ve met plenty who were afraid of the mess — the two weeks of chaos, the crew grumbling, the customer who falls through the cracks while everybody learns the new thing. That fear is fair. It’s also avoidable, and I want to walk you through how.

Why change management for small business gets a bad name

Most change hurts because of how it’s done, not what’s being done. John Kotter at Harvard spent ten years studying more than a hundred companies trying to transform themselves, and his famous finding is that roughly 70% of those efforts fail. When you read why, a pattern jumps out: they tried to change everything at once, and folks never saw a reason to believe in it.

So we don’t do that. Ever.

One process. The one that hurts most.

We change one thing at a time, and we start with the thing that’s already causing pain. That matters for a simple, human reason: when the first change makes life noticeably better, nobody needs convincing about the second one. The relief does the selling.

The old way keeps running

Here’s the part that puts owners at ease. When we bring in a new system — say, automatic payment matching — the old way doesn’t get ripped out on day one. Both run side by side. You watch the new system do the job, you check its work as long as you like, and the old spreadsheet sits right where it always was. The cutover happens when you stop reaching for the old way — not when a consultant declares victory.

And if something’s not right? We roll it back. A good system is built so going backward is easy. You are never standing on a ledge.

Small bites, steady gains

A week or two per change. A clear before-and-after. The crew’s feedback actually acted on. Then, and only then, the next one. It feels almost too modest — until you look back after a few months and realize the schedule builds itself, the books balance themselves, and nobody remembers exactly when the stress left the building.

That’s change without the growing pains. It’s not magic. It’s just respect — for the business you’ve built and the people who run it with you. I’ve got two more short pieces on this: one about bringing your team along, and one just for you, the owner — you don’t have to become a computer person.