The Hidden Cost of Becoming More Than You Are

Ben H.

Hatched by Ben H.

Aug 18, 2026

10 min read

91%

0

What do a collapsing pharmacy empire and a shrinking teacher pipeline have in common? At first glance, almost nothing. One is a corporate balance sheet problem, the other is a workforce and education problem. Yet both reveal the same institutional failure: organizations often lose their core strength while pursuing a larger identity.

A pharmacy chain expands into clinics, primary care, and vertically integrated healthcare. A teaching organization scales a compelling national mission by recruiting temporary, highly motivated outsiders into classrooms. In both cases, growth initially looks like evidence of relevance. Later, the institution discovers that its new perimeter is more expensive, more fragile, and more dependent on conditions it does not control than its original model.

The deeper question is not why large organizations fail. It is this: How can an institution become more ambitious without becoming less capable?

The answer requires distinguishing between growth that compounds an institution's strengths and growth that merely increases its surface area. That distinction matters not only to executives and nonprofit leaders, but also to anyone deciding whether to add a new responsibility, platform, service, or identity to an already overloaded system.

Growth Can Hide a Loss of Capacity

The most seductive kind of growth is expansion into an adjacent category. A retailer adds healthcare services. A nonprofit broadens its geographic reach. A school system introduces another initiative. The move seems rational because the new activity is related to the old one.

But related is not the same as compatible.

A pharmacy chain may possess locations, purchasing power, brand recognition, and customer traffic. Those assets can make a move into clinical care appear natural. Yet operating clinics requires a different set of capabilities: recruiting clinicians, managing patient panels, coordinating care, navigating reimbursement, and maintaining quality over time. The fact that customers already visit a store does not mean the organization knows how to deliver primary care.

Likewise, an organization that can recruit talented college graduates and inspire them with a public purpose may be able to place teachers quickly. That does not mean it can solve the deeper labor market problems of teaching: compensation, working conditions, professional development, retention, and the social status of the profession.

In both settings, an existing asset is mistaken for a transferable capability.

A useful distinction is between stored capacity and borrowed momentum. Stored capacity is what an institution can reliably do because its systems, people, incentives, and culture support it. Borrowed momentum comes from favorable conditions: investor enthusiasm, public excitement, a charismatic mission, a temporary labor surplus, or the willingness of highly motivated people to compensate for weak infrastructure.

Borrowed momentum can produce impressive numbers. It can also conceal that the underlying machine is becoming weaker.

Growth is not proof that an institution is getting stronger. Sometimes it is proof that the institution has found more ways to spend strength it no longer has.

This is why revenue, enrollment, placements, store count, or program count can become misleading measures. They describe the size of the institution's footprint. They do not necessarily describe its ability to deliver excellent outcomes repeatedly, at reasonable cost, without extraordinary heroics.

The pharmacy chain's expansion into healthcare illustrates the danger of accumulating complexity faster than competence. The teacher pipeline illustrates a related danger: treating the arrival of new participants as a substitute for improving the conditions that make participation sustainable. One institution carries too many assets. The other struggles to replenish the people required to carry its mission.

The Adjacency Trap

Every organization has a capability neighborhood: a set of activities close enough to its core that existing skills genuinely help. The trouble begins at the edge of that neighborhood, where superficial similarities mask different operating realities.

Consider three layers of adjacency.

The first is customer adjacency. The same person or institution buys both offerings. A pharmacy customer may need a doctor. A school needs teachers, and a nonprofit serving schools may recruit them. Customer adjacency is useful, but it is the weakest form of strategic fit.

The second is workflow adjacency. The organization uses similar processes, technology, and expertise to deliver both offerings. A pharmacy's dispensing workflow may support medication management, for example. But a clinic's work involves diagnosis, continuity, and clinical judgment, which are not simply extensions of filling prescriptions.

The third is institutional adjacency. The new activity fits the organization's incentives, culture, accountability structure, and time horizon. This is the most important layer and the easiest to ignore.

Healthcare delivery is judged through outcomes that may unfold over years, while retail operations often emphasize traffic, transactions, and quarterly performance. Teaching depends on trust, preparation, and continuity, while recruitment programs may be structured around annual cohorts and short service commitments. The apparent adjacency is real at the level of mission or customer contact, but weak at the level where success is actually produced.

This creates what might be called the adjacency trap: an organization expands because the new activity looks close from a distance, then discovers that the last mile contains an entirely different profession.

The trap becomes especially powerful when leaders use the language of integration. Integration sounds efficient. If one organization controls more of the chain, perhaps it can remove friction, capture more value, and coordinate the experience. Sometimes that works. But vertical integration also means the organization inherits every difficult function it previously purchased, partnered for, or avoided.

The strategic question is therefore not, “Can we enter this market?” It is, “Which burdens become ours if we do?”

For the pharmacy chain, the burden may include clinician labor, unprofitable locations, regulatory complexity, and the challenge of managing care rather than transactions. For the teacher pipeline, the burden includes the gap between recruiting someone into the classroom and keeping that person there. The first problem appears as an asset load. The second appears as a replenishment problem. Both are forms of unpriced complexity.

The Institution's Real Product Is Continuity

Organizations often describe their product as a service, a platform, or a mission. But for institutions, the deeper product is frequently continuity: the ability to provide a dependable result after the founding team, the first wave of enthusiasm, or the favorable market cycle has passed.

