The Hidden Cost of “We’ve Always Done It This Way”

Every organization has processes that seem to exist for one simple reason: that’s the way they’ve always been done.

Maybe it’s a spreadsheet that gets updated manually every Friday. Maybe information has to pass through three people before someone can make a decision. Maybe employees are copying data from one system into another because the two systems don’t communicate. Or maybe a report takes hours to build even though very little changes from week to week.

Individually, these tasks may not seem like major problems. They get done, the business keeps moving, and employees learn how to work around them.

But over time, those workarounds become expensive.

The cost of inefficient processes is rarely obvious because it does not always appear as a separate line on a financial statement. Instead, it shows up in lost time, duplicated work, delayed decisions, preventable errors, frustrated employees, inconsistent customer experiences, and missed opportunities.

For organizations trying to grow, improve productivity, or adopt new technologies such as automation and artificial intelligence, these hidden inefficiencies can become a serious obstacle.

Sometimes improving performance does not start with introducing something new.

It starts with questioning something old.

Inefficiency Is Often Hiding in Plain Sight

When organizations think about reducing costs, they often focus on obvious expenses: software subscriptions, vendors, equipment, facilities, or staffing.

Operational inefficiency is harder to see.

Five minutes spent entering the same information twice does not seem significant. Neither does waiting an hour for an approval, spending 20 minutes searching for the latest version of a document, or manually creating a report every Friday afternoon.

But small inefficiencies become much larger when they happen repeatedly.

Imagine a task that takes an employee just 15 unnecessary minutes each day. Over a five-day workweek, that becomes more than an hour. Multiply it across a year and then across dozens or hundreds of employees, and what appeared to be a minor inconvenience becomes a significant amount of organizational capacity.

The real cost is not simply the time spent performing unnecessary work.

It is also the work employees could have been doing instead.

An employee who spends hours copying information between systems is not spending those hours serving customers, analyzing problems, developing new ideas, improving operations, or completing other work that requires human judgment.

That opportunity cost is one of the most important—and most overlooked—consequences of inefficient processes.

How Temporary Workarounds Become Permanent

Many inefficient processes were never intentionally designed to be permanent.

They started as solutions.

A system did not provide the information someone needed, so an employee created a spreadsheet.

The spreadsheet became difficult to manage, so another tracker was created.

People were unsure who had the latest information, so an additional meeting was scheduled.

Managers needed visibility, so employees started sending another weekly report.

Someone needed to approve a decision, so an additional email step was added.

Each change probably made sense at the time.

The problem occurs when temporary solutions remain in place long after the original problem has changed.

Over months or years, organizations accumulate these workarounds. Eventually, employees may no longer know why certain steps exist. They simply know that those steps are required.

The workaround has become the process.

This is one reason inefficient operations can be difficult to recognize from inside an organization. Employees become extremely good at navigating them.

They know which spreadsheet contains the right information. They know which person needs to be copied on an email. They know who actually approves a request even if the official procedure says something different. They know which report has to be manually corrected before leadership sees it.

From the outside, the process may appear complicated.

From the inside, it feels normal.

Familiarity, however, should not be confused with efficiency.

People may simply have become skilled at compensating for a process that no longer works well.

The Cost Goes Beyond Labor Hours

Wasted time is one of the easiest consequences of inefficient processes to understand, but it is far from the only one.

Poor processes can create problems throughout an organization.

Errors

Manual and repetitive work creates more opportunities for mistakes.

If information has to be copied from one system into another, every transfer creates another opportunity for something to be entered incorrectly, omitted, duplicated, or placed in the wrong location.

One mistake may then affect reports, decisions, customer communication, or other downstream activities.

Delays

Every unnecessary handoff adds time.

A process requiring several approvals may seem responsible, but if each approval creates hours or days of waiting, the organization can become slow to respond.

In competitive environments, slow decisions have real consequences.

Inconsistent Information

Organizations frequently develop multiple versions of the same information.

One department has its spreadsheet. Another has a different report. A third group relies on information stored in another system.

Soon, meetings begin with a surprisingly difficult question:

Which number is correct?

When employees cannot trust the information available to them, decision-making becomes slower and more difficult.

Employee Frustration

Repetitive administrative work can be frustrating, particularly when employees know a process could be simpler.

Organizations hire talented people for their judgment, creativity, expertise, communication skills, and problem-solving ability.

Using significant portions of their time for repetitive tasks is not only inefficient—it can also reduce engagement.

Customer Experience

Customers may never see an organization's internal processes, but they experience the results of them.

A delayed approval can become a delayed response.

Incorrect data can become incorrect customer information.

Poor communication between departments can force customers to explain the same issue multiple times.

Internal operational problems eventually become external customer experiences.

Difficulty Scaling

Inefficient processes become especially dangerous during growth.

A manual process may be manageable when a company has 10 customers, 20 employees, or a relatively small number of transactions.

Double or triple the workload, however, and that same process may become unsustainable.

Instead of growth creating greater efficiency, the organization may respond by adding more people simply to manage the additional administrative work.

The organization is scaling the inefficiency along with the business.

The Compounding Effect of Small Problems

One inefficient process rarely exists by itself.

Organizations operate through interconnected workflows.

A delay in one department can create additional work for another. Incorrect information entered at the beginning of a process may need to be corrected several times downstream. A report that arrives late can delay a decision, which then delays another team.

