The Case for Automation: Why “We've Always Done It This Way” Is Costing You Growth

Every business has a process that survives not because it is good, but because it is familiar. Someone built it years ago, it mostly works, and nobody has had a strong enough reason to change it—until it quietly starts holding the business back.

“We've always done it this way” can become one of the most expensive sentences a growing business says to itself.

Why process inertia happens—and why it is not a character flaw

It is tempting to label resistance as stubbornness, but several reasonable forces usually sit behind it.

The current process is a known quantity

Even a flawed process is predictable. Everyone knows its quirks, workarounds, and failure modes. A new process, however promising, creates genuine uncertainty about what might go wrong.

The cost of staying is invisible; the cost of changing is visible

Nobody receives an invoice for hours lost to a clumsy manual process. A change project, however, has obvious upfront costs in time, money, and disruption. Comparing a visible cost with an invisible one makes the status quo look artificially cheap.

The person who built it may feel ownership

Changing a process someone created and maintained for years can feel like criticism of their work, even when that is not the intention. Avoiding that discomfort is a human reason to let a process remain longer than it should.

Nobody has permission to question it

Longstanding processes often gain protected status without anyone deciding they are sacred. They remain because nobody's role explicitly includes challenging how the business has always worked.

The real cost of staying the same as the business scales

“It has always worked” is often true until the moment it is not. Processes that function at one size can fail quietly or dramatically after volume, headcount, or complexity crosses a threshold.

• A process owned by one person breaks when a second person joins because knowledge and judgment were never made explicit; they lived in one person's head.
• A process that worked at low volume becomes a bottleneck because it never became faster or smarter as demand grew; it simply became more strained.
• A process that was acceptable in a smaller business becomes a liability when compliance, larger contracts, or increased scrutiny expose its informal and undocumented nature.

Growing businesses face the greatest risk from process inertia because growth is exactly what exposes cracks in processes that were never designed to scale.

How to build internal buy-in for change

If resistance is a response to real concerns, pushing harder is not the answer. Address what is driving it.

1. Make the invisible cost visible

Instead of arguing abstractly that the business should modernise, calculate the labour, error, and opportunity costs of the current process. A specific defensible figure is more persuasive than a general sense that things could improve.

2. Separate the process from the person

Make it clear that questioning a process is not questioning the person who created it. Involve that person in designing the replacement, turning a potential source of resistance into the expert best placed to make the new approach work.

3. Start with the highest-leverage process, not the easiest

A quick but low-impact win will not build support for meaningful change. Start with a process causing genuine, widely felt pain so the improvement is visible and persuasive.

4. Treat the transition as a process, not an event

A sudden switch from a familiar old process to a complete new one creates more resistance than a phased transition that lets people adapt and give feedback. This is one reason an MVP often works better than a big-bang rollout.

5. Be honest about the discomfort

Change causes some disruption even when it is clearly beneficial. Acknowledging that reality and addressing it directly builds more trust than promising an effortless transition that does not match people's experience.

The bottom line

“We've always done it this way” is not a character flaw and is not automatically wrong; sometimes the existing process remains the right one. But it should become a question answered deliberately, not a default accepted through inertia. Businesses that keep growing smoothly periodically ask whether old answers still fit their current size and change them when they do not.

If changing a process feels harder than living with it, look again. The discomfort of change is often smaller and shorter-lived than the cost of staying the same.