A clinic is not merely a room, a brand, and a roster of clinicians. It is continuity of care. A school is not merely a building with an adult in front of a class. It is continuity of instruction, relationships, routines, and accumulated professional knowledge.

This perspective changes how we evaluate success. A program that places many people for one year may look effective. A program that creates a stable, experienced teaching workforce may be doing something more durable, even if its annual placement numbers are lower. A corporation that owns many healthcare assets may look strategically sophisticated. A corporation that can operate a smaller network profitably, with reliable quality and manageable complexity, may be stronger.

Continuity is difficult because it depends on boring infrastructure. It requires supervision, training, middle management, realistic workloads, credible career paths, and feedback systems. These investments rarely create a dramatic launch story. They do not photograph as well as a new clinic, a national expansion, or a record cohort. Yet they are what convert temporary effort into institutional capability.

The decline in teacher preparation enrollment adds another layer to the problem. When fewer people enter the pipeline, institutions cannot solve the shortage simply by recruiting harder at the end. A pipeline is a sequence, not a faucet. If preparation, compensation, working conditions, and professional status deteriorate upstream, downstream recruitment becomes increasingly expensive and less reliable.

The same logic applies to business assets. A company can acquire locations, brands, and services quickly, but it cannot acquire organizational fluency at the same speed. Fluency develops through repeated practice, stable teams, and lessons that remain inside the institution. Buying the visible components of a capability does not guarantee possession of the capability itself.

This is why a shrinking teacher pipeline and a distressed healthcare empire belong in the same conversation. Each shows what happens when the visible output is managed separately from the conditions that reproduce it.

A Better Test for Ambition

Before expanding, leaders should run a capacity audit rather than a market analysis alone. The audit asks four questions.

1. What is the bottleneck we are actually solving?

Organizations often expand around a symptom. A retailer sees that customers want more healthcare and builds clinics. A school system sees unfilled classrooms and intensifies recruitment. But the true bottleneck may be clinician retention, teacher working conditions, administrative overload, or weak professional pathways.

Expansion that does not relieve the bottleneck can make the system look busier while making it less healthy.

2. Which capabilities are genuinely transferable?

List the skills required by the new activity, then mark which ones already exist in depth. Not merely in one executive, one pilot team, or one unusually committed cohort, but across the organization.

A capability is real when an ordinary team can perform it under ordinary conditions. If success depends on exceptional people working unsustainable hours, the organization has a heroic exception, not a scalable capability.

3. What kind of complexity are we adding?

Complexity has at least three forms. Operational complexity adds more processes and handoffs. Cognitive complexity requires people to make different kinds of judgments. Accountability complexity introduces new stakeholders, standards, and time horizons.

A new service may appear operationally simple while radically increasing accountability complexity. A new program may use familiar technology while requiring an entirely different professional culture. Leaders should price all three forms before calling an initiative synergistic.

4. What must be true for continuity?

Imagine the organization five years after launch. Who remains? Who trains newcomers? What happens when funding tightens, enthusiasm fades, or a key leader leaves? How are quality problems detected? What makes a competent person want to stay?

These questions force a shift from launch thinking to maintenance thinking. Most institutional failures are not caused by an inability to begin. They are caused by an inability to keep going without consuming the system's reserves.

A practical rule follows: Do not scale an activity until you can explain how it will reproduce its own competence. If every new unit requires fresh heroics from outside recruits, expensive acquisitions, or constant executive attention, the model is not yet ready for scale.

Key Takeaways

  • Separate adjacency from capability. Shared customers or a shared mission do not prove that two activities belong under one operating model. Identify the specialized skills, incentives, and time horizons the new work requires.

  • Measure continuity, not just throughput. Track retention, repeat quality, experienced staff, and cost to maintain performance. A large annual output can coexist with a weakening institution.

  • Find the bottleneck before adding capacity. More clinics do not automatically solve access. More recruitment does not automatically solve teacher shortages. Diagnose the constraint that prevents the system from renewing itself.

  • Treat complexity as a liability that must earn its keep. Every new service, stakeholder, and workflow consumes management attention. Demand a clear explanation of what value the added complexity creates and how it will be governed.

  • Pilot for ordinary conditions. A successful experiment powered by exceptional leaders or unusually devoted participants is not evidence of scalability. Test whether a normal team can deliver the result at a sustainable pace.

The Question Leaders Should Ask Before They Grow

The usual growth question is, “How large can this become?” It invites forecasts, market maps, and optimistic assumptions. A more revealing question is, “What will this organization have to become in order to sustain that size?”

That question exposes the hidden transformation inside every expansion. A pharmacy chain entering healthcare is not simply adding clinics. It is becoming a clinical organization. A recruitment program sending people into schools is not simply filling vacancies. It is participating in the formation, support, and renewal of a profession.

If an institution does not consciously build the identity and infrastructure required by its new responsibilities, it may end up with the worst of both worlds: the cost structure of a larger organization and the capabilities of a smaller one.

The lesson is not to remain small or to reject ambition. It is to understand that scale is a promise of dependable repetition. Growth that cannot reproduce competence is only expansion of exposure. Growth that strengthens the conditions of continuity, by contrast, creates something more valuable than size: an institution capable of outlasting the enthusiasm that first made it possible.

Sources

← Back to Library

Hatch New Ideas with Glasp AI 🐣

Glasp AI allows you to hatch new ideas based on your curated content. Let's curate and create with Glasp AI :)

Start Hatching 🐣