The Hidden Economics of Care: Why the Best Systems Grow by Shrinking the Center

What if the smartest way to scale is to stop centralizing?

Most institutions believe growth works like gravity: pull more people toward the center, add more layers, tighten control, and somehow the whole system becomes stronger. But that instinct often creates the opposite result. The center gets heavier, slower, and more expensive, while the real work happens somewhere else, closer to the edge, where the customer, patient, or client actually lives.

That tension shows up in two very different worlds: healthcare and consulting. In one, a statewide kidney care model tries to improve outcomes by bringing care closer to patients, families, and local physicians. In the other, a global consulting giant cuts support roles and reshapes how its own internal machine is staffed. At first glance, one is about medicine and the other about management. But both are wrestling with the same question:

What does it really mean to create value in a complex system, and how much of the old center can a system afford before it starts consuming itself?

The answer is not just about efficiency. It is about where intelligence lives, how trust is built, and whether scale can remain humane.

---

The old model: more center, more control, more cost

For decades, institutions equated maturity with centralization. If a healthcare system wanted to improve quality, it built more in-house capacity. If a consulting firm wanted to grow, it added more people, more coordinators, more support functions, more process. In both cases, the implicit belief was the same: the center should absorb complexity so the edges can function.

That logic once worked reasonably well. In simpler environments, centralization reduced variation. It created predictable workflows, easier supervision, and stronger standardization. But complexity changes the rules. A patient with chronic kidney disease does not live in a spreadsheet. A consultant managing a client project does not produce value by being surrounded by administrative insulation. In both cases, the work succeeds only when judgment, responsiveness, and context remain close to the action.

This is the first paradox: the more complex the system, the less useful pure centralization becomes. Central control can standardize what is already known, but it struggles to adapt to what is locally true. A patient’s medication adherence may depend less on clinic hours than on transportation, family support, food access, or trust in a physician who has known them for years. Likewise, a firm’s client value may depend less on the size of its back office than on how quickly project teams can make decisions without waiting for layers of coordination.

In both settings, the center starts to behave like a tax. It adds overhead, delay, and distance from reality.

---

The real asset is not scale, it is proximity

The kidney care model points to a different design principle: build capacity in local markets, preserve physician independence, and mobilize community resources around the patient’s actual life. That is a profound shift. It treats care not as something delivered to a passive recipient, but as a network of relationships that must be activated around a person’s daily constraints.

This is where many systems misunderstand value-based care. They think the innovation is mostly financial, as if “value-based” means a clever reimbursement formula. But the deeper innovation is organizational. It recognizes that outcomes improve when the system becomes more intimate, not just more informed.

Think of the difference between a lighthouse and a neighborhood guide. A lighthouse is powerful, but it only shines from one fixed point. A neighborhood guide knows which street is blocked, which family needs help, which neighbor can offer a ride, and which obstacle is invisible from headquarters. Chronic illness often requires the neighborhood guide, not just the lighthouse.

The consulting example reveals a mirror image of the same principle. A large firm can grow revenue while deciding that some functions are now too far from value creation. Support layers that once made sense may become too expensive relative to the speed and judgment they enable. The message is not that overhead is bad in itself. It is that overhead has a shelf life. As a firm scales, the question becomes whether each additional layer improves decision quality or merely reassures the institution that it is in control.

This is the hidden economics of proximity: the closer the system is to the real problem, the less it has to spend trying to simulate understanding from afar.

---

A useful framework: the three distances that destroy value

When institutions become bloated or brittle, they usually suffer from one or more of three distances.

1. Distance from the end user

This is the most obvious distance. In healthcare, it is what happens when care is designed around appointments instead of lives. In professional services, it is what happens when teams become so layered that junior staff or support functions are more accountable to internal process than to client outcomes.

When distance from the end user grows, the organization begins to optimize for what it can measure easily, not what matters most.

2. Distance from local context

Complexity is rarely uniform. One neighborhood, one patient, or one client account can differ dramatically from another. A system that assumes sameness across all contexts will inevitably overstandardize some areas and underserve others.

