What Swimming Lessons, Local Heroes, and Hospital Mergers Reveal About Scale

What if the biggest threat to good healthcare is not a lack of expertise, but our habit of moving expertise farther away from the people who need it?

That question appears in unlikely places. It is present in the humble logic of Swimming 101, where survival begins with a few physical fundamentals. It is present in the idea of hometown rock stars, people whose excellence is often more visible and valuable within a community than on a national stage. And it is present in the accelerating consolidation of healthcare, where independent physicians, practices, and hospitals increasingly become parts of larger systems.

These ideas seem unrelated until you notice the common tension: the difference between scale and capability.

Scale promises efficiency, consistency, and access to resources. But capability is often local, embodied, and dependent on relationships. A large system may possess more equipment, more capital, and more formal expertise while becoming less able to notice the particular person standing in front of it. The central danger is not that big organizations are always bad. It is that we confuse organizational size with human competence.

The lesson reaches beyond healthcare. It concerns schools, companies, communities, and our own careers. Whenever a system grows, we must ask what it gains through coordination and what it loses through distance.

The fundamentals are easy to overlook until the water rises

Swimming 101 is not glamorous. It does not begin with complex strokes, elite competition, or advanced equipment. It begins with breathing, buoyancy, body position, and the ability to remain calm in water.

That is the nature of fundamentals: they look obvious when conditions are favorable and become decisive when conditions change. A person who has practiced the basics can recover from an unexpected wave. A person who has only memorized a sophisticated technique may panic when the environment stops cooperating.

Organizations behave in much the same way. During stable periods, a healthcare system can appear impressive because it has specialized departments, elaborate software, centralized purchasing, and a recognizable brand. Yet none of those features guarantees that a patient can get a timely answer, that a physician can exercise judgment, or that a family knows whom to call when something goes wrong.

The basic questions remain stubbornly physical and human:

• Can the patient reach someone who knows the case?
• Can the clinician make a decision without navigating unnecessary layers?
• Can the organization detect a problem before it becomes a crisis?
• Can responsibility be located clearly when many offices and departments are involved?

These are healthcare's equivalent of staying afloat. They are not intellectually dazzling, but they determine whether the system works under pressure.

Consolidation often begins with a reasonable promise: shared infrastructure will improve care. One billing system can replace several. A larger group may negotiate better prices. Specialized services may become available in communities that previously lacked them. Centralization can reduce waste and give clinicians access to resources that a small practice could never afford.

The problem arises when supporting infrastructure becomes the center of gravity. The system starts optimizing for what can be standardized, counted, and controlled. The fundamentals of care, however, are not always easy to standardize. Trust, context, continuity, and judgment are more like swimming than like accounting. They must be practiced by people in real situations.

A system can become more sophisticated while becoming less capable of keeping people afloat.

Why hometown excellence matters

The phrase hometown rock star points toward a form of excellence that conventional rankings often miss. A person may not be famous nationally, yet be indispensable locally. The neighborhood mechanic who diagnoses a strange engine noise in minutes, the teacher who knows exactly when a student is pretending to understand, or the family physician who recognizes a serious problem because a patient is behaving differently than usual: these are forms of expertise rooted in proximity.

Their power comes from more than technical knowledge. It comes from repeated contact with a particular environment.

A local expert accumulates what might be called situated knowledge. They know the recurring patterns, the informal networks, the constraints that official records leave out. They remember that a patient works nights, that a family has resisted a certain treatment before, or that a supposedly minor symptom appeared in a different form six months earlier. This knowledge is difficult to transfer because it is not stored only in a database. It lives in memory, attention, and trust.

Large systems frequently treat this kind of knowledge as anecdotal. It appears inefficient because it cannot be perfectly quantified. But anecdotal does not mean unimportant. In many complex environments, the most valuable information is precisely what has not yet been converted into a metric.

Consider two clinics. The first is part of a large network. It has extensive protocols, centralized scheduling, and a sophisticated patient portal. The second is independent, with fewer resources but a physician who has cared for several generations of local families. If the second physician notices that a patient is unusually quiet, connects a vague complaint to a previous episode, and calls the patient's daughter because something feels wrong, that intervention may never appear in a performance dashboard. Yet it may be the most consequential act of care that day.

This is not an argument for romanticizing small organizations. Local institutions can be poorly managed, technologically outdated, or overly dependent on one person. A hometown rock star can become a bottleneck. Familiarity can produce blind spots as easily as insight.

The more precise point is that local excellence is a strategic asset, not merely a charming exception. A good system should preserve and amplify it rather than assume that absorption is the only path to improvement.

The hidden cost of consolidation is not size, but distance

People often debate consolidation as if the central question were whether a larger organization is more efficient. That is too narrow. The deeper question is: efficient for whom, and at what distance from the actual work?

When a physician practice joins a hospital system, some benefits may be real. The practice may gain capital, negotiating power, compliance support, and access to specialists. But it may also gain additional approval layers, productivity targets, standardized appointment structures, and incentives designed at headquarters rather than in the exam room.