This creates a compounding effect.

Consider something as simple as an unclear intake process.

A customer or employee submits incomplete information. Someone has to review the request and identify what is missing. An email is sent asking for clarification. The recipient responds later. The request returns to the original employee, who has to reopen the task and remember where it left off.

What could have been completed once has now been touched several times.

Multiply that pattern across hundreds of requests and the cost becomes significant.

That is why process improvement should look beyond individual tasks.

The goal is to understand how work moves through the organization from beginning to end.

Before Adding Technology, Look at the Process

Organizations are increasingly turning to automation and artificial intelligence to improve productivity.

That creates tremendous opportunities.

But technology alone does not fix an inefficient workflow.

In some cases, it can make the problem worse.

Automating an unnecessary step simply allows the organization to perform an unnecessary step faster.

Digitizing a confusing process creates a digital confusing process.

Adding artificial intelligence to a workflow that nobody fully understands can introduce additional complexity instead of reducing it.

Before asking, “How can we automate this?” organizations should first ask:

“Why are we doing this at all?”

That question changes the conversation.

Perhaps a report does not need to be created.

Perhaps two approvals can become one.

Perhaps information can be captured correctly at the beginning instead of corrected later.

Perhaps several spreadsheets can be replaced with one reliable source of information.

Perhaps a meeting exists only because employees do not have visibility into the status of work.

Once the process is understood and improved, technology can become far more valuable.

Automation can handle repetitive activities. Artificial intelligence can assist with analysis, classification, communication, and decision support. Analytics can provide better visibility. Integrated systems can reduce duplicate data entry.

But technology works best when it supports a process that makes sense.

Start With the Friction

Finding opportunities for process improvement does not always require a massive transformation initiative.

One of the best places to start is simply by listening to the friction employees experience every day.

Ask questions such as:

Where are people entering the same information more than once?

Which reports take an unreasonable amount of time to create?

Where do employees regularly wait for approvals?

What information is difficult to find?

Which processes generate the most complaints?

Where do mistakes happen repeatedly?

Which activities depend heavily on one person knowing how everything works?

Where are spreadsheets being used to compensate for limitations in existing systems?

Which meetings exist primarily to provide status updates?

What tasks do employees immediately describe as “tedious,” “manual,” or “time-consuming”?

Those frustrations are not simply complaints.

They are operational data.

Employees who perform a process every day often know exactly where the problems are. They may even have ideas for improving them.

Organizations simply need to ask.

Measure Before You Change

Not every inconvenience requires a major redesign.

Process improvement should focus on areas where change can create meaningful value.

That requires measurement.

Organizations can begin with basic questions:

How often does the process occur?

How many people participate?

How long does it take?

How much of that time is active work versus waiting?

How often do errors occur?

How frequently does work have to be corrected or repeated?

What happens if the process is delayed?

Once those questions are answered, organizations can prioritize opportunities based on impact.

A five-minute improvement to a task performed once a month may not matter very much.

A five-minute improvement to a task performed thousands of times could be extremely valuable.

Measurement helps organizations distinguish between processes that are merely annoying and processes that are genuinely expensive.

Process Improvement Is Also About People

Operational improvement is sometimes described as if it were purely technical.

It isn't.

Processes are performed by people.

Employees need to understand why a process is changing, how the new approach works, and what is expected of them.

This becomes especially important when automation or artificial intelligence is introduced.

Employees may understandably wonder what new technology means for their responsibilities. If changes are implemented without communication or training, even a technically strong solution can struggle.

Successful process improvement should involve the people closest to the work.

Their experience helps identify problems that may not be visible in a process map or leadership meeting. Their involvement also makes it easier to design solutions that work in the real world rather than only on paper.

The goal should not simply be to make employees work faster.

It should be to remove unnecessary work so employees can spend more time on activities where their knowledge and judgment create greater value.

Build a Habit of Questioning the Process

The most effective organizations do not wait until a process completely fails before examining it.

They develop a habit of continuous improvement.

That does not mean constantly changing everything.

It means creating an environment where employees are allowed to ask:

Why do we do this?

Is this step still necessary?

Could this information be captured once instead of three times?

Does everyone involved in this approval actually need to be involved?

Could technology handle this repetitive task?

What would happen if we removed this step?

These questions create a culture where processes are treated as tools rather than traditions.

A process should exist because it helps the organization achieve an objective—not because nobody remembers a time before it existed.

“That’s How We’ve Always Done It” Is a Signal

Not every old process is a bad process.

Some procedures have survived for years because they work extremely well. Experience and consistency have real value, particularly in environments where accuracy, safety, compliance, or reliability matter.

But longevity should not be the only reason a process continues.

Organizations change.

Customers change.

Employees change.

Technology changes.

The volume and complexity of work change.

Processes should evolve with them.

When the answer to “Why do we do it this way?” is simply “because we always have,” that does not automatically mean the process should be eliminated.

It does mean the process deserves another look.

At Kimemasu, process improvement is a core part of how we help organizations prepare for automation, AI implementation, analytics, and digital transformation. The goal isn't technology for technology's sake. It's creating operations where people, processes, data, and technology work together more effectively.

The organizations that benefit most from new technology are often not the ones that adopt the most tools.

They are the ones that first understand how their work actually gets done.

Because sometimes the biggest opportunity for improvement isn't adding something new.

It's finally questioning something old.