The Corporate Aisle: Why Growth Fails When Systems Are Designed for Departments

What if the most important business problem in a complex system is not a lack of resources, talent, or demand, but the order in which ordinary activities occur?

An airplane can have enough seats, gates, staff, and fuel, yet still board passengers painfully slowly. A healthcare company can grow revenue, membership, and several operating divisions, yet see total operating profit decline. In both cases, the visible activity looks healthy. The hidden system is not.

This points to a powerful and underused idea: performance is often determined less by the strength of individual components than by the friction at their interfaces.

A company may own more of the value chain. An airport may have more employees. A health insurer may add more members. None of these facts guarantees that the system will move faster, serve customers better, or generate more profit. The decisive question is whether the system has been designed to prevent its parts from blocking one another.

The Local Logic That Makes Systems Slow

The conventional way to board a plane appears reasonable. Passengers enter in groups, often by large zones or rows, and each person finds a seat. The method feels orderly because it is easy to explain and easy to administer.

But the apparent order conceals a queueing problem. A passenger sitting at a window seat may need to place a bag in an overhead bin. The passenger behind them must wait in the aisle. That delay propagates backward, even if every person is behaving sensibly. The system is not slowed by walking. It is slowed by interference.

Research and experiments have repeatedly shown that common boarding procedures are among the slowest. Methods that separate passengers by seat position, such as boarding window seats before middle seats and aisle seats, perform better because they reduce the number of people competing for the same narrow workspace. More choreographed approaches improve further by spacing out activities that would otherwise collide.

The lesson is not merely about airplanes. It is about the difference between individual efficiency and system throughput.

Every passenger can be punctual, cooperative, and physically capable. Every employee in a company can work hard. Every business unit can meet its own targets. Yet the overall process can deteriorate if adjacent activities are poorly sequenced.

A system does not move at the speed of its fastest part. It moves at the speed of its most consequential bottleneck.

This is why local improvements often disappoint. Making each passenger board quickly does not solve the problem if passengers repeatedly block one another. Adding more capacity to one department does not solve a problem created by handoffs with another department. Increasing sales does not automatically improve economics if the new business carries higher service costs.

The most dangerous inefficiencies are often invisible in departmental reports because they live between departments.

Growth Can Increase the Cost of Coordination

Consider the operating picture of a large healthcare enterprise. Membership grew in several important categories. Commercial membership rose substantially, while growth in Medicare Advantage and Medicare Supplement membership was much slower. Revenue increased strongly. Prescription services and provider operations also produced higher profit.

At first glance, this is a story of expansion with isolated setbacks. But a more interesting interpretation emerges when the numbers are viewed as a system rather than a collection of divisions.

The company combines insurance, medical care delivery, pharmacy services, data, consulting, and technology. This structure promises coordination. In theory, information can travel across the organization, patient care can become more integrated, and the company can capture value at multiple points in the healthcare chain.

The same structure also creates more interfaces. A claim may touch the insurer, the provider, the pharmacy benefit manager, a data platform, and a technology infrastructure. A payment disruption in one area can create cash flow stress somewhere else. A cyberattack on a transaction network can force the organization to fund providers, absorb emergency expenses, and revise reserve calculations even when the underlying medical demand has not suddenly changed.

This is the corporate equivalent of passengers competing for the same aisle.

The figures reveal the tension. Intercompany revenue eliminations increased significantly, suggesting that more activity was occurring among affiliated businesses. That can indicate growing vertical integration. But it also means that the organization is becoming more internally interdependent. The more tightly connected the parts, the more valuable coordination becomes, and the more expensive a failure at a shared interface can be.

Meanwhile, the loss ratio increased as medical costs consumed a larger share of premium revenue. Several forces contributed, including changes in Medicare funding, business mix, and the consequences of the cyberattack. Operating expenses as a percentage of revenue improved, but total operating profit still declined slightly.

That combination matters. It shows why a falling expense ratio is not the same as improving system economics. One part of the machine became more efficient while another absorbed more pressure. The organization may have optimized administrative spending while the cost of care, funding conditions, and disruption risk overwhelmed those gains.

The airport analogy helps clarify the pattern. Suppose an airline saves money by reducing the number of gate agents, then asks passengers to board more quickly. The labor cost may improve on paper, but congestion at the gate could increase. The savings would be real at the gate and negative for the journey.

Likewise, an enterprise can improve a segment metric while making the total system more fragile. Efficiency is always efficiency relative to a boundary. The relevant boundary is not necessarily the department, product, or quarter. It may be the entire customer journey, the full claims cycle, or the organization’s ability to keep money and information moving during a shock.

The Hidden Tax of Vertical Integration

Vertical integration is often described as a way to capture more margin and reduce dependence on outside partners. Those benefits can be substantial. But integration should not be confused with coordination.

Owning multiple steps in a process gives a company authority over those steps. It does not guarantee that information, incentives, and timing will align across them. In fact, the internal version of a market can sometimes become more complicated than the external one because each unit develops its own goals, systems, language, and performance measures.

Imagine a healthcare organization with four divisions:

1. An insurance unit focused on premium pricing and medical cost control.
2. A provider unit focused on patient visits, staffing, and clinical outcomes.
3. A pharmacy unit focused on prescription volume and drug economics.
4. A technology unit focused on data products, reliability, and contracts.

Each can report strong performance while the patient or payer experiences friction. The insurer may tighten utilization management. The provider may face slower reimbursement. The pharmacy may optimize its formulary. The technology unit may prioritize profitable consulting work over maintaining a critical transaction platform. From inside each unit, the choices may be rational. Across the system, they can create delays, duplicated effort, or distrust.

