The Hidden Business Model of Friction: Why Sludge Is Not a Bug, but a Rationing System

What if the frustration is the product?

Most people think of bad forms, long lines, confusing websites, and endless phone trees as evidence that an organization is failing. But what if those painful experiences are not failures at all? What if they are the mechanism by which a system quietly decides who gets access, who gives up, and who pays more than they intended?

That is the uncomfortable truth at the center of modern service design, especially in healthcare and subscription businesses. Sludge is not just incompetence. Sometimes it is deliberate friction. Sometimes it is accidental friction that has the same effect. And in both cases, the outcome is the same: people make worse decisions, spend more time, and often receive less of what they thought they were buying.

The deeper question is not whether sludge exists. It is this: when a system cannot ration with price, how else does it ration? The answer, increasingly, is with complexity.

---

When price fails, friction takes over

In a normal market, rationing is blunt and legible. A product costs $65, you either buy it or you do not. But healthcare breaks that logic. Insurance, subsidies, employer benefits, and social expectations all combine to create a world where the person making the decision is rarely the person paying the full cost. That means price cannot do the work of sorting demand.

So systems invent substitutes. They use prior authorization, narrow networks, opaque deductible rules, provider directories that are out of date, and reimbursement processes that seem designed by committee and forgotten by Friday. In other words, when the market cannot say no with price, it says no with process.

This is why the same pattern shows up in so many places. A subscription service that takes 30 seconds to join and 20 minutes plus a phone call to leave is not merely clumsy. It is a small private rationing system. A healthcare website that lists 25 specialists but leaves you to discover that none are available is not just an outdated database. It is a filter. A DMV office where appointments and walk-ins collapse into one line is not just inefficient. It is a machine that turns time into a barrier.

Friction is often a hidden price.

If you cannot charge people enough to discourage demand, you can always charge them in time, effort, confusion, or humiliation.

This is why sludge is such a revealing concept. It exposes the fact that many institutions do not actually want to maximize ease. They want to control flow. They want fewer claims, fewer cancellations, fewer visits, fewer inquiries, fewer surprises. And if the experience becomes miserable in the process, that is often treated as an acceptable externality.

---

The two faces of sludge: incompetence and intent

It is tempting to divide sludge into two neat categories: the stuff nobody meant to create, and the stuff designed to trap you. But that distinction is often less useful than it seems, because the effect can be the same even when the motives differ.

Some sludge is pure design failure. The classic bad door handle, the kind that looks like a pull but must be pushed, is a tiny daily humiliation. Nobody is necessarily trying to trick you. They simply failed to think from the user’s perspective. Yet the result is identical to intentional obstruction: wasted motion, irritation, and a learned distrust of the environment.

Other sludge is unmistakably strategic. The unsubscribe trap is the clearest example. Joining is easy because acquisition matters. Leaving is hard because retention matters. The company knows what it is doing, because it lives in a market where every canceled subscription is lost revenue. The same pattern appears when a gym makes you come in to cancel during lockdown, or when a service routes you through a maze of automated menus before a human can do what you asked for in the first place.

But here is the more interesting point: intent and incompetence often coexist. A clunky insurance portal may not have been built to punish patients, but once it exists, it functions like punishment. A disorganized provider directory may not be a conspiracy, but it still reduces utilization. In practice, the user does not experience the internal distinction. They experience the barrier.

That is why the most useful question is not always, “Was this deliberate?” It is, “What behavior does this system reliably produce?” If the answer is fewer claims, fewer calls, fewer reimbursements, or fewer cancellations, then the sludge is doing economic work whether or not anyone admits it.

---

The paradox of healthcare sludge: bad experience, lower spending

Healthcare is where this logic becomes most consequential. We usually talk about access as if it were the main problem. But access is inseparable from cost control. If a system tries to make care free at the point of use, someone must decide what gets covered, when, and under what conditions. If that decision is not made through price, it is made elsewhere.

In the U.S., that elsewhere is often a tangle of insurer rules, network constraints, deductibles, and prior authorization requirements. It is messy, fragmented, and often infuriating. Yet from the standpoint of a payer or insurer, it may also be effective. If a process discourages utilization, spending goes down. That is not a side effect. That is the point.

This creates a deeply uncomfortable moral puzzle. A system can be both wasteful and cost-controlling. It can impose absurd transaction costs while still suppressing total spending. It can frustrate patients and still protect the balance sheet. In fact, one reason healthcare sludge persists is that it is rarely visible in one ledger. The cost appears in patient time, provider labor, delayed care, and administrative overhead, while the savings appear in reduced claims or deferred treatment.

That is why sludge is such a dangerous form of rationing. It hides the policy choice inside the user experience. Instead of saying, “We will not cover this,” the system says, “Please complete these forms, verify these codes, call this number, and try again tomorrow.” The rationing has been outsourced to friction.

There is a more organized version of this in national health systems. In places with centralized decision making, the rationing is often more legible. You wait in line. A body like NICE evaluates cost effectiveness. The system may still deny or delay care, but at least the mechanism is clear.