Local context is not noise. It is often the main variable. A kidney patient may need transportation coordination, family education, medication reminders, and home monitoring, not just another appointment. A consulting team may need a different staffing mix, faster escalation paths, or more senior involvement on a specific account. Without local context, institutions mistake resemblance for relevance.

3. Distance from decision-making

The longer a signal takes to travel upward and a decision takes to travel back down, the less adaptive the system becomes. This is why bureaucracies feel sluggish. Not because people are lazy, but because judgment has to move through too many hands before it can act.

A healthier system compresses this distance. It pushes authority outward and keeps support close enough to help, not so far away that it becomes ceremonial.

Complex systems fail when the people closest to the problem are least empowered to solve it.

That sentence applies just as much to a nephrology practice as it does to a global advisory firm.

---

Independence is not the opposite of coordination

One of the most interesting ideas in the kidney care model is that it preserves physician independence while raising quality and lowering cost. That sounds contradictory only if you believe control and coordination are the same thing.

They are not.

Control means the center dictates. Coordination means the system aligns. Control often suffocates professional judgment because it replaces expertise with compliance. Coordination, by contrast, gives experts the infrastructure to do their best work. The difference is similar to that between a conductor and a dictator. A conductor does not play every instrument. The conductor helps each musician hear the whole composition and enter at the right time.

This matters beyond medicine. In consulting, the healthiest firms do not centralize every decision because centralization makes leaders feel important. They design a system where the right person can make the right call at the right time with enough support to avoid chaos. The best firms are not those with the most hierarchy. They are those with the most reliable coordination without unnecessary friction.

That distinction explains why some organizations become more efficient as they decentralize. They are not giving up discipline. They are removing drag.

---

The future belongs to organizations that can do more with less center

The phrase “doing more with less” usually implies austerity. But there is a better interpretation: do more by concentrating value where it actually happens. That means cutting the distance between expertise and execution, between knowledge and action, between service design and lived experience.

In healthcare, that can mean at-home clinical models, technology-enabled engagement, and deep integration with community resources. It means recognizing that a person with chronic illness is not simply a diagnosis, but a household, a schedule, a set of constraints, and a network of relationships. The best intervention may not be a new policy. It may be a ride, a call, a reminder, or a trusted local clinician.

In consulting, it can mean a leaner internal structure that reserves human attention for client-facing work and reduces the administrative burden surrounding it. Not because support functions are unimportant, but because support functions become counterproductive when they outgrow the work they are supposed to support. The point is not to worship lean operations. It is to prevent the organization from mistaking internal expansion for external value.

This is the central insight: scale should thicken the quality of local relationships, not inflate the machinery above them.

A good test is simple. If you removed one layer of middle management, one administrative queue, or one internal approval step, would the end user notice worse outcomes or better service? If the answer is better service, the layer was not an asset. It was a habit.

---

Key Takeaways

1. Map the distances in your system. Identify where you are farthest from the end user, from local context, and from decision-making. Those are usually the places where value leaks.

2. Treat support as an enabler, not a destination. Support functions should reduce friction for frontline experts, not become a second center of gravity.

3. Decentralize judgment, centralize standards. Let decisions happen close to the work, but keep clear principles, measurement, and accountability.

4. Audit every layer for added value. If a role, process, or approval step does not improve speed, quality, trust, or patient and client experience, it probably deserves scrutiny.

5. Design for context, not just consistency. The best systems know when uniformity helps and when it hides important differences.

---

The deeper lesson: value is created at the edge, not in the empire

It is tempting to think that strong institutions are built by accumulating power at the center. But the most resilient systems often do the opposite. They keep the center light enough to coordinate, not so heavy that it crowds out the work being done at the edges.

That is true in healthcare, where the best care may depend on a neighborhood network more than a distant command structure. It is true in consulting, where a firm can be financially successful and still realize that certain internal layers no longer deserve to exist in their current form. And it is true for almost any organization trying to survive a more complex world.

The old dream of scale was dominance. The new dream should be responsiveness with discipline. Not bigger centers. Smarter peripheries. Not more insulation. More proximity. Not a machine that expands for its own sake, but a living system that knows when to step closer to the person it serves.

In the end, the most advanced institutions may not be the ones with the tallest headquarters. They may be the ones wise enough to shrink the center so the edge can finally do its work.