This is a form of coordination debt. Just as technical debt accumulates when a software system is built quickly without maintaining its underlying structure, coordination debt accumulates when an organization adds products, acquisitions, and internal transactions without redesigning how the parts work together.

Coordination debt has recognizable symptoms:

• Revenue grows, but profit conversion weakens.
• More transactions occur, but customers experience longer resolution times.
• Internal revenue rises, but it becomes difficult to identify where value is actually created.
• One unit’s improvement repeatedly appears as another unit’s cost.
• A disruption in one platform spreads rapidly across unrelated operations.

The decline in data and technology profit is especially revealing in this context. A technology or insights business may look like a discrete profit center, but its true importance can be much larger than its reported earnings. It may function as connective tissue for the rest of the enterprise. When that connective tissue weakens, the effect is not confined to the segment’s income statement.

This is why conventional accounting can miss systemic weakness. Financial statements are excellent at assigning results to legal entities and reporting periods. They are less effective at showing how much value depends on a shared interface, a single data exchange, or a fragile sequence of handoffs.

The Interface Is Where Strategy Becomes Real

Strategy is often discussed in terms of markets, capabilities, and assets. But customers encounter strategy at interfaces.

A passenger encounters an airline at the moment they check in, board, find space for a bag, and settle into a seat. A patient encounters an integrated healthcare company through appointment scheduling, eligibility verification, treatment, prescription fulfillment, and payment. The customer does not experience the organization chart. They experience the transitions.

These transitions determine whether integration feels like convenience or bureaucracy.

A useful mental model is to classify every important process by three questions:

1. Where can work physically or digitally block?

On a plane, the aisle is the obvious constraint. In healthcare, it might be a payment switch, a claims interface, a prior authorization process, or a shared identity system. The bottleneck may not be the busiest component. It is the component whose delay prevents many others from proceeding.

2. Where do incentives conflict?

A department rewarded for reducing its own costs may push work onto another department. An insurer rewarded for lowering claims may create administrative burdens for providers. A technology team rewarded for new sales may underinvest in resilience. These are not character flaws. They are predictable results of measurement design.

3. Where does failure propagate?

Some activities are isolated. Others are hubs. A failure in a peripheral service may be inconvenient. A failure in a shared transaction platform can disrupt thousands of organizations at once. The more central the interface, the more its reliability should be valued, even if it generates modest direct profit.

These questions produce a better diagnostic than simply asking which unit is growing fastest. They reveal whether growth is increasing throughput or merely increasing the number of things that must coordinate.

The boarding problem offers a practical design principle: sequence independent work before shared space becomes scarce. Window passengers can prepare without blocking aisle passengers. In a business, this might mean completing eligibility checks before a clinical encounter, resolving data discrepancies before payment submission, or separating high urgency cases from routine workflows.

Another principle is to reduce unnecessary concurrency. Organizations often assume that doing more things simultaneously is efficient. It is efficient only when the activities do not compete for the same scarce resource. Parallel work can become serial delay when too many tasks converge on one bottleneck.

A Better Way to Read Growth Metrics

Growth metrics are most useful when paired with friction metrics.

Membership, revenue, and profit answer the question: How much activity is occurring? They do not fully answer: How much effort is required to make that activity work?

For a complex enterprise, leaders should track both outputs and the cost of coordination. Useful measures might include:

• Time from a transaction’s initiation to its final resolution.
• Percentage of cases requiring manual intervention.
• Number of handoffs per customer journey.
• Rate of rework, denials, or duplicate submissions.
• Concentration of activity on shared platforms.
• Time required to recover from a system failure.
• Profit after adjusting for disruption, exception handling, and emergency funding.

These measures expose the difference between scale and scalability. Scale means the organization handles more volume. Scalability means it handles more volume without a disproportionate increase in friction.

A company can therefore grow while becoming less scalable. Commercial membership can rise rapidly, revenue can approach a higher level, and affiliated transactions can increase, while the system becomes harder to operate. The warning signal is not necessarily a collapse. It may be a subtle divergence between activity and economics: more volume, higher medical costs, larger disruption exposure, and weaker conversion of revenue into operating profit.

The right question is not whether the enterprise is getting bigger. It is whether each additional unit of growth makes the next unit easier or harder to process.

Key Takeaways

• Map the handoffs, not just the departments. Identify where customers, money, data, or decisions move from one unit to another. Friction usually hides there.
• Measure throughput alongside local efficiency. A lower expense ratio or faster department can coexist with a slower end to end process.
• Find the shared aisle. Locate the scarce resource that many workflows depend on, then redesign the sequence around it.
• Treat resilience as an economic capability. A platform that produces modest direct profit may protect enormous value elsewhere in the organization.
• Distinguish scale from scalability. Ask whether new volume increases coordination costs faster than it increases useful output.

The deeper lesson is that complexity does not become valuable merely because it is owned. Integration creates potential, but only choreography converts that potential into performance.

An airplane does not board efficiently because passengers are individually disciplined. It boards efficiently when the sequence prevents passengers from obstructing one another. A healthcare enterprise does not become more productive simply because insurance, care, pharmacy, and technology sit under one corporate roof. It becomes more productive when those parts exchange information and resources with minimal friction, especially under stress.

The next time a company announces strong growth, look beyond the headline numbers. Ask what has become more connected, which interface now carries more load, and whether the organization has redesigned its sequence for the new scale.

Because in complex systems, the future is rarely decided by the number of parts. It is decided by what happens when those parts meet.