Organizations are trained to remove friction

Business improvement often begins with a sensible question: where are customers or employees experiencing unnecessary difficulty?

That question has created better products, faster service and simpler operations.

But ‘remove friction’ can become too broad.

Friction is waste when it serves no legitimate purpose. Friction is valuable when it protects judgment, accountability, learning or system integrity.

The mistake of universal streamlining

A company may try to eliminate every approval, review, handoff and check because each one slows the process.

Some should be removed.

Others exist because risk increases when a process becomes too easy.

The challenge is not simplification alone.

It is intelligent simplification.

Controls are designed friction

Financial controls, legal review, safety checks and access permissions intentionally slow some actions.

They are not inefficiencies by definition.

Their value depends on whether the risk they reduce justifies the delay they create.

The Control-to-Burden Ratio

Every control should be evaluated by two dimensions: how much risk it reduces and how much burden it imposes.

A high-burden, low-value control should be redesigned or removed.

A low-burden, high-value control should usually remain.

This prevents both bureaucracy and recklessness.

Verification protects trust

Customers want convenience.

They also want accuracy, security and reliability.

A frictionless process that produces fraud, error or irreversible mistakes is not good customer experience.

Trust depends on knowing where verification matters.

The signature problem

Organizations sometimes retain controls long after technology makes them unnecessary.

A wet signature, manual approval or duplicated entry may once have served a purpose.

If that purpose can now be achieved more safely and simply, the old friction becomes waste.

Controls should be purpose-based, not tradition-based.

Friction can create better decisions

A consequential decision may benefit from a second approver, cooling-off period or written rationale.

These mechanisms slow action slightly.

They also force assumptions into the open.

The delay is valuable when the cost of error is high.

The learning cost of automation

When a process becomes fully automated, employees can lose contact with how the system works.

This may be acceptable for routine tasks.

But where exceptions matter, organizations need enough human understanding to diagnose failure.

Automation should remove repetitive burden without erasing operational knowledge.

Exception handling is where capability lives

Routine cases are increasingly easy to automate.

Human value concentrates in exceptions.

Employees therefore need practice with ambiguous cases, not only exposure to the happy path.

A system that hides all complexity until a crisis appears creates brittle expertise.

The Useful Friction Matrix

A simple organizational matrix can classify friction by purpose.

Remove: duplicated entry, unnecessary handoffs, pointless waiting.

Automate: repetitive low-risk verification.

Preserve: judgment points, safety checks, high-risk approvals.

Strengthen: learning loops, challenge processes, post-incident review.

The objective is not less friction everywhere.

It is the right friction in the right place.

Customer convenience and informed choice

A one-click purchase is convenient.

A one-click high-risk financial commitment may be irresponsible.

As consequence rises, systems should increase clarity, confirmation and explanation.

Good experience design is proportional to risk.

Friction and accountability

Approvals can clarify who is responsible.

Removing every checkpoint can create faster execution while making accountability vague.

Organizations should avoid designs in which everyone can act but nobody clearly owns the consequence.

Strategic friction

Leadership teams also need productive disagreement.

A culture with no friction may look aligned because nobody challenges assumptions.

The absence of dissent can be a sign of psychological weakness rather than strategic strength.

Useful organizational friction includes the freedom to say, ‘This does not make sense.’

The challenge function

Important decisions should have someone responsible for challenge.

Not opposition for its own sake.

The goal is to test the argument before reality does.

A challenge function creates intellectual friction at low cost compared with market failure.

Innovation needs constraints

Constraints can stimulate creativity.

A clear budget, deadline or design requirement forces prioritization.

Unlimited optionality can create drift.

The right constraints help teams focus on the problem that matters.

The Friction Audit for Organizations

For every recurring obstacle, ask:

What purpose does this serve?

What risk appears if it disappears?

Can technology reduce the burden without removing the protection?

Who experiences the friction?

Does it improve learning, judgment or accountability?

Is there a simpler way to achieve the same protection?

Friction debt

Just as systems accumulate technical debt, they can accumulate friction debt.

Old approvals, duplicate systems and outdated processes remain because nobody owns removal.

Employees adapt through workarounds.

The organization becomes slower without knowing why.

Regular friction audits prevent this accumulation.

The opposite danger: control debt

Organizations can also accumulate control debt: too many safeguards are removed in the pursuit of speed.

The process becomes efficient until fraud, error, safety failure or governance breakdown exposes what was lost.

A mature organization balances friction debt against control debt.

Human capability should survive automation

The objective of automation should be to release people from low-value repetition and move human attention toward judgment, relationship, creativity and exception handling.

If automation leaves people less able to understand the business, the design may have optimized the task while weakening the institution.

The final systems principle

Efficiency is not the absence of friction.

Efficiency is the removal of friction that does not serve the purpose.

A resilient organization keeps the friction that protects what matters.

The best system is not frictionless. It is free of waste and rich in the safeguards, challenge and learning that make good performance durable.

The zero-friction myth in customer experience

Customer experience teams often pursue fewer steps, fewer clicks and less waiting.

That is usually useful.

But the mature objective is not zero friction.

It is minimum necessary friction consistent with safety, trust and informed choice.

Controls should expire unless justified

Organizations can prevent friction debt by giving some controls review dates.

If a step still protects a real risk, renew it.

If the original purpose has disappeared, remove it.

This prevents temporary safeguards from becoming permanent bureaucracy.

Automation needs manual competence

Where automated systems control important workflows, organizations should decide which manual capabilities must be retained.

Run drills.

Test fallback processes.

A backup that nobody remembers how to use is not a real backup.

Friction can reveal weak demand

Sometimes removing friction increases usage.

That can be good.

But organizations should ask whether greater usage reflects genuine value or merely easier access.

Not every increase in activity is proof of improved outcomes.

The governance of defaults

Defaults can simplify operations and customer journeys.

They should be reviewed where the default has financial, privacy, safety or strategic consequences.

Ease should not become a substitute for informed choice.

Useful internal friction

Strong organizations preserve places where assumptions are challenged.

Risk committees, peer review, second signatures, red-team exercises and post-incident reviews all create friction.

Their value lies in catching error before reality imposes a larger cost.

The resilience reserve

Every organization should preserve some unused capacity: backup suppliers, human knowledge, decision authority, cash, time or technical redundancy.

Unused capacity can look inefficient in stable periods.

It becomes invaluable when conditions break.

Maximum efficiency and maximum resilience are not the same objective.

Convenience for leaders can become burden for teams

A senior leader may simplify their own workflow by asking teams for frequent custom reports.

The convenience is local; the burden is distributed.

System design should follow total organizational cost, not merely the convenience of the most powerful user.