Operational Friction, Explained

Speak to people inside a growing business and the conversation rarely begins with strategy. It begins with the working day.

A report took the whole morning to pull together. An order had to be typed into two places. A number was checked in one system, corrected in another, then confirmed by email. A customer asked for an update, but nobody could say with confidence where the job had reached.

These are not grand problems. They are ordinary ones. That is why they matter.

This is operational friction. It is the operational problem people notice first, because they do not encounter it as theory. They meet it in the work. It is the extra effort, the repeated checking, the delay, the uncertainty, and the low-level irritation that builds into the day.

What friction is

Operational friction is the resistance people face when trying to get work done.

It is the gap between how much effort a task should need and how much effort it actually takes. A simple action becomes a small project. A decision waits for missing information. A customer answer depends on three separate checks. A job moves forward only because someone remembers to nudge it.

If operational complexity explains why a business has become difficult to manage, friction is the way that difficulty is felt by the team. Complexity often sits in the background. It is built into structures, systems, handovers, exceptions, and reporting lines. It may be hard to see from one desk.

Friction is different. It is immediate. It shows up in the inbox, the spreadsheet, the call, the second screen, the manual correction, and the question nobody can answer without asking someone else.

Complexity is quiet. Friction is noisy.

It is the person chasing an approval. It is the manager rebuilding the same report every Friday. It is the administrator comparing two sources because neither can be trusted on its own. It is the salesperson waiting for a stock answer. It is the finance team correcting data that entered the business badly at the start.

Most businesses have some friction. That is normal. The issue is not whether it exists. The issue is whether it has become part of the operating model without anybody choosing it.

Where it comes from

Friction appears when the way people need to work and the way the business is set up do not fit together.

Often, it starts with systems that cannot share information. One tool holds the customer record. Another holds the order. A third holds the job status. A fourth produces the invoice. None of this is a problem if the movement between them is clear and reliable. But when it is not, a person becomes the link.

That person copies information across. They check whether it arrived. They fix what changed on the way. They keep their own list, because the official system does not quite answer the question the team needs answered.

Friction also comes from processes that made sense at an earlier stage of the business. A founder once handled approvals personally. A team once sat in the same room. A spreadsheet once tracked ten jobs well enough. A weekly meeting once caught every exception.

Then the business grew. More people joined. More customers arrived. More products, services, locations, or contract types were added. The old process stayed in place, but the weight on it changed. What was once informal becomes fragile. What was once quick becomes slow.

Information is another common source. It stops moving. It sits in an inbox, a spreadsheet, a downloaded file, or the head of one experienced employee. Other people wait for it. Work pauses until it is found, checked, or explained.

Knowledge can create the same problem. In many firms, important know-how lives with individuals rather than inside the business. Someone knows which customer needs a special check. Someone remembers how the month-end file is built. Someone understands why a report never quite matches the system total.

That knowledge may be valuable, but it is also a risk when it has no proper home. If the right person is busy, away, or leaves, the work slows down.

The symptoms are usually easy to recognise. Manual work that should happen without intervention. The same data entered more than once. A spreadsheet that has become essential without ever being designed as a core system. Reports that take a day to assemble. Requests managed through email until one is missed.

None of these issues needs to look dramatic. In fact, they often look sensible in isolation. A small workaround here. A quick check there. A spreadsheet to cover a gap. An email trail to keep everyone informed.

But together, they change how the business feels to run.

Why we stop noticing it

The odd thing about friction is how quickly people adapt to it.

At first, a workaround is clearly a workaround. Everyone knows it is temporary. Someone says they will fix it when things are quieter. The team carries on, because the work has to be done.

Then time passes.

The extra step becomes normal. The spreadsheet becomes the place people trust. The manual check becomes part of the role. The person who knows the workaround teaches it to someone new. Before long, the workaround is no longer treated as a sign of a broken process. It is treated as the process itself.

This is one reason operational friction can be hard for owners to see. They may not be close enough to the small daily compromises. Or they may see each one separately and judge it too minor to worry about.

