Authority Does Not Scale the Way Complexity Does

Why formal governance clarifies responsibility but rarely reduces leadership strain

When leadership strain appears in buy-and-build platforms, authority is often the first lever pulled. Decision rights are clarified, governance is formalized, escalation paths are defined, and reporting lines are tightened. Boards ask whether accountability is clear enough, whether management has sufficient mandate, whether roles are properly drawn. These interventions are not wrong. They are often necessary. But they rarely do what they are expected to do. They clarify responsibility without materially reducing leadership load. This is not a failure of governance design. It is a structural mismatch between how authority scales and how complexity accumulates.

The Intuition That Authority Should Solve Strain

Authority feels like the natural solution to leadership pressure. When too many decisions reach the top, the instinct is to push them down. When ambiguity slows execution, the instinct is to define roles more tightly. When coordination breaks, the instinct is to formalize escalation. Underneath all of it sits a reasonable assumption: if authority is clear, leadership effort should be conserved. In stable organizations that assumption often holds. In buy-and-build platforms it breaks down. An earlier note in this section argued that decision rights, not alignment, govern decision velocity; this note is about the ceiling that allocation runs into, not how to allocate.

Linear Authority, Non-Linear Complexity

Formal authority scales linearly. You can add roles, define mandates, extend spans of control, and articulate decision rights with reasonable precision. Authority can be documented, communicated, and replicated. Complexity does not behave this way. Each acquisition introduces new operating assumptions, new interfaces, new exceptions, and new judgment calls that were not present before, and these do not add up in a straight line. They interact. The result is non-linear growth in coordination demand.

This is the practical face of a principle from systems theory. Only variety can absorb variety: any control structure can regulate a system only if it commands at least as much variety as the system it governs (Ashby, 1956). Authority is a low-variety instrument applied to a high-variety problem. The same idea reaches organizations through the information-processing view, which holds that as task uncertainty rises, the volume of information that must be processed during execution rises with it, and structures that do not expand their information-processing capacity fall back on exceptions and escalation (Galbraith, 1974). Authority can be clarified faster than complexity can be absorbed, but clarifying it is not the same as containing it.

Why Escalation Persists After Authority Is Fixed

One of the most common frustrations in buy-and-build is persistent escalation. Even after decision rights are defined, governance is clarified, and accountability is assigned, issues keep surfacing at senior levels. This is usually misread as a lack of discipline, weak management, or cultural dependency. More often it reflects the limits of authority itself. Authority resolves who may decide. It does not resolve what the system does not yet know. Novelty, meaning new combinations of problems, trade-offs, and timing conflicts, cannot be fully delegated, so it escalates because it must. Leadership load stays high not because authority is unclear but because complexity is unresolved, exactly as the information-processing view predicts when exceptions outrun the structure built to handle them.

The Re-Emergence of Informal Authority

Where formal authority cannot absorb complexity, informal authority fills the gap. It shows up as check-ins before decisions, reliance on specific individuals, shadow vetoes, and decisions that are formally delegated but practically centralized. These behaviors are often framed as governance failures. They are better understood as adaptive responses. Informal authority lets the system function when formal structures lag reality, and it reduces friction in the short term. But it also concentrates leadership load and masks the true level of system strain.

Why More Authority Can Increase Leadership Load

There is a counterintuitive dynamic here. As authority structures become more explicit, leaders become the reference point for interpretation, edge cases multiply, and decision-making becomes more visible. This increases demand on leadership attention rather than reducing it. Leaders are pulled into exception handling, arbitration between formally valid claims, and sequencing decisions that authority cannot resolve on its own. The system becomes more dependent on leadership judgment precisely because authority is clearer.

Authority as a Design Variable, Not a Relief Valve

Authority is usually treated as a relief valve, something that releases pressure. In buy-and-build systems it behaves more like a design variable. It shapes how pressure surfaces, where ambiguity accumulates, and how leadership effort is consumed. Well-designed authority does not eliminate leadership strain. It channels it, determining whether leadership attention is focused on novel, high-value decisions or dissipated across recurring coordination problems. That distinction matters far more than formal clarity alone.

The Limits of Governance as a Solution

None of this diminishes the importance of governance. Clear authority is foundational, and without it systems fragment quickly. But governance cannot substitute for absorbed learning, stabilized cadence, or reduced novelty. Leadership strain persists when systems generate decisions faster than authority can process them, and at that point the constraint is not governance. It is organizational capacity, the finite stock of managerial attention examined in the absorptive-capacity note.

Setting Up the Bottleneck

This is why leadership bottlenecks form even in well-governed platforms. Performance may stay strong, metrics may look healthy, and initiatives may keep advancing, yet leadership effort becomes increasingly concentrated: more decisions require senior input, fewer issues resolve themselves, and time horizons compress. These bottlenecks do not signal failure. They signal saturation. The deepest version of the point is old: a firm’s growth is ultimately bounded not by capital or opportunity but by the managerial capacity it can supply to absorb new resources, the limit Penrose identified and the engine behind the resource-based account of how platforms actually grow (Penrose, 1959). The next essay examines how and why leadership bottlenecks appear before performance declines, and why they are so often misdiagnosed when they finally become visible.

Closing

Authority is essential. But it is not elastic. In buy-and-build strategies complexity outpaces formal structure long before it appears on financial statements. Leadership strain persists not because authority is unclear but because authority alone cannot absorb the system it governs. Recognizing this is not a critique of governance. It is a prerequisite for understanding why leadership becomes the binding constraint in scaled acquisition strategies.

References

Ashby, W. R. (1956). An introduction to cybernetics. Chapman & Hall. (Law of Requisite Variety, ch. 11.)

Galbraith, J. R. (1974). Organization design: An information processing view. Interfaces, 4(3), 28–36.

Penrose, E. T. (1959). The theory of the growth of the firm. Oxford University Press.

Related in the Thesis Notebook:

Resource-Based View Revisited · Absorptive Capacity under Cumulative Load

Related in this section:

Leadership Is a Constraint, Not a Trait · Decision Rights, Not Alignment, Scale Platforms · Operating Cadence Is a Leadership System