Friction That Someone Quietly Removed

Category: Why This Was Never an Accident The reason it’s easy now is that someone made it easy — and then disappeared.

For years, getting a new starter set up took the better part of a week. The form had thirty-one fields. Several asked for information the new person couldn’t possibly have yet — a payroll number that didn’t exist until they’d been processed, a manager’s cost code nobody had to hand. So the form would come back, get chased, get half-filled, then sit on someone’s desk. The first day was usually spent waiting for a login.

One year, someone in the team sat down with the form. They weren’t asked to, and weren’t thanked for it. They worked out which fields actually had to be filled in on day one, and which could be filled in later by the people who already knew the answers. Thirty-one fields became nine. The chasing stopped. New starters logged in on their first morning.

Nobody noticed. The people who arrived after the change had no idea it had ever been hard. A first-morning login was simply how it worked. The person who fixed it moved on.

Three years later, a process review found that the new-starter form looked thin next to the others, and added back the missing fields, for completeness.

The Principle

Most smooth processes are not smooth by default. They were sanded smooth, one removed obstacle at a time, by people who noticed a recurring small pain and took it out.

Friction is the confusing form that gets one field shorter. The approval step that quietly stops being required. The manual reconciliation that someone automated. The fudged workaround that someone finally made the real path. It is rarely the big, broken thing — those get noticed and fixed loudly. It is the small, repeated, tolerated friction that everyone has learned to live with.

When friction is removed well, the result is that nothing is hard any more. And a thing that isn’t hard doesn’t announce itself. Nobody experiences the absence of an obstacle as a feature. They just stop hitting it. The work was real, deliberate and skilled, but its entire output is a negative space: a pain that no longer happens.

Here is the inversion at the centre of it. Adding leaves an artefact. Removing leaves a hole, and a hole is invisible. So the most valuable kind of improvement is often the one that is hardest to see was ever made. The trap follows directly. Because the removal left no trace, the smoothness gets read as natural, and what was deliberately taken out can be put back by anyone who mistakes the gap for an oversight.

Why It Is Inevitable

This part of the chapter has to be honest about its own frame. Removing friction is not inevitable in the way that a process drifting or a delay favouring the status quo is inevitable. It is a chosen act. Nobody is forced to sit down with the form. The inevitability is on the other side: where the removal is not done, the friction is permanent, and it compounds.

That is what makes the removal high-leverage rather than merely nice. A recurring friction is paid every time the process runs. Remove it once and you stop paying it forever, for everyone. The friction the new-starter form imposed was not a one-off cost. It was a tax levied on every single hire, for years, and it would have gone on being levied indefinitely if nobody had touched it.

The cost it was imposing was distributed and hidden, which is precisely why it survived. A minute here. A chase there. A half-day a new starter lost waiting for a login. No single instance was large enough to demand attention, so no single instance ever triggered a fix. It took someone willing to add the instances up and see the total, which almost nobody does, because the total never appears anywhere.

And the removal required understanding, not just effort. You have to know which friction is load-bearing and which is residue — which field protects something real and which is there because it was always there. That discernment is the actual skill, and it is exactly the thing a careless later hand cannot replicate. The reviewer who added the fields back was not lazy. They simply could not see the judgement that had taken them out, so they could not reproduce it.

How It Shows Up

• The process that “just works now” and nobody can remember being any other way — because someone quietly took the rough edges off and never said.
• The form, the request, the sign-off that got shorter one year, and was never noticed getting shorter.
• The workaround that quietly became the official path, so the thing everyone fudged stopped needing to be fudged.
• The new person who has no idea anything was ever hard, working smoothly on day one in a system that took years of small removals to build.
• The well-meaning review that finds a process “looks thin” or “is missing a check” and adds friction back — for completeness, for consistency, to be safe — with no idea it was deliberately removed.

Why It Causes Benefit

The payoff from removing a small recurring friction is real, compounding, and almost entirely unattributed. It lands in three places.

The first is ease at scale. Every future run of the process is now cheaper, faster and less error-prone. The saving is small per instance and vast in aggregate, because the process runs and runs. The person who cut the form from thirty-one fields to nine did not save one week. They saved a fraction of a week on every hire, forever, which adds up to something no single dramatic project could match — and which no report will ever show, because the time saved simply never gets spent.

The second is freed attention. The friction wasn’t only slow. It was a tax on focus. Every confusing form, every step that needs working around, is a small cognitive cost — a moment where attention goes to fighting the process instead of doing the work. Removing the friction gives people that attention back. A new starter who logs in on the first morning spends the first morning starting, not waiting and chasing.

The third is a lower error rate. Frictions are where mistakes breed. The field people fudge because they can’t fill it in honestly. The step people skip under pressure. The workaround that goes wrong because it was never meant to be load-bearing. Remove the friction and you remove the failure mode that grew in it. A clean path is not just faster than a fudged one. It is safer.

The deeper benefit, and the one to sit with, is that a well-removed friction makes the whole thing feel natural and obvious, as though it could never have been otherwise. That feeling is the highest compliment to the work and the exact reason the work goes uncredited. The asymmetry is worth stating flatly. The gain from removing a small recurring friction is large, permanent and silent. The cost of leaving it in is small, repeated and equally silent. That symmetry of silence is why the friction survived so long in the first place, and why the person who finally removed it got thanked for nothing.

How To Cultivate It

• Treat recurring small pain as a signal, not a fact of life. The form everyone groans at, the step everyone works around, the thing that always needs chasing is a removal waiting to happen. Notice it instead of normalising it.
• Leave a note where you removed something. A one-line comment, a changelog entry, a “this field was removed on purpose, because X.” A trace costs nothing and is the only real defence against the reinstatement. It turns an invisible gap into a deliberate decision someone has to argue with before undoing.
• Before adding a step “for completeness,” ask whether it was ever there and removed on purpose. Treat a smooth, sparse process as possibly load-bearing by its absence. The gap may be the feature, not the oversight.
• Credit the subtraction. When someone removes a friction, name it as the win it is. “Less process” is hard to put on a slide, so celebrate it deliberately, or you train people to add visible things and never remove invisible ones.
• Default to removing before adding. When a process is painful, the reflex is to add a tool, a check, a step. The higher-leverage move is usually to ask what can come out. Reward the person who deletes a field over the person who builds a dashboard around it.

What Good Looks Like

An ongoing, enjoyed smoothness that everyone benefits from, nobody attributes, and — crucially — that is protected from being undone. The easy thing stays easy. The removed friction stays removed, because someone left a trace explaining why. The next reviewer reads the note and leaves the gap alone. And the people who do the quiet work of subtraction are recognised for producing less, not only the people who produce more.

The smoothest processes are not the ones that were always smooth. They are the ones someone patiently sanded down, one removed obstacle at a time, and then had the good sense to mark — so the next tidy hand wouldn’t lovingly put the splinters back. A gap can be doing work precisely by being empty. The whole craft is in recognising that before you fill it.

A Reflective Question

What in your work feels effortless today because someone, at some point, quietly took an obstacle out of the way — and would you even know if a well-meaning tidy-up put it back tomorrow?