The Hidden Value of Friction: Why Smart Systems Need Fewer Gates, Not More

Apr 19, 2026

10 min read

4 views

34%

What if the problem is not the line, but the room?

Most people think bureaucracy is a matter of paperwork. But the deeper issue is not the form, the fax, or the checkbox. It is the moment a system decides that trust must be replaced with permission. That decision creates a gate, and every gate changes behavior. Some gates protect value. Many simply slow down motion, increase anxiety, and make ordinary activity feel like trespassing.

That tension becomes especially visible in healthcare, where prior authorization is often defended as a way to protect premium dollars, limit waste, and ensure that the right care happens at the right time and place. Those are real goals. Yet the same mechanism can also turn care into a waiting game, transforming a clinical decision into an administrative negotiation. The real question is not whether controls are good or bad. It is whether the control is adding value, or merely converting speed into friction.

Now imagine a very different setting: a hotel lobby. Not a sterile checkpoint, but a designed threshold. You are not asked to justify your existence at the door. You are guided, oriented, and moved toward an experience. The best hotels do not eliminate boundaries, but they make transitions feel intentional rather than punitive. That contrast reveals something important about systems: good friction is legible, proportionate, and in service of the guest or patient. Bad friction is opaque, repetitive, and in service of the institution’s fear.

The real issue is not control versus freedom

The usual debate around administrative review gets trapped in a false binary. One side wants fewer restrictions. The other fears runaway cost and misuse. But the deeper tension is not control versus freedom. It is blanket suspicion versus calibrated trust.

Every system needs some way to distinguish ordinary cases from exceptional ones. A hotel does not treat every arrival as if it were a security threat, but it does still have a front desk, room keys, and a reservation system. Healthcare is similar. Not every request should go automatically through an expensive review. But not every request should be instantly approved either. The challenge is designing a system that reserves its attention for the cases where attention actually changes outcomes.

That is why the idea of moving toward zero is so powerful. It does not mean abolishing every review mechanism. It means shrinking prior authorization until it becomes a rare exception rather than a routine obstacle. In other words, the ideal is not no structure. It is near zero unnecessary structure.

This distinction matters because humans are not just inconvenienced by delay. They are morally affected by it. A patient waiting for approval hears a quiet institutional message: your care must first survive our process. That message may be economically rational, but it is psychologically corrosive. Over time, repeated friction teaches people to plan around the system instead of with it.

The best systems do not ask people to prove they deserve access every time. They make the right path the default, and reserve scrutiny for the edge cases that truly need it.

A hotel is not healthcare, but it teaches a useful design principle

At first glance, a luxury hotel and a health plan could not be more different. One sells comfort. The other manages risk. One wants delight. The other wants accountability. Yet both are in the business of orchestrating trust under constraints.

A well run hotel understands that the guest experience is not just the room. It is the sequence: arrival, check in, key handoff, orientation, response to needs. If any of those steps becomes confusing or adversarial, the stay feels smaller than it should. The point is not that the hotel has no rules. The point is that its rules are mostly invisible until they are needed.

That is a valuable model for healthcare administration. Think about the difference between a system that requires prior approval for nearly everything and one that relies on preapproved pathways for common, evidence based care. In the first system, every encounter feels like a customs inspection. In the second, clinicians operate inside an environment of broad trust, with targeted review only where variation is costly or dangerous.

This is not just about convenience. It changes the economics of attention. Administrative energy is a finite resource. When it is spent reviewing low risk, high frequency cases, it is unavailable for complex decisions, genuinely questionable claims, and patient support. A system that overuses gates ends up blind where it most needs insight.

A hotel does not waste staff time asking each guest to re explain why they booked a room. It uses reservation systems, standards, and predictable service patterns. Healthcare can learn from that. When most cases follow known paths, the system should behave as if it believes its own standards.

Prior authorization becomes harmful when it confuses probability with certainty

One of the quietest failures in administrative systems is overgeneralization. A process designed for rare exceptions spreads to ordinary cases because someone once needed protection from abuse. Soon, what started as a safeguard becomes a default checkpoint. The system says, in effect, because some requests are inappropriate, all requests must be slowed.

That logic sounds prudent, but it is often mathematically sloppy. A control makes sense when the expected benefit exceeds the expected burden. But when the burden is imposed on thousands of routine cases to catch a handful of problematic ones, the system has probably crossed the line from governance into drag.

Healthcare illustrates this vividly. A patient with a well established treatment plan should not face the same burden as a request for an expensive, ambiguous, or new intervention with limited evidence. Yet in many systems, the administrative treatment of these cases converges. The result is not smarter oversight. It is non selective skepticism.

This is where the phrase moving toward zero becomes more than a slogan. It becomes a design ethic. Every step in that direction should ask three questions:

Does this review prevent meaningful harm or waste?
Is the review targeted enough to justify its delay and effort?
Could the same goal be met by a clearer rule, better data, or a value based agreement?

If the answer to the first question is weak, and the answer to the second is weak, the process is probably defending its own existence rather than serving care.

A hotel would not keep a guest in the lobby while multiple departments debate whether the room is really needed, unless there were a genuine reason to do so. That seems obvious. Yet many institutional systems behave as if delay itself were proof of seriousness. In reality, delay is only valuable when it reduces error more than it increases harm.

The best friction is invisible until it matters

The phrase prior authorization usually evokes the visible parts of bureaucracy: forms, delays, appeals. But the more interesting question is what kind of friction actually improves a system.

There is a useful distinction between friction as a filter and friction as a barrier. A filter improves quality by letting the right things through and stopping the wrong ones. A barrier simply makes passage harder. The problem is that many institutions cannot tell the difference because they measure the barrier, not the outcomes.

In healthcare, this means the right goal is not to maximize the number of approvals denied or to minimize administrative work at any cost. It is to improve value: better care, less waste, less harm, appropriate spending. If prior review helps a system move toward those ends, it has a role. If it does not, it should shrink.

Here is a simple way to think about it:

Good friction is rare, specific, explainable, and reversible.
Bad friction is frequent, broad, confusing, and sticky.

Good friction might be a targeted review for a high cost drug with uncertain evidence, especially when cheaper effective alternatives exist. Bad friction is making a clinician repeatedly justify the same stable therapy for the same patient, month after month, as though the system has forgotten the rationale it already accepted.

This is where value based arrangements matter. When health plans and providers share the same objective, the process can shift from adversarial checking to collaborative stewardship. In that environment, prior authorization becomes less like a toll booth and more like a quality assurance tool. The difference is not semantic. It is structural. Shared incentives reduce the need for suspicion.

Systems behave better when they are designed around shared truth instead of repeated proof.

The path to zero is really a path to maturity

The phrase moving toward zero sounds reductive, as if the goal were simply to eliminate a process. But the deeper meaning is developmental. Mature systems do not rely on heavy handed interventions for routine behavior. They encode standards so well that intervention becomes exceptional.

Think about how a polished hotel runs. The guest does not feel the full machinery of operations, but the machinery is there: reservations, housekeeping, maintenance, billing, staffing. The experience feels effortless because complexity has been organized behind the scenes. That is what mature administrative design looks like. It does not eliminate structure. It internalizes structure so the user does not carry its weight.

Healthcare can do something similar by moving toward three design shifts:

From individual gatekeeping to standardized pathways
From repeated manual review to data driven exception handling
From adversarial oversight to aligned accountability

This is not utopian. It is operational. Systems that trust routine care more and reserve scrutiny for anomalies can spend more effort on the patients who need help navigating complexity. They can also reduce burnout among clinicians, who often spend as much energy negotiating the system as treating the patient.

There is also a deeper cultural effect. The more a system relies on authorization, the more it trains everyone to expect mistrust. Clinicians learn to document defensively. Patients learn to brace for denial. Administrators learn to optimize through exceptions rather than improvement. Over time, the whole system becomes less like a care network and more like a contest of endurance.

Moving toward zero is therefore not just an efficiency project. It is a culture change. It says that the default relationship between institutions and professionals should be one of informed trust, not routine suspicion. And when suspicion is necessary, it should be precise enough to justify itself.

Key Takeaways

Do not confuse controls with value. A process is only worth its burden if it meaningfully improves care, reduces waste, or prevents harm.
Design for exceptions, not averages. Routine cases should flow through standard pathways, while unusual cases receive targeted review.
Ask whether friction is a filter or a barrier. Filters improve decisions. Barriers merely slow them down.
Use shared incentives to reduce policing. When payers and providers share goals, oversight can become lighter, smarter, and less adversarial.
Treat administrative simplicity as a feature, not a luxury. The easier the right path is to follow, the more likely it is that the system will deliver real value.

The most humane systems are the least suspicious by default

The deeper lesson here reaches beyond healthcare. Any institution that serves people eventually faces the temptation to add one more gate, one more approval step, one more proof requirement. Each addition feels small and responsible in isolation. But over time, the accumulation of small defenses becomes a machine that makes ordinary life harder than it should be.

That is why the idea of moving toward zero matters so much. It is a reminder that the highest form of control is not constant intervention. It is a well designed environment where intervention is rare because the system already knows what good looks like.

A hotel that makes arrival feel seamless is not being lax. It is being competent. A healthcare system that reduces prior authorization to the smallest necessary footprint is not surrendering oversight. It is concentrating oversight where it actually matters.

So the real question is not whether we should have gates. We should. The question is what kind of relationship a gate creates. Does it say, welcome, you are expected here, and we will help if needed? Or does it say, prove yourself again? The future of better systems depends on choosing the first message as often as possible, and making the second one the exception.