When Removing Friction Backfires (and When Adding Trust Does)

A better system increases trust and decreases friction. Both halves matter. When you only remove friction without adding trust, people end up rejecting the system or regulating it. When you only add trust while piling on friction, people quietly route around it. The systems that win do both at once. This article walks through how each mistake happens, why it is so common, and how to apply the Trust and Friction framework so your next improvement does not create a new problem.

When removing friction backfires

Removing friction feels like progress. Fewer steps, faster replies, less waiting. Most of the time it is progress. But friction sometimes does a quiet job you did not notice, and when you take it away without replacing that job, things go wrong.

The clearest example is communication. Couriers gave way to mail, the telegraph, the phone, email and messaging. Each step was faster. But speed without trust gave us spam, scams and deepfakes. Once sending a message cost nearly nothing, bad actors could send millions of them. The friction that used to slow down honest senders had also been slowing down dishonest ones.

Inside a business, the same pattern shows up in smaller ways.

• A checkout with no guarantee. One-click buying is great when the customer trusts you. If they do not, a faster checkout just leads to faster regret, refunds and disputes.
• Skipping the kickoff call. Cutting a step from onboarding saves an hour, until clients start the work with the wrong expectations.
• Letting anyone send invoices or payments. Removing an approval step speeds things up, and also removes the one moment where a mistake would have been caught.
• Automating an unreliable process. This is the big one right now.

The AI version of this mistake

Many businesses are adding AI on top of their existing friction. If a process already produces errors, rework and confused customers, an agent running it will produce errors, rework and confused customers faster. If you have ever been camping, you know faster friction makes a fire. And now you are a firefighter.

The fix is to put the order right. Fix the system first by raising trust and cutting friction. Then let agents run the better system.

When adding trust backfires

The opposite mistake is just as common, and it often comes right after the first one. Something goes wrong, so a check gets added. Then another. Then a form, a sign-off and a weekly review. Each one was meant to add trust. Together, they bury the work.

When a system adds trust while piling on friction, people route around it. Think of bureaucracy and compliance theater: rules that look like safety but mostly create delay. In a business, it looks like this.

• Approvals so slow that the team starts making decisions without asking.
• Reports nobody reads, filled in because they are required.
• Sign-up forms so long that good prospects give up before they finish.
• A process so strict that the best people work around it to get results.

The worst part is that routing around a system destroys the trust it was meant to create. Now there is an official process that looks controlled and a real process nobody can see.

The ones that do both

The best improvements raise trust and lower friction in the same move. The 1985 example is a good model. Cash could be lost or stolen and checks could be faked, so everybody stayed on guard. Credit card chargeback protection added trust, because a bad deal could be reversed. That same protection removed friction, because people no longer had to be so careful with every purchase. One change, both directions.

Ride-share works the same way. Getting into a stranger's car went from something parents warned you about to normal, once ratings and live tracking closed the trust gap. Booking a ride also got easier. The trust features are what made the convenience acceptable.

Society followed a similar path. Trust was high in the 1950s and eroded through the 80s as the world globalized and people could no longer look each other in the eye. Since the 90s it has been rebounding, largely because technology keeps closing the gaps: chargebacks, reviews, trust indicators, class actions. That is not a case for a nanny state. There is a happy medium. When there are fewer ways to abuse trust at the margins, more people get to live trusting lives.

A simple check before you change anything

Before you remove a step or add one, ask both questions about the change itself.

A few questions help you catch the hidden job a step might be doing:

1. What could go wrong if this step disappeared?
2. Who is currently catching that problem, and how?
3. Is there a lighter way to catch it, such as a guarantee, a clear rule or an automatic check?
4. If people are skipping this step already, what does that tell you about it?

This applies to people too

The same balance shows up with the people already on your team. Someone who moves fast but needs constant checking is lowering friction while lowering trust. Someone who is careful but slows every project down is adding trust while adding friction. Neither is a verdict on the person. It is a starting point for a conversation about how they can do both.

Keep stepping

You will never remove all the friction, and you should not try. The goal is a long series of small steps, each one raising trust, lowering friction, or ideally both. When a step only moves one side, pause and ask what it is costing on the other.