The Hidden Cost of "We've Always Done It This Way"

The Seven Most Expensive Words in Business: "We've Always Done It This Way."

It's Monday morning.

A new employee has started work at your company.

They're intelligent, enthusiastic and keen to understand how things operate.

They've just been shown how to process a customer order.

First, the order gets printed.

Then someone signs it.

Then it gets scanned.

Then the scanned document gets emailed to another department.

That department prints it again.

And finally, someone types the information into a spreadsheet.

The new employee raises a perfectly sensible question.

"Why don't we just process it digitally?"

An experienced colleague looks up from their desk.

There's a moment of silence.

Then comes the answer.

And with those words, the conversation ends.

Nobody remembers exactly when the process started.

Nobody knows whether the original reason still exists.

And nobody has checked whether there's now a better way to do it.

The process simply continues.

Now, tradition isn't automatically a bad thing.

Some longstanding business procedures exist for excellent reasons. They may protect safety, prevent fraud, support customers or satisfy legal obligations.

But others survive simply because nobody has challenged them.

At DigitalBooth, our Operational Audit service examines how businesses operate, from the moment an enquiry or order arrives to the people, processes and systems involved in delivering it.

And one particularly useful question is:

Let's visit the museum.

Why Do Businesses Keep Processes That No Longer Make Sense?

Usually, nobody wakes up in the morning and decides to make the business deliberately inefficient.

Outdated processes often develop gradually.

A company starts small.

A particular method works perfectly well.

Then the company grows.

More employees.

More customers.

More departments.

And more complicated requirements.

But the original process doesn't change.

What worked for five employees is now being used by fifty.

Sometimes the system becomes awkward so gradually that nobody notices.

Other reasons include fear of disruption, unclear responsibility, lack of time or uncertainty about whether an alternative would actually work.

And sometimes the original reason for a process has simply been forgotten.

Understanding why a process exists is essential before changing it.

Otherwise, you might remove something that was providing a useful control.

Ten Outdated Business Habits That Deserve a Proper Review

How Much Can an Outdated Business Process Actually Cost?

Let's look at a fictional company with an approval process that requires fifteen unnecessary minutes of administration per request.

Assume the company processes twenty such requests each week.

That's five hours of staff time per week.

Using an illustrative employee cost of £25 an hour and fifty working weeks per year:

The calculation is straightforward.

But the real business question is more complicated.

Are all fifteen minutes unnecessary?

Does the approval process prevent costly mistakes or unauthorised purchases?

Could the process be simplified without weakening controls?

And what would the business do with any staff time released?

The £6,250 figure is an estimate of time currently allocated to the process, not a guaranteed cash saving.

The actual value of changing the process depends on the answer to those questions.

Not Every Old Process Is Bad. Some Exist for Very Good Reasons.

Here's something that deserves proper attention.

An old process isn't necessarily an inefficient process.

Some activities have remained unchanged because they work.

Some checks exist to protect customers, employees or the business.

And others are required by contracts, safety procedures or legislation.

For example, an engineering inspection may need a formal sign-off.

A financial transaction may require separation of duties.

And particular records may need to be retained in an appropriate format.

Removing those steps simply to save a few minutes could create much larger problems.

The objective is to remove unnecessary effort while maintaining the controls the business genuinely needs.

That's a better goal than simply making every process shorter.

Why Staff Resist Change. And Why They Might Have a Point.

Management decides to introduce a new system.

A presentation is prepared.

The director announces that everything is going to be faster, easier and more efficient.

The new software launches Monday.

By Tuesday, half the team wants the old system back.

It's tempting to blame the employees.

"They just don't like change."

But sometimes staff resistance is useful feedback.

Maybe the new system requires more steps.

Maybe nobody explained why the process is changing.

Maybe staff weren't involved in testing.

Or perhaps the application genuinely doesn't work properly on the devices employees use.

That doesn't mean every objection should stop a worthwhile improvement.