The effects are rarely immediate or dramatic. That is what makes them difficult to see. A familiar physician does not suddenly become incompetent. Instead, the time available for an appointment becomes slightly shorter. A nurse spends more time on documentation. A referral travels through one more administrative channel. A patient sees a different clinician because scheduling is optimized across a network. Each change may look minor. Together, they alter the texture of care.

We can understand this through a simple model:

Net capability equals resources multiplied by judgment, divided by distance.

Resources include money, technology, staffing, data, and specialized equipment. Judgment is the capacity to interpret circumstances and act appropriately. Distance includes organizational layers, physical separation, administrative friction, and the weakening of personal relationships.

A larger system may dramatically increase resources. But if it also increases distance and constrains judgment, the final result may not improve. In some situations, it may worsen.

This explains why consolidation can produce contradictory experiences. An organization may be financially stronger and operationally more frustrating. It may offer more services while making it harder to reach a person who can make a decision. It may have better data while paying less attention to what the data does not contain.

The chart that shows growing concentration in healthcare should therefore be read as more than an ownership diagram. It is also a map of where decisions are made. When more practices belong to fewer systems, the question is not simply who owns the buildings. It is who controls prices, staffing, referrals, schedules, treatment protocols, and the definition of acceptable performance.

Ownership matters because it changes the feedback loop. In a small practice, a dissatisfied patient may speak directly to the physician who made the decision. In a large system, the complaint may enter a survey, become a data point, and disappear into a reporting process. Scale can create accountability in theory while weakening accountability in lived experience.

The real alternative is not small versus large

The usual debate sets up a false choice. It assumes that we must choose between fragmented local care and centralized institutional power. But the better design is neither pure independence nor total absorption. It is federated capability.

A federated system shares what benefits from scale while protecting what depends on proximity. It centralizes back office functions, purchasing, cybersecurity, specialized expertise, and emergency capacity. At the same time, it leaves clinical relationships, local decision making, and team culture close to the patient.

Think of a swimming instructor. A national organization might provide training standards, safety equipment, and emergency procedures. But the instructor still needs enough discretion to adapt to the individual in the pool. One student is afraid of the deep end. Another understands the theory but cannot coordinate breathing. A third has a medical condition that changes the lesson. Standardization can make instruction safer, but only judgment makes it useful.

The same principle applies to healthcare. Good systems should standardize the conditions for excellence, not every expression of excellence.

This produces a practical design rule: centralize commodities, decentralize judgment.

Commodities are the things that can be reliably shared without erasing context. They include payroll, procurement, legal support, data security, and certain forms of technology. Judgment includes diagnosis, communication, prioritization, relationship management, and decisions that depend on local knowledge.

The distinction is not perfect. Some clinical protocols save lives precisely because they are standardized. Some local practices should be challenged. The point is to identify which elements require uniformity and which require discretion, rather than allowing organizational convenience to decide by default.

A second design rule follows: measure the strength of feedback loops, not just the size of the network.

Ask how quickly a frontline observation reaches someone with authority. Ask whether a physician can change a process without waiting months for approval. Ask whether patients can identify the person responsible for their care. Ask whether performance measures include continuity, access, and trust, or only volume and revenue.

A system with fewer locations may provide better care if its learning loops are short. A system with hundreds of facilities may underperform if information becomes distorted as it travels upward. In complex work, the speed and fidelity of feedback often matter more than the number of resources available.

What individuals and leaders can do now

The broad structure of healthcare cannot be changed by one patient or one manager. But the principles of local capability can be applied immediately, whether you are choosing a doctor, running a team, or designing an institution.

Key Takeaways

1. Master the basics before adding complexity. In healthcare, begin with access, continuity, clear responsibility, and timely communication. In any organization, identify the equivalent of staying afloat before investing in advanced systems.

2. Protect local knowledge as an asset. Ask who understands the particular community, customer, classroom, or patient population. Do not assume that information becomes more valuable merely because it has been centralized.

3. Separate scale from control. Shared infrastructure can be useful without requiring every decision to pass through a central authority. Centralize support functions and preserve frontline judgment wherever context matters.

4. Audit distance. Count the steps between a problem and a decision maker. Look for extra approvals, disconnected departments, rotating contacts, and metrics that replace conversation. Every layer adds potential friction.

5. Reward hometown rock stars. Identify the people whose expertise is locally trusted and give them influence, resources, and succession plans. Do not force them to leave the work they understand in order to earn recognition.

The deepest lesson is not that big systems are inherently dangerous or small ones inherently virtuous. It is that human capability has a geography. It grows through repeated encounters with real people in real places. When institutions expand, they must deliberately preserve the proximity that produced their best judgment in the first place.

A hospital system can own more clinics and still know less about its patients. A company can collect more data and understand less about its customers. A school district can adopt more programs and notice less about the child who is quietly falling behind.

The question to ask whenever an institution becomes larger is not simply, "What efficiencies will we gain?" It is also, "What forms of attention will become harder?"

Swimming 101 teaches that survival depends on fundamentals. Hometown excellence teaches that mastery often belongs to people who are close enough to notice. Healthcare consolidation forces us to confront what happens when those two truths are separated from the decisions that matter.

The future of effective institutions will not belong automatically to the largest players. It will belong to those that learn how to make scale serve proximity, rather than consume it.