That judgement is understandable. One copied field is not a crisis. One delayed report is not a strategic threat. One missed email may be written off as human error. One spreadsheet may look like practical initiative.

The problem is the total.

Friction is rarely measured as a whole. It is spread across people, teams, weeks, and months. It hides in five-minute tasks repeated hundreds of times. It hides in the half hour before a meeting, when someone is trying to make the numbers line up. It hides in the extra calls needed to confirm what should already be visible.

Because nobody sees the full amount, nobody quite owns it.

New staff then inherit it. They are trained to follow the workaround, not to question why it exists. They learn which report is unreliable, which system is out of date, and which person to ask before taking the data seriously.

In that moment, friction has become part of the culture. Not because anyone wanted it there, but because the business learned to cope.

What it costs

The cost of friction is real, but it rarely appears neatly in the accounts.

The largest cost is often labour. When a process depends on people pushing it along, their time becomes the price of that weakness. If half of someone’s role is spent re-keying, checking, chasing, and reconciling, that is not a small admin issue. Over a couple of years, it can amount to a full salary spent on work that creates no new value.

That time could have gone elsewhere. Better customer service. Faster billing. Cleaner reporting. More careful buying. Stronger management. More useful conversations with clients or staff.

Friction also creates delay. Decisions wait while information is gathered. Managers delay action because they do not yet trust the numbers. Customers wait for updates. Work waits for approval. Opportunities move on while the business is still trying to understand its own position.

Then come errors.

Every manual step is a chance for something to go wrong. A number is typed incorrectly. A discount is missed. A job is priced using old information. An order is entered twice. A customer promise is made on the basis of an incomplete view.

Some errors have a clear financial cost. Others are harder to price. They affect confidence. They make customers ask twice. They make teams cautious. They make managers spend more time checking than deciding.

There is also a human cost.

Good people do not usually mind hard work. They do mind pointless work. They notice when their time is spent fighting the system rather than doing the job they were hired to do. They notice when the business asks them to care, but gives them poor tools, unclear information, and avoidable admin.

Over time, that wears people down. It also dulls the business. Energy goes into coping rather than improving. Capable staff become the shock absorbers for weak process.

That may keep things moving for a while. It is not a healthy way to run.

Friction is the most fixable layer

There is a useful point here. Of the common operational problems, friction is often the quickest to improve.

Operational complexity takes careful thought, because it is structural. It may involve roles, service lines, customer types, reporting needs, approvals, and the shape of the business itself. Operational debt can also take time to unwind, because it has often accumulated over many years.

Operational friction sits closer to the surface.

It can often be reduced by removing a step, clarifying ownership, changing where information is captured, or connecting two systems so a person no longer has to stand between them. The work is not always glamorous, but it is practical. It deals with the places where time is being lost today.

A good place to start is wherever people are compensating for the system.

Look for copying. Look for checking. Look for chasing. Look for bridging. Look for lists kept outside the main system because the main system does not show the truth clearly enough. Look for reports rebuilt by hand. Look for inboxes being used as workflow tools. Look for the person everyone depends on because nobody else can find the answer.

These are not personal failings. They are signals. The business is asking a human being to do work the operating model should be doing.

That is friction. Much of it can be removed.

The method Simplify then Connect then Build is useful because it keeps the order sensible. First, simplify the process. Remove steps that no longer serve a purpose. Make ownership clear. Decide what information is really needed and where it should enter the business.

Then connect what should already be connected. Let information move without being carried manually. Reduce the number of places people need to check before they can act.

Only then build. New tools can help, but they should not be used to preserve a poor process in a more expensive form. The point is not to add more machinery. The point is to make the work easier to run.

When enough friction is removed, the change is felt quickly. The day becomes lighter. People stop pushing so hard just to keep ordinary work moving. Managers get clearer information sooner. Customers receive better answers. The business becomes less dependent on memory, chasing, and heroic effort.

That is a practical step towards operational clarity.

Work should still require judgement. It should still require care. But it should not require people to fight the same avoidable resistance every day.