It means those objections should be understood.

A business process should be designed around real operational needs, not just what looks impressive in a management presentation.

How to Fix an Outdated Process Without Turning the Office Upside Down

You don't need to replace every system by next Tuesday.

In fact, trying to do everything at once can introduce unnecessary risk.

A more practical approach is to select one process, understand it properly and test a sensible improvement.

Sometimes the improvement is surprisingly simple.

A clear handover.

One agreed record.

A shorter approval route.

A better-designed form.

And other times, software or automation is worth investigating.

The right solution depends on the process.

Do You Need New Software to Fix an Old Business Process?

Not always.

In fact, purchasing new software before understanding the underlying problem can make matters worse.

Imagine a company with a complicated approval process.

Management decides to automate it.

So now the request travels through the same unnecessary seven stages.

But digitally.

Congratulations.

You've built a faster version of the wrong process.

Before commissioning software, consider whether the process could be simplified first.

DigitalBooth provides CRM & Business Automation and App Development for projects where technology is part of the solution.

But selecting the right technology should follow a proper assessment of the requirements.

What Happens When Nobody Ever Reviews the Process?

A process that worked well years ago may become unsuitable as the company grows.

More employees.

Different customer expectations.

New software.

Changed regulations.

And new operational requirements.

If processes aren't reviewed, a business may gradually accumulate extra steps, duplicated records and inconsistent procedures.

This can create more than just financial cost.

Regular process reviews help identify these issues before they become larger problems.

Who Actually Owns Your Business Processes?

Here's a question worth asking in your next management meeting.

Who is responsible for keeping each important process up to date?

Not who performs it.

Who owns it.

Who checks whether it still works?

Who approves changes?

And who makes sure the documentation matches what employees actually do?

Without clear ownership, outdated procedures can survive indefinitely.

Everyone uses the process.

Nobody feels responsible for reviewing it.

So the company ends up operating on a collection of inherited habits.

Build a Business Where People Are Allowed to Ask "Why?"

Some of the best operational improvements start with an employee asking an innocent question.

"Why do we enter this twice?"

"Why does this need printing?"

"Why does the report take three hours?"

"Why can't operations see the information sales already has?"

Those questions shouldn't automatically be treated as criticism.

They can reveal opportunities.

Of course, employees won't always know the full reason a control exists.

Management may have access to legal, financial or contractual information that explains it.

But that is an opportunity to explain the requirement.

If nobody can explain why a process exists, it deserves investigation.

The DigitalBooth "Does This Process Still Make Sense?" Checklist

Use these questions to review an established procedure.

A few uncertain answers may justify a closer review.

But the objective should be better business outcomes, not change for its own sake.

How DigitalBooth Reviews Outdated Business Processes

Imagine a growing company approaches us.

It's been trading successfully for years.

The staff are experienced.

Customers are generally happy.

But internal administration is becoming increasingly complicated.

Management suspects there are inefficiencies but doesn't know where to start.

A practical review would begin by understanding how the business actually operates.

Our Operational Audit service is designed around this broader examination of how businesses work.

Final Verdict: Tradition Is Lovely. Unnecessary Administration Isn't.

There's nothing wrong with a company having established ways of working.

Experience matters.

Consistency matters.

And reliable procedures can be extremely valuable.

But processes shouldn't survive forever simply because nobody remembers who created them.

Businesses change.

Technology changes.

Customer requirements change.

And what worked brilliantly ten years ago may now be creating avoidable work.

The answer isn't to replace everything at once.

It's to examine the processes that matter, understand why they exist and improve those that no longer serve the business well.

Sometimes the answer is better training.

Sometimes it's clearer responsibilities.

Sometimes it's using existing software properly.

And sometimes a bespoke application can help.

But the next time somebody says:

"We've always done it this way."

Try asking:

"Does that mean it's still the best way?"

It's a simple question.

But it could start a very useful conversation.

Frequently Asked Questions