The U.S. version is more chaotic. It is not always more brutal, but it is more disorienting. Instead of one visible gate, there are fifty overlapping gates, each with its own key, its own clerk, and its own memory problem. The result is not just delay. It is cognitive exhaustion.

---

Why the best companies try to remove friction, while others profit from it

If sludge is a hidden rationing system, then the opposite is a design philosophy: make the right thing easy.

That is why Amazon feels almost unnervingly seamless. It does not make you think about your purchase more than necessary. It reduces the number of decisions between desire and completion. In retail and consumer software, this is often the winning strategy, because ease increases conversion and clear pricing increases trust.

But healthcare companies operate in a paradoxical environment. They are asked to behave like consumer products, but they are built inside systems that benefit from opacity. That is why the most interesting healthcare businesses often start with a different question: not “How do we make the organization look efficient?” but “How do we remove enough friction for users to feel the value directly, while still proving value to the institution that pays?”

This is where B2C2B becomes more than a business model. It becomes a way of escaping sludge without ignoring the realities that create it.

A consumer may download a product because it feels useful, simple, and immediate. But an employer, payer, or hospital system will not pay merely because the app is pleasant. They need proof. They need a story about reduced waste, lower risk, better outcomes, or improved revenue. They need to see that the product does not just delight users, but changes system behavior.

The best modern healthcare products understand this double audience. They create real utility for the individual and then translate that utility into enterprise language: cost savings, clinical outcomes, risk reduction, utilization management. In other words, they do not choose between experience and economics. They connect them.

The most durable healthcare products solve two markets at once: the patient’s need for ease and the system’s need for control.

This is why storytelling matters so much in enterprise sales. People inside institutions are not pure calculators. They buy with their hearts and rationalize with their spreadsheets. A strong ROI helps, but so does a coherent narrative about why the product fits the institution’s priorities. If the story is too fantastical, the numbers lose credibility. If the numbers are solid but the story is absent, the product feels abstract and hard to champion.

There is a sweet spot: a claim that is credible, measurable, and emotionally legible. Not 300 percent ROI fantasy. More like, “This pays for itself, reduces a problem everyone recognizes, and gives us a cleaner way to operate.” That is the language of trust.

---

The real lesson: friction is a product decision, not just a UX issue

The most valuable insight from sludge is that friction is not merely a usability problem. It is a strategic choice about who bears the burden of complexity.

If a company makes sign-up instant but cancellation torturous, it has chosen to concentrate pain at the exit. If an insurer offers broad coverage but hides the rules in a maze of exceptions, it has chosen to concentrate pain at the moment of need. If a medtech company cannot rely on conventional sales cycles and instead builds demand through consumers or clinicians first, it is choosing a different path around institutional friction. In every case, someone is paying the transaction cost, even if no cash changes hands at that moment.

This suggests a useful framework: ask of any system, where does the complexity go?

1. To the user: time, confusion, cancellation barriers, documentation, waiting.
2. To the institution: operational overhead, slower sales, more support, higher service costs.
3. To the marketplace: hidden fees, reduced comparison shopping, distorted demand.
4. To society: delayed care, lower trust, inequitable access, and administrative bloat.

Most systems do not eliminate complexity. They merely relocate it. The ethical question is who gets stuck carrying it.

This is also why product-led growth is harder than it sounds. It is easy to say, “Just make something simple and let users adopt it.” It is much harder to build a product so genuinely useful that people keep using it, recommend it, and force institutions to take notice. Especially in healthcare, where the product may need to satisfy the patient, the clinician, the payer, and the procurement team, all while fitting into a regulatory and financial maze.

The companies that succeed tend to do three things at once:

• Create unmistakable value for the end user
• Generate hard evidence of system-level impact
• Design a path from individual adoption to institutional approval

That is not just a go-to-market strategy. It is a theory of how to move through sludge without becoming sludge.

---

Key Takeaways

1. Treat friction as a signal. When a process is unusually hard, ask what behavior it is preventing. Often, the barrier is the real policy.

2. Look for hidden rationing. If price is not limiting demand, time, effort, and confusion may be doing the rationing instead.

3. Separate accidental clutter from strategic complexity, but do not overfocus on intent. Whether sludge was designed or inherited, the user experiences it as a cost.

4. Build products that solve both experience and economics. In healthcare especially, ease for the user and ROI for the buyer must be linked, not traded off.

5. Ask where complexity ends up. Every system relocates friction somewhere. The better question is who pays for it, and whether that is acceptable.

---

Conclusion: the systems that feel worst may be the ones doing the most invisible work

We usually assume that good systems feel smooth and bad systems feel painful. That is only partly true. Some of the most painful systems are not broken at all. They are functioning exactly as designed, just not for the person standing in front of them.

That is the real lesson of sludge. It reveals that modern institutions often govern not by saying no directly, but by making yes exhausting. And once you see that, you start noticing it everywhere: in cancellations, in insurance, in provider directories, in reimbursement, in pricing, in procurement, even in the quiet little hoops that separate intent from action.

The next time a process feels bizarrely difficult, do not ask only whether it is inefficient. Ask what it is protecting, what it is deterring, and what hidden price you are being asked to pay.

Because in a world where price can no longer do the rationing, friction has become one of our most powerful, least honest forms of control.