That asymmetry is worth naming precisely, because it is where the rest of this Notebook, and the research it accompanies, tries to contribute.

What the field establishes: private-equity value creation

The foundations are solid. Early accounts located the value of the leveraged buyout in governance and incentive discipline, the alignment of owners and managers and the discipline of debt on free cash flow (Jensen, 1989). Later work organised the sources of buyout value into financial, governance, and operational engineering, with operational engineering, the industry and operating expertise a sponsor brings, emerging as the distinguishing capability of leading firms (Kaplan & Strömberg, 2009). And the returns themselves are real but heterogeneous and persistent across funds, which points to sponsor skill rather than luck (Kaplan & Schoar, 2005). On the economics of private equity, the field is on firm ground.

What the field establishes: the economics of buy-and-build

On buy-and-build specifically, the descriptive record is increasingly strong. Inorganic growth through add-ons has become central to the private-equity business model (Hammer et al., 2017), and the strategy can earn above-average returns despite premiums paid for add-ons, through a combination of top-line growth and multiple expansion, the familiar effect of buying small and selling big (Hammer et al., 2022). The conditions under which consolidation creates value, the industry and platform characteristics that make it attractive, have begun to be specified (Bansraj & Smit, 2017). The field can tell you that buy-and-build pays, roughly when, and through which financial channels. Notably, much of this evidence is drawn from European samples, leaving the larger and more add-on-intensive US market comparatively underexamined.

What the field underexplains: the mechanism

The gaps appear when the question turns from whether to how. Three are worth naming. First, target-selection research is built overwhelmingly on corporate acquirers and assumes strategic fit as the motive; it rarely accounts for the distinctive incentives and finite horizons of financial sponsors, and the recent move to theorise private equity as a specialised intermediary (Nary & Kaul, 2023) has not yet been brought to bear on add-on selection. Second, what work exists on private-equity selection examines investor preferences at the platform stage rather than the sequential add-on logic that defines buy-and-build (Osborne et al., 2012). Third, and most fundamental, the field models selection as a discrete, static event rather than the unfolding process it is in a sequence of deals (Welch et al., 2020), even though performance is best understood at the level of the acquisition programme (Laamanen & Keil, 2008). The result is a literature rich in outcomes and prices and thin on the mechanism that produces them.

A worked illustration: the question the field cannot yet answer

The gap is easiest to see as a question the existing evidence cannot resolve. Suppose two US building-products platforms run the same thesis over the same five years, pay similar multiples, and operate in the same fragmented market. One compounds; the other stalls after its fourth add-on. The financial literature can tell you the average platform in their cohort earned a given return through growth and multiple expansion. It cannot tell you why these two diverged, because the divergence lives in the mechanism: the accumulated integration capability, the recursive build-borrow-buy choices, and the way the selection criteria did or did not update across the sequence. Those are exactly the lenses this Notebook has applied, and exactly the variables the descriptive literature does not capture. The study that would answer the question is a process account of how selection actually unfolds, which is what the field still lacks.

What the field still needs

Four gaps, stated as an agenda rather than as claims:

1. A private-equity perspective on selection, built on sponsors’ incentives and finite horizons rather than imported from corporate-acquirer research.

2. Add-on-level study, examining how sponsors identify and prioritise add-ons over a hold period, not just how they choose platforms.

3. A process account, treating selection as a sequence in which each deal reshapes the criteria for the next, rather than as a discrete event.

4. US evidence, since the market where add-on activity is most intense is the one least examined.

Closing the Notebook

Read together, the seven notes make a single argument. Buy-and-build advantage is built, not bought (the resource-based view); platforms acquire rather than contract when ownership is the cheaper governance form (transaction-cost economics); selection is a resource-matching and integration decision, not a quality screen; the thesis forms through a deliberate-emergent process; integration capacity, not deal supply, is the binding constraint; and the optionality languageplatforms borrow from finance describes value but not mechanism. The literature establishes that buy-and-build works and what it costs. How it works, and why otherwise-similar platforms diverge, is the open question, and it is the question the research behind this Notebook sets out to answer.

References

Bansraj, D. S., & Smit, H. T. J. (2017). Optimal conditions for buy-and-build acquisitions [Preliminary version]. Erasmus School of Economics.

Hammer, B., Knauer, A., Pflücke, M., & Schwetzler, B. (2017). Inorganic growth strategies and the evolution of the private equity business model. Journal of Corporate Finance, 45, 31–63.

Hammer, B., Marcotty-Dehm, N., Schweizer, D., & Schwetzler, B. (2022). Pricing and value creation in private equity-backed buy-and-build strategies. Journal of Corporate Finance, 77, 102285.

Jensen, M. C. (1989). Eclipse of the public corporation. Harvard Business Review, 67(5), 61–74.

Kaplan, S. N., & Schoar, A. (2005). Private equity performance: Returns, persistence, and capital flows. The Journal of Finance, 60(4), 1791–1823.

Kaplan, S. N., & Strömberg, P. (2009). Leveraged buyouts and private equity. Journal of Economic Perspectives, 23(1), 121–146.

Laamanen, T., & Keil, T. (2008). Performance of serial acquirers: Toward an acquisition program perspective. Strategic Management Journal, 29(6), 663–672.

Nary, P., & Kaul, A. (2023). Private equity as an intermediary in the market for corporate assets. Academy of Management Review, 48(4), 719–748.

Osborne, S., Katselas, D., & Chapple, L. (2012). The preferences of private equity investors in selecting target acquisitions: An international investigation. Australian Journal of Management, 37(3), 361–389.

Welch, X., Pavićević, S., Keil, T., & Laamanen, T. (2020).The pre-deal phase of mergers and acquisitions: A review and research agenda. Journal of Management, 46(6), 843–878.

What Exit Actually Tests

At exit, buyers are not asking whether leadership worked. They are asking whether leadership transfers: whether judgment can travel without the people who currently hold it, whether decisions can be made without informal escalation, whether cadence can survive a reset of authority, and whether complexity can be absorbed without heroic intervention. These questions are rarely stated explicitly; they are inferred through diligence, management interactions, and early integration planning. What exit tests is not leadership quality but leadership durability.

Built Capacity vs. Borrowed Capacity

Over the hold period, platforms inevitably borrow leadership capacity, through exceptional executives, founder presence, operating-partner support, board intervention, or concentrated decision-making at the top. None of this is wrong, and in many cases it is necessary. The audit comes later. At exit, buyers distinguish between capacity embedded in operating systems, authority structures, and cadence, and capacity concentrated in individuals or relationships. Borrowed capacity performs well under stable ownership. Built capacity survives ownership change, because built capacity is an accumulated, path-dependent stock rather than a personal attribute (Dierickx & Cool, 1989), and the ceiling it relieves is the managerial limit on growth itself (Penrose, 1959; the resource-based account).

How Leadership Fragility Surfaces at Exit

Leadership fragility rarely announces itself. It surfaces indirectly, through patterns buyers recognize quickly: decisions that require checking with specific people, processes that work only when certain leaders are present, cadence that depends on informal coordination, authority that is clear in practice but hard to articulate, and performance that looks strong but feels brittle. None of these is a deal-breaker alone. Together they signal that leadership effectiveness is context-dependent, and context disappears at exit, which is the bottleneck dynamic seen from the buyer’s side (Leadership Becomes a Bottleneck Before Performance Does).

Why Strong Leaders Can Increase Exit Risk

This is the uncomfortable truth exits often surface. Strong leaders can compensate for weak systems so effectively that the weaknesses remain invisible: decision rights stay implicit because leaders resolve ambiguity personally, cadence stays informal because leaders synchronize activity manually, and escalation stays manageable because leaders absorb load themselves. The platform performs and value is created, but what buyers see is not performance, it is dependency. Exit reframes leadership excellence as a concentration risk unless it has been converted into organizational capacity, the conversion that authority and its limits and leadership debt both bear on.

Exit Does Not Punish Intervention, It Punishes Opacity

Buyers do not penalize platforms for being actively managed. They penalize platforms when leadership effort cannot be disentangled from outcomes, when accountability is hard to trace, or when authority is unclear outside existing relationships. This is why exit diligence focuses so heavily on decision clarity, operating rhythm, management depth, and how work actually gets done under pressure. These are not governance preferences. They are transferability tests, and they probe whether the finite resource of leadership attention has been institutionalized or merely spent (Cohen & Levinthal, 1990; the absorptive-capacity note).

Leadership as an Asset Class

Seen through the exit lens, leadership behaves like an asset. It can be accumulated, depreciated, leveraged, or impaired. Leadership assets that are codified, distributed, and reinforced through cadence and authority retain value beyond the original owners. Leadership assets that remain tacit, centralized, or personality-driven do not disappear at exit, but they discount, not because they are ineffective but because they are non-transferable.

The Quiet Symmetry with Integration

Exit exposes the same dynamics integration does, just in reverse. Integration asks whether this system can absorb change. Exit asks whether this system can survive separation. In both cases leadership is tested not at the level of intent but at the level of design.

What Exit Ultimately Reveals

By the time exit arrives, leadership systems are largely fixed. What buyers observe is the cumulative result of how authority was clarified, how cadence was stabilized, how decision-making was distributed, and how leadership behavior compensated or failed to. Exit does not ask whether leadership was strong. It asks whether leadership was built.

Closing the Leadership & Operating Section

Across this section a single logic has been developed: leadership capacity is finite, authority and cadence determine how it is used, behavior under constraint determines whether it scales, operating choices accumulate leadership debt or equity, and exit reveals which path was taken. This is not a moral argument about leadership. It is an operating reality. Leadership that exists only in people performs well until ownership changes; leadership that exists as a system performs well after. That distinction is invisible during growth. Exit makes it legible.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

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 as a System, Not a Role · Operating Models Accumulate Leadership Debt · Leadership Becomes a Bottleneck Before Performance Does · Authority Does Not Scale the Way Complexity Does

Buyers Do Not Buy Execution Results

They buy confidence that execution will hold after they take control. This explains a great deal of otherwise puzzling exit behavior: businesses with similar EBITDA, growth, and margins can trade at meaningfully different valuations, not because one executed better but because one appears less fragile. Execution quality is inferred, not declared. Buyers ask, often implicitly, how much of this performance depends on specific people, how much of the execution logic is embedded in systems versus habit, how reversible the prior owner’s decisions are, and how much learning capacity remains once integration pressure resumes. None of these appear directly in a CIM. They surface through diligence posture, deal structure, and pricing discipline.

Where Execution Shows Up in Diligence

Strong execution systems compress diligence. When execution is coherent and legible, buyers spend less time reconciling narratives, fewer confirmatory workstreams are required, and the organization appears to explain itself without excessive translation. When execution depends heavily on tacit knowledge, informal coordination, or individual judgment, diligence expands, not because buyers distrust the numbers but because they are trying to understand what would break under their ownership. Execution quality often reveals itself through how much explanation a business requires.

The Individual vs. the System

Buyers do not discount strong leaders. They discount systems that cannot survive leadership change. Founders often read concern about key-person risk as a judgment on leadership strength; in reality it is a judgment on system portability. Execution systems that rely on personal escalation paths, uncodified integration knowledge, informal authority, or exception-heavy processes appear brittle under transition even if they perform well in steady state. The question is not whether execution has worked but whether it will continue once decision rights, incentives, and oversight change, and what makes the difference is whether integration capability was deliberately codified into routines that outlast their authors (Zollo & Singh, 2004).

Optionality After Close

Execution quality is also inferred through what it constrains. Buyers assess how standardized the platform already is, how difficult it would be to reverse or adapt prior decisions, and how much flexibility remains to sequence future integrations differently. Standardization that arrived too early reads as finality rather than maturity, and systems that encode unresolved assumptions limit the buyer’s ability to learn post-close, so what felt like discipline under one owner can feel like rigidity under another (Standardization Is a One-Way Door; Adner & Levinthal, 2004). This is why optionality matters more than polish. Execution systems that preserve learning capacity appear more valuable even when they are less tidy, because a capability still capable of renewing has not yet entered decline (Helfat & Peteraf, 2003).

Execution as Downside Protection

The economic effect of execution quality is best understood not as upside creation but as downside compression. Strong execution systems reduce perceived integration risk, shorten transition timelines, lower the probability of post-close disruption, and make future acquisitions feel more predictable. Weak or opaque systems do the opposite, and buyers compensate not by walking away but by pricing defensively through earn-outs, holdbacks, integration discounts, or conservative multiples. This is why execution affects exit value even when performance is strong, and why the learning that has or has not been preserved shows up directly in the price (Learning Breaks Before Performance Does; When Execution Becomes Defensive).

The Exit Mirror

Seen through the exit lens, execution is not a phase or a capability. It is a signal system, communicating how the organization handles strain, how learning compounds or stalls, how dependent performance is on continuity, and how much confidence a new owner can place in future execution. Most of these signals were emitted long before exit was contemplated, shaped by decisions made under integration pressure, by how quickly systems were imposed, and by whether learning was preserved or crowded out, the cumulative-load dynamic developed in the absorptive-capacity note. Exit does not introduce these dynamics. It reveals them.

What This Means for Integration & Execution

The implication is not that execution should be designed for exit; that framing is too narrow and usually wrong. The implication is that execution systems inevitably become part of the asset. Whether intentionally or not, they shape how the business is understood, valued, and transferred. Execution that compounds capability over time appears reliable; execution that merely sustains performance appears fragile, and buyers know the difference even when they struggle to articulate it, because what they are really pricing is the accumulated, transferable resource base (the resource-based account).

Closing the Section

Integration and execution is often treated as operational follow-through. In reality it is where strategy either becomes transferable or remains owner-specific. Execution does not just determine how the business runs. It determines how the business can be owned. That is why it matters at exit.

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Helfat, C. E., & Peteraf, M. A. (2003). The dynamic resource-based view: Capability lifecycles. Strategic Management Journal, 24(10), 997–1010.

Zollo, M., & Singh, H. (2004). Deliberate learning in corporate acquisitions: Post-acquisition strategies and integration capability in U.S. bank mergers. Strategic Management Journal, 25(13), 1233–1256.

Related in the Thesis Notebook:

Absorptive Capacity under Cumulative Load · Resource-Based View Revisited

Related in this section:

Execution as a System Property · When Execution Becomes Defensive · Learning Breaks Before Performance Does · Standardization Is a One-Way Door

What the Exit Actually Reflects

Buyers do not price what was meant to happen. They price what exists. The system they encounter, its coherence, fragility, optionality, and constraints, is the cumulative result of decisions made long before integration began. At exit the market reflects back how tightly the system has been coupled, how resilient it is under scrutiny, how much uncertainty remains unresolved, and how credibly future performance can be sustained. These characteristics are not created at exit. They are exposed by it.

Selection Decisions That Echo Forward

Exit outcomes often trace directly to early design choices, though the connection is rarely acknowledged. Targets selected for compatibility tend to produce deeply integrated systems that can appear coherent but brittle, so buyers scrutinize key dependencies, leadership concentration, and the cost of disentanglement. Targets acquired with preserved distance may look messier but often offer clearer modularity, identifiable value centers, and optional paths forward, attributes sophisticated buyers value (Distance Is a Design Variable). Diligence that compressed uncertainty rather than resolving it leaves its residue in buyer diligence, where deferred questions resurface with greater consequence (Diligence Does Not Eliminate Uncertainty), and signals ignored during early integration reappear as patterns that are difficult to explain away (Early Signals Are Not Noise). The exit does not create these issues. It aggregates them.

The Buyer’s Perspective Is Unforgiving

Buyers approach exits differently than sellers approach acquisitions. They are less concerned with narrative and more concerned with transferability, asking not whether the strategy made sense but whether the system can be owned, operated, and adapted under new stewardship. From that perspective exit pricing reflects how much rework the buyer anticipates, how much learning remains, how dependent performance is on specific individuals or conditions, and how much uncertainty must still be carried forward. These assessments are grounded in structure, not story, and they turn on the same information conditions that govern acquisitions of private firms in the first place, where what cannot be verified is priced as risk (Capron & Shen, 2007). Exit is where early design decisions are translated into economic terms.

Exit as an Audit Trail

Viewed properly, exit functions as an audit, not of execution quality but of design integrity. It tests whether interaction risk was appropriately sized, whether distance was collapsed deliberately rather than by default, whether uncertainty was allocated where the system could absorb it, and whether early signals were integrated rather than overridden. Strong exits are not those without friction; they are those where friction is legible and contained. Weak exits are not those with disappointing multiples; they are those where buyers struggle to understand what they are inheriting. The difference lies upstream, in what the section’s capstone calls system design, and in the broader point that the pre-deal phase is an unfolding process rather than a discrete event (Welch et al., 2020).

Why Exit Should Not Drive Selection

This framing carries an important implication. If exit is a mirror, then designing selection for exit is a category error. Optimizing for buyer preferences too early distorts design: it encourages premature standardization, excessive integration, and narrative overreach, and it collapses distance before learning is complete. Paradoxically, the systems most attractive at exit are often those not designed with exit foremost in mind but with coherence, optionality, and absorption limits respected along the way. Exit rewards systems that make sense on their own terms, because the resources that actually transfer value are the accumulated, hard-to-replicate ones, not the cosmetic ones (Dierickx & Cool, 1989).

Holding the Mirror Without Flinching

For operators and investors willing to look closely, exit offers rare clarity. It reveals whether early comfort masked later strain, whether diligence created confidence or merely closure, whether signals were integrated or ignored, and whether the system was allowed to become something coherent or simply something busy. This clarity is uncomfortable precisely because it cannot be corrected retroactively, but it is invaluable, because the mirror reflects not just the past deal but the logic that will shape the next one, the recursive selection process developed in the target-selection note and the resource-based account.

Closing the Section

This section has not argued that better selection guarantees better outcomes. It has argued something narrower and more demanding: that selection decisions quietly design the system long before execution begins, and that exits merely reveal what those designs made possible. Exit is not the end of the story. It is where the story becomes legible.

References

Capron, L., & Shen, J. C. (2007). Acquisitions of private vs. public firms: Private information, target selection, and acquirer returns. Strategic Management Journal, 28(9), 891–911.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Welch, X., Pavićević, S., Keil, T., & Laamanen, T. (2020). The pre-deal phase of mergers and acquisitions: A review and research agenda. Journal of Management, 46(6), 843–878.

Related in the Thesis Notebook:

The Pre-Deal Phase and Target Selection · Resource-Based View Revisited

Related in this section:

Target Selection as System Design · Early Signals Are Not Noise · Diligence Does Not Eliminate Uncertainty · Distance Is a Design Variable

What Buyers Are Really Assessing

At exit, buyers are not evaluating whether the strategy was clever. They are evaluating whether the system is absorbable, and that capacity to be absorbed is the same finite resource that bounded the platform’s own growth (the absorptive-capacity note). A platform can show strong financials and still feel fragile; one with modest growth can command confidence if its internal logic is clear and durable. Buyers look for answers to questions that were implicit during the build: can this system continue without the people who currently compensate for its complexity; does coordination live in structure or in relationships; are integration choices resolved or merely stabilized; is growth encoded into the operating model or carried by momentum? These are rarely answered explicitly during ownership. They are answered structurally, through what the buyer encounters in diligence.

Exit as the First External Stress Test

During ownership, many weaknesses stay invisible. Leadership absorbs ambiguity, exceptions are managed informally, deferred decisions are tolerated, and performance can remain strong because the organization has learned to live with its own complexity. The exit removes these buffers. Suddenly the platform must explain itself: decision rights must be legible, integration logic defensible, coherence institutional rather than personal. This is why exits feel heavier than anticipated, not because something is wrong but because the system is being seen whole for the first time. The buyer is not asking whether this worked. They are asking whether it will keep working once it is no longer yours.

What Exits Reveal About Compounding

One of the clearest signals at exit is whether early success was converted into durable capacity. Platforms that truly compounded show integration practices that are consistent rather than heroic, leadership roles that are defined rather than overloaded, systems that reduce coordination cost rather than raise it, and growth paths that feel deliberate rather than opportunistic. In these cases the exit feels close to inevitable and negotiation focuses on price, not structure. Platforms that ran on early momentum reveal a different profile: learning that never institutionalized, optionality carried rather than resolved, leadership acting as the glue. They may still sell well, but the process feels negotiated rather than natural, and value is discounted not because performance is lacking but because continuity feels conditional. The exit reveals whether compounding happened at the system level or only at the deal level, which is the resource-accumulation question at the heart of the resource-based account. It is also where the multiple expansion that buy-and-build relies on is finally tested against what the platform can sustain (Hammer et al., 2022).

Irreversibility Made Visible

Exit is where irreversibility becomes unmistakable. Decisions that once felt provisional, about integration depth, governance, or operating cadence, are suddenly seen as permanent features of the platform. Buyers do not ask whether these choices were optimal. They ask whether they can live with them, which is why some exits feel constrained despite strong performance. The buyer evaluates what the platform is and how costly it would be to change, not what it could have been. Irreversibility is not punished. Unacknowledged irreversibility is, the dynamic developed in Irreversibility in Buy-and-Build Systems.

Strategy Drift Seen in Reverse

At exit, strategy drift becomes legible in hindsight. The buyer reconstructs the platform’s evolution backward: which acquisitions shaped the operating model most deeply, where integration principles bent under pressure, how target selection adapted to internal constraints. What emerges is usually not inconsistency but adaptation, the platform evolving to preserve coherence as complexity rose. Exit diligence surfaces this drift not as a critique but as context, because the path that produced the current system constrains what comes next (Strategy Drift in Serial Acquisition Platforms). In this sense the exit is not a verdict on the strategy. It is an interpretation of how the system learned.

Why Survival Shows Up at Exit

One quiet truth of buy-and-build is that many platforms eventually optimize for survival rather than aspiration. This is not failure; it is selection. Systems that survive long enough to exit have usually learned to avoid destabilizing themselves, trading some optionality for predictability and narrowing their operating range to preserve continuity. At exit this optimization becomes visible, and buyers often pay for it, explicitly or implicitly, because survival under complexity is not trivial. The tension arises when the narrative stays aspirational while the system has become conservative. The exit exposes that gap, and buyers reconcile it through price, structure, or terms. The exit is not moral. It is diagnostic, and it confirms the value-creation evidence that what distinguishes platforms is operating capability, not deal activity alone (Kaplan & Strömberg, 2009).

What the Exit Does Not Reveal

It is equally important to say what the exit does not reveal. It does not tell you whether the strategy was right, whether different choices would have produced better returns, or whether growth was maximized. It tells you something narrower and more useful: this is what the system you built can now support, without you. That is the only question an exit can answer reliably.

Reading the Exit Properly

For operators and investors alike, the temptation is to treat exit outcomes as validation or refutation. That is a mistake. The more useful reading is structural: what did the exit surface that was invisible during ownership; which constraints proved binding; where did the system rely on people rather than design; which choices aged well and which narrowed the future? These questions are not about regret. They are about learning. The exit is the moment buy-and-build stops being a story told by its builders and becomes an object evaluated by someone else. Handled thoughtfully, it is not the end of the strategy. It is the clearest mirror the strategy will ever have.

Closing

Buy-and-build strategies are rarely undone by bad deals. They are shaped, quietly and cumulatively, by how systems adapt under load (Dierickx & Cool, 1989). The exit does not judge those adaptations. It reveals them. For those willing to read it carefully, the exit offers something more valuable than confirmation or critique: clarity about what the system truly optimized for, and what it could carry no further. That clarity, more than the transaction itself, is what makes the next cycle wiser than the last.

References

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Hammer, B., Marcotty-Dehm, N., Schweizer, D., & Schwetzler, B. (2022). Pricing and value creation in private equity-backed buy-and-build strategies. Journal of Corporate Finance, 77, 102285.

Kaplan, S. N., & Strömberg, P. (2009). Leveraged buyouts and private equity. Journal of Economic Perspectives, 23(1), 121–146.

Related in the Thesis Notebook:

Resource-Based View Revisited · Absorptive Capacity under Cumulative Load

Related in this section:

What Buy-and-Build Actually Optimizes For · Strategy Drift in Serial Acquisition Platforms · Irreversibility in Buy-and-Build Systems · Integration Capacity Is the Binding Constraint

Operators feel this immediately. Once a decision is made and executed, teams are pulled toward the next priority: integration deadlines loom, new initiatives arrive, and leaders are rewarded for progress, not pause. Asking people to slow down and examine what just happened feels countercultural, sometimes even irresponsible. Review competes directly with momentum, and the bandwidth it would require is exactly what the system is shortest of (the bandwidth-debt note makes that scarcity explicit).

From a deal team’s perspective the challenge is different but related. Deals are evaluated against theses that must stay coherent, and attribution matters for internal credibility, external communication, and capital allocation. Revisiting assumptions after the fact risks unsettling that coherence and introducing ambiguity where confidence is expected. So organizations default to narrative continuity: what went well is credited to strategy, what went poorly is attributed to execution or external factors, and the story stays intact even when the underlying mechanics are poorly understood. Learning is replaced by explanation, and that substitution is subtle and corrosive.

Post-decision review demands a different posture. It requires holding several truths at once: that the decision may have been reasonable, that the outcome may still be disappointing, and that causality may be distributed across factors no one controlled. Most systems are not designed for that ambiguity; they prefer clarity, ownership, and forward motion, all of which review threatens. As a result organizations learn selectively, reinforcing what aligns with existing beliefs and discarding what complicates them, so experience accumulates without insight and the organization becomes busier, not wiser. Real capability comes only when experience is deliberately articulated and codified rather than merely repeated (Zollo & Winter, 2002), and raw experience as easily entrenches the wrong lesson as the right one (Haleblian & Finkelstein, 1999).

This is why learning velocity often declines as complexity increases. Each additional decision adds noise, interactions multiply, and outcomes become harder to attribute, so by the time a review is scheduled too much has changed to isolate cause and effect cleanly, and the capacity to absorb the lesson has already been spent (Cohen & Levinthal, 1990; the absorptive-capacity note). The cost compounds quietly: mistakes repeat with minor variation, sequencing errors persist, bandwidth strain is reintroduced under new labels, and risk accumulates under the assumption that prior success validated the approach (how risk fails quietly). The organization becomes experienced without becoming adaptive.

Experienced operators recognize the pattern. They know real learning requires carving out space when it feels least available, reviewing decisions while consequences are still unfolding rather than years later when memory has faded and incentives have shifted, and distinguishing outcomes from mechanisms even when the outcome was acceptable. For investors this discipline is easy to endorse and hard to enforce, because learning reviews slow deployment and introduce friction into narratives markets prefer to keep clean. Yet without them, organizations mistake repetition for mastery, and they confuse the expansion that masks fragility with the consolidation that builds capability (growth is not value creation).

The most effective post-decision reviews share a common feature: they are designed to surface strain, not to assign blame. They ask where the system absorbed pressure, where leaders compensated, and where assumptions quietly failed, focusing less on what was decided and more on what the decision required the organization to carry. That orientation is rare because it is uncomfortable. It forces an organization to confront the limits of its own capacity, not just the quality of its judgment, and to acknowledge that some failures are structural rather than personal and some successes fragile rather than earned. But that is precisely what makes review valuable. Learning does not come from explaining outcomes away. It comes from examining what the system had to become in order to produce them. Organizations that take this seriously do not become slower. They become more deliberate, preserving the ability to adjust course before patterns harden into destiny. In complex systems the most important learning happens after the decision but before the next one. That window is narrow, and it closes quickly.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Haleblian, J., & Finkelstein, S. (1999). The influence of organizational acquisition experience on acquisition performance: A behavioral learning perspective. Administrative Science Quarterly, 44(1), 29–56.

Zollo, M., & Winter, S. G. (2002). Deliberate learning and the evolution of dynamic capabilities. Organization Science, 13(3), 339–351.

Related in the Thesis Notebook:

Absorptive Capacity under Cumulative Load

Related in this section:

Bandwidth Debt: The Cost Leaders Don’t See · Why Risk Rarely Fails Loudly · Growth Is Not Value Creation

Looked at closely, a tension appears. Real options theory offers a compelling way to value investments under uncertainty, but it is far less clear that it explains, or guides, the organisational reality of buy-and-build as it is actually executed. This note examines that tension. The narrow question is whether real options is an operative mechanism in buy-and-build or primarily a retrospective valuation and sensemaking lens that overstates managerial flexibility.

My argument is that real options theory helps explain how acquisitions can create contingent growth opportunities, but that it systematically overstates the degree of reversibility, discretion, and modularity available to a platform running a serial-acquisition strategy. In practice, buy-and-build outcomes align more closely with the resource-based view, developed in the first note of this Notebook, than with real options logic. I hold that as a proposition to be tested, not a settled finding, because the evidence on how sponsors actually decide is still thin.

The promise of real options

Real options theory emerged to address a known weakness of traditional capital budgeting. Net present value treats an investment as a now-or-never commitment, discounting expected cash flows under a fixed plan, and it performs poorly under uncertainty, learning, and staged commitment. Myers (1977) coined the real options framing, observing that many corporate assets, growth opportunities especially, behave like call options whose value depends on discretionary future investment. Dixit and Pindyck (1994) and Trigeorgis (1996) developed the canonical treatments.

The core insight is that investments embed managerial flexibility. A firm may defer, expand, abandon, or stage an investment as uncertainty resolves, so the investment confers the right but not the obligation to act later. Strategy scholars carried the logic into resource allocation, arguing that firms invest to keep options open and that flexibility has economic value static NPV misses (Bowman & Hurry, 1993). On its face, buy-and-build fits: a platform creates follow-on acquisition opportunities, minority stakes preserve expansion options, and sequential deals resemble compound options.

Where real options enters the buy-and-build literature

The most direct application to buy-and-build treats serial acquisitions as compound option games, in which a platform acquisition creates options on future deals, competitive dynamics shape option value, and positioning affects the value of waiting versus acting (Kogut, 1991; Smit & Trigeorgis, 2004; Smit & Moraitis, 2010). Later work extends the framework to the cognitive biases that distort acquisition decisions, arguing that an options frame can help managers price overconfidence and escalation more accurately (Smit & Lovallo, 2014).

This work is theoretically sophisticated and internally coherent, and it deserves a fair hearing rather than a straw-man dismissal. Crucially, the option-games literature does not assume costless reversibility; it incorporates competition, commitment, and path dependence, which is exactly why it is the strongest version of the optionality case. It also states its own scope condition: real options models are most useful when managers explicitly recognise and manage investments as options. That qualification is where theory and practice begin to diverge.

The operating reality of buy-and-build

In execution, buy-and-build exhibits three structural features that strain the assumptions even a sophisticated options account leans on.

First, organisational commitments are hard to reverse. Options logic values the ability to abandon or defer at low cost. Once an acquisition closes, leadership attention is reallocated, systems are integrated, reporting lines change, and cultural expectations shift, and those changes create organisational sunk costs that are not recoverable even when financial capital might be. Abandonment is available in theory and rare in practice, especially once several integrations overlap.

Second, options interact through shared capacity. Options models often treat options as separable. In a platform, acquisitions compete for the same executive attention, integration capacity, and governance bandwidth, so exercising one affects the value and feasibility of the others. That interdependence is the cumulative-load dynamic of the absorptive-capacity note, and it is hard to represent as a portfolio of independent options.

Third, flexibility falls as scale rises. Successful early add-ons, the ones that validate the thesis, often reduce future flexibility rather than increase it. As the platform grows, the cost of reversing course rises, the organisation becomes less modular, and discretion narrows. That is the opposite of the simple options intuition, and it is the heart of the boundary critique that a sequential stream of investment does not, by itself, constitute a real option (Adner & Levinthal, 2004).

Real options as valuation logic versus operating mechanism

These features point to a distinction worth holding onto. As a valuation logic, real options can articulate why an early investment justifies a premium when future growth paths are plausible but uncertain. As an operating mechanism, it rarely governs how buy-and-build is actually run. Acquisition decisions in practice rely on narratives of fit and adjacency, resource complementarities, governance and integration-capacity constraints, and heuristic thresholds, far more than on option lattices. Formal option valuations, binomial trees and compound-option models, seldom sit at the centre of a board’s decision beyond illustrative analysis. The lens describes a logic of value; it does not describe the machine.

Where the two lenses diverge

The tension with the resource-based view runs deeper than method, because the two rest on different assumptions about how value is created. The resource-based view assumes resources are heterogeneous, capabilities are embedded and path-dependent (Dierickx & Cool, 1989; Barney, 1991), and value is created through accumulation and recombination. Real options assumes decisions can be staged cleanly, flexibility is retained over time, and investments can be abandoned without system-level disruption. In buy-and-build settings the resource-based assumptions dominate observed outcomes: capabilities accumulate unevenly, integration debt compounds, and early decisions shape later feasibility. Acquisitions look less like options than like irreversible resource commitments whose value depends on future recombination capacity.

When real options does add value

The critique narrows the framework rather than discarding it. Real options is most useful in buy-and-build where investments are genuinely staged, as with minority stakes or joint ventures, where exit or expansion rights are contractually explicit, where integration is deliberately limited, and where the platform stays structurally modular. Those conditions are more common at the edges of a strategy than at its core. The compound-option account is most defensible when acquisitions retain genuine separability, which serial roll-ups, by design, tend to lose.

A worked illustration: the option that became a commitment

Picture a platform that takes a minority stake in a regional supplier, structured deliberately as an option: a contractual right to acquire the rest within three years, with the supplier left to run independently in the meantime. On a real-options view this is textbook, a staged investment that preserves the right to expand and the right to walk.

Within a year the logic erodes. The platform, wanting the procurement synergy that justified the stake, begins integrating purchasing and back-office systems before exercising the call, because waiting leaves value on the table. The supplier’s owner, now dependent on the platform’s systems, can no longer be cleanly separated, and the platform’s own operations have been reorganised around the combination. When the three-year mark arrives, the option to walk is nominal: the businesses are entangled, the sunk organisational costs are real, and not exercising would be more disruptive than exercising. The option was genuine at signing and a commitment in practice long before it was formally exercised. The reversibility the structure promised was consumed by the integration the synergy required.

The objection: option-games already model this

The strongest objection comes from the option-games tradition itself: it already incorporates competition, commitment, and irreversibility, so the critique attacks a cruder version of the theory than its best proponents hold. This is fair, and worth conceding. The sophisticated models can represent partial irreversibility and interaction. The disagreement is not really about whether the mathematics can accommodate these features; it is about what does the explanatory work in practice. When a platform’s behaviour is driven by accumulated capability, integration capacity, and the path dependence of earlier deals, the resource-based account names those forces directly, while the options account must enter them as parameters. A lens that requires its central phenomena to be supplied as adjustments is a weaker description than one that puts them at the centre. Real options remains a valuable complement for valuation and for disciplining bias (Smit & Lovallo, 2014); it is not the engine.

Four propositions

Stated plainly, so they can be argued with and tested against cases:

1. Valuation, not mechanism. Real options is a useful valuation and sensemaking lens for buy-and-build, but it rarely governs how platforms actually decide and integrate.

2. Reversibility is overstated. The organisational commitments created by integration make abandonment costly and rare, so the flexibility the options frame assumes is largely illusory at the core of a roll-up.

3. Options are not separable. Add-ons interact through shared integration capacity, so they cannot be treated as an independent portfolio of options.

4. Flexibility falls with scale. Successful early deals tend to reduce future flexibility, the opposite of simple options intuition and consistent with a resource-commitment account.

Why this matters

Real options offers a powerful metaphor for investment under uncertainty. In buy-and-build the metaphor often outruns the mechanism: acquisitions are described as options and experienced as commitments, organisationally, culturally, and cognitively. The further a platform travels along a serial path, the less its future resembles a set of freely exercisable options and the more it reflects accumulated resource positions shaped by earlier choices, the position argued in Resource-Based View Revisited and constrained by the dynamics behind Integration Capacity Is the Binding Constraint. Treated as a partial lens disciplined by the resource-based account, real options earns its place. Treated as the engine of buy-and-build, it misleads.

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Barney, J. (1991). Firm resources and sustained competitive advantage. Journal of Management, 17(1), 99–120.

Bowman, E. H., & Hurry, D. (1993). Strategy through the option lens: An integrated view of resource investments and the incremental-choice process. Academy of Management Review, 18(4), 760–782.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Dixit, A. K., & Pindyck, R. S. (1994). Investment under uncertainty. Princeton University Press.

Kogut, B. (1991). Joint ventures and the option to expand and acquire. Management Science, 37(1), 19–33.

Myers, S. C. (1977). Determinants of corporate borrowing. Journal of Financial Economics, 5(2), 147–175.

Smit, H. T. J., & Lovallo, D. (2014). Creating more accurate acquisition valuations. MIT Sloan Management Review, 56(1), 63–72.

Smit, H. T. J., & Moraitis, T. (2010). Serial acquisition options. Long Range Planning, 43(1), 85–103.

Smit, H. T. J., & Trigeorgis, L. (2004). Strategic investment: Real options and games. Princeton University Press.

Trigeorgis, L. (1996).Real options: Managerial flexibility and strategy in resource allocation. MIT Press.

The Persistent Misdiagnosis of Leadership Failure

Buy-and-build strategies rarely fail loudly. More often they degrade quietly: decisions take longer, escalation increases, coordination costs rise, learning slows, and leaders feel busier while becoming less effective. When this happens, leadership is usually blamed, and the diagnosis is intuitive, that leaders are stretched, mismatched, or no longer fit for the next phase. Sometimes that is true. Often it is not. What has failed is not leadership capability but the system leadership operates within. Treating leadership as a trait leads to recurring remedies, replacement, restructuring, reinforcement, that rarely address the source of strain. Seeing leadership as a system changes the diagnosis.

Leadership Capacity as a Finite Resource

The section opened by reframing leadership as a constrained resource. Leadership capacity is not simply time. It is a composite of attention, judgment, interpretive ability, and relational bandwidth, and buy-and-build taxes all of them at once. Each acquisition introduces ambiguity, each integration adds interfaces, each expansion multiplies exceptions, and none of it arrives evenly. Complexity increases in jumps, not gradients, while leadership capacity does not expand automatically in response. Early success masks this as leaders stretch and informal coordination compensates, so the constraint becomes visible only after capacity has been exceeded. This is the managerial limit on growth in its sharpest form (Penrose, 1959; Leadership Is a Constraint, Not a Trait), and it is why strain is so often recognized too late to reverse easily.

Authority Does Not Scale with Complexity

One response to strain is to clarify authority: define decision rights, formalize governance, draw escalation paths (Decision Rights, Not Alignment, Scale Platforms). These are necessary but not sufficient. Authority scales linearly while coordination demand scales non-linearly, so as platforms grow, new situations arise faster than authority structures can anticipate them, informal decision-making re-emerges, and escalation increases, not because authority is unclear but because it is incomplete. Only variety can absorb variety, and an authority structure cannot regulate a system that generates novelty faster than the structure can process it (Ashby, 1956; Galbraith, 1974; Authority Does Not Scale the Way Complexity Does). This is why leadership load often rises after governance is fixed.

Cadence Determines How Leadership Is Consumed

If authority determines who decides, cadence determines when leadership is engaged. Operating cadence governs how frequently issues surface, how long ambiguity persists, and how often leaders are interrupted, and it is rarely designed explicitly, emerging instead from reporting cycles, integration timelines, and crisis responses. When cadence accelerates without selectivity, capacity is consumed rapidly, everything feels urgent, and leaders are forced into constant context-switching. When cadence stabilizes, leadership effort compounds, patterns emerge, and decisions travel further with less intervention. Cadence does not slow or speed the organization. It determines whether leadership effort is focused or fragmented (Operating Cadence Is a Leadership System).

Behavior Under Constraint

Systems are never complete. In buy-and-build, leaders must operate before structures are settled, authority is internalized, or cadence is stabilized, and this is where behavior matters most, not as personality but as load-bearing action. As the section explored through the work of Warren Bennis (L&O-04), leadership under constraint shows up as consistency rather than certainty, judgment rather than control, restraint rather than urgency, and meaning rather than instruction. These behaviors do not replace system design. They let systems function while design lags reality, conserving leadership capacity rather than consuming it.

Leadership Debt and Path Dependence

Leadership systems are path-dependent. Early choices, often made for speed, accumulate consequences: centralized decisions accelerate early execution but concentrate load, informal coordination bypasses friction but resists scaling, and temporary structures harden into permanent dependencies. These create leadership debt, which is not the result of poor leadership but of leadership working too well in the absence of system reinforcement, and like other organizational debt it stays invisible until conditions change and the stocks that would have to be rebuilt cannot be conjured quickly (Dierickx & Cool, 1989; Operating Models Accumulate Leadership Debt). By the time reversal is needed it is costly, which is also when the bottleneck has already formed (Leadership Becomes a Bottleneck Before Performance Does).

Leadership as an Emergent Property

Treated as a system, leadership outcomes are emergent. No single decision determines whether leadership scales and no single leader creates durability alone; outcomes arise from the interaction of capacity limits, authority structures, cadence design, behavior under pressure, and accumulated operating choices. This explains why similar strategies with similar talent produce different leadership outcomes. Leadership success is not reproducible through people alone. It is reproduced through systems that make good leadership easier and bad leadership harder, and the finite resource being protected, attention, is the same one absorptive capacity describes (Cohen & Levinthal, 1990; the absorptive-capacity note).

Why This Perspective Matters

Treating leadership as a system does not diminish leaders. It respects the reality of their work: that they operate under real constraints, that complexity accumulates faster than capability, and that success often depends on invisible design choices rather than visible heroics. It also reframes responsibility. Leadership strain is not a personal failure to be corrected but a system outcome to be understood, and that distinction lets organizations diagnose earlier, intervene more effectively, and preserve leadership capacity before it visibly degrades. The deeper logic, that advantage rests on accumulated, hard-to-replace resources, is the subject of the resource-based account.

From Leadership to Exit

The section has built a single argument from several angles: leadership capacity is finite, authority shapes leverage, cadence governs consumption, behavior under constraint conserves or dissipates effort, and operating choices accumulate leadership debt or equity. What remains is to observe what happens when the system is tested under its most revealing condition, exit. The next essay examines how ownership change exposes whether leadership capacity was built into the system or borrowed from individuals. That audit does not judge leadership quality. It reveals leadership durability.

Closing

Leadership in buy-and-build is often discussed as an art. This section has treated it as engineering, not because leadership can be reduced to rules but because outcomes follow structure, and systems amplify or exhaust even the strongest leaders. Seeing leadership as a system does not simplify the work. It makes the work legible, and legibility is the first condition for durability.

References

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

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

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:

Operating Models Accumulate Leadership Debt · Leadership Becomes a Bottleneck Before Performance Does · Authority Does Not Scale the Way Complexity Does · Operating Cadence Is a Leadership System · Decision Rights, Not Alignment, Scale Platforms · Leadership Is a Constraint, Not a Trait

From Individual Acts to System Behavior

At the level of individual action, execution looks straightforward: people decide, teams coordinate, processes run, metrics are tracked. But execution outcomes are not the sum of individual acts. They are the result of interaction effects. Small frictions accumulate, delays propagate, local optimizations conflict, decisions made for speed constrain later choices, learning stalls, and controls tighten. None of these dynamics is fatal alone; together they shape how the system behaves. This is why execution quality can change even when leadership remains strong, incentives are aligned, and the strategy is sound. The system has changed.

The Four Forces That Shape Execution

Across integration-heavy environments, four forces consistently determine execution quality, and they rarely move in isolation.

Integration load accumulates as a stock. Each acquisition adds coordination demands, interfaces, and unresolved assumptions that do not fully reset before the next deal, and even successful integrations leave residue. As load rises, execution becomes more expensive and leaders spend more time reconciling the past than shaping the future. Execution slows not because teams forget how to execute but because the system is carrying more than it appears, the binding constraint developed in the absorptive-capacity note (Cohen & Levinthal, 1990).

Standardization timing converts uncertainty into structure. Timed well it creates leverage; timed early it freezes partial learning into permanent form, closes doors, and makes the organization path dependent, efficient at repeating what it knows and constrained in adapting to what it does not. Execution becomes cleaner and narrower at once (Standardization Is a One-Way Door; Adner & Levinthal, 2004).

Learning velocity is the first casualty of sustained load. As pressure rises, organizations substitute confirmatory execution for generative inquiry, post-mortems shorten, and exceptions are normalized. Performance can stay strong while learning slows, but once learning stalls execution loses its ability to improve and the system protects existing performance rather than expanding capability (Learning Breaks Before Performance Does).

Defensive posture follows. When learning slows and load stays high, controls tighten, variance is treated as risk, escalation increases, and change becomes costly. The posture feels responsible and often is, but it narrows future moves, optimizing for predictability rather than adaptability, the tilt from exploration toward exploitation that sets in under load (March, 1991; When Execution Becomes Defensive).

Why Execution Feels Binary but Isn’t

Execution is often described in binary terms: it works or it does not. That language misleads, because execution degrades gradually in a predictable sequence: integration load accumulates, standardization arrives early to restore control, learning slows under pressure, execution becomes defensive, adaptability narrows, and performance eventually plateaus. At no point does execution fail outright. The system keeps functioning and results may hold for years, but the capacity to absorb new strain diminishes steadily, which is why execution problems are so often misdiagnosed: by the time performance declines, the causes are deeply embedded.

Why Effort and Discipline Are Insufficient

When execution stalls, leaders often respond by demanding more discipline: tighter accountability, more reporting, reinforced standards, harder pushing. These can stabilize performance temporarily but rarely restore adaptability, because effort cannot compensate for cumulative load, irreversible standardization, slowed learning, or a defensive posture. In fact, more effort applied to a constrained system often accelerates rigidity, exhausting remaining slack without changing the underlying dynamics. Execution does not improve because the system can no longer respond to effort the way it once did. The capability itself has entered the decline phase of its lifecycle (Helfat & Peteraf, 2003).

Execution as an Emergent Constraint

Once execution is understood as a system property, a critical insight follows: execution quality constrains strategy long before strategy constrains execution. Organizations rarely abandon strategic ambition explicitly. Instead they narrow the strategies they are willing to pursue, choosing deals that fit the system, sequencing integrations conservatively, and avoiding moves that require reopening decisions. These choices feel prudent and are also revealing. Execution capacity is already limiting what the organization believes it can do.

The Role of Leadership, Reframed

None of this diminishes leadership; it reframes it. Leaders do not drive execution directly. They shape the system that produces execution outcomes, and their influence is strongest in how integration load is paced, when standardization is finalized, whether learning is protected under pressure, and how defensiveness is interpreted and addressed. These are judgment calls, not process decisions, rarely visible in dashboards and often intangible in the moment, but they determine whether execution compounds or constrains.

Why Execution Systems Differ Across Platforms

Two platforms can pursue similar strategies, acquire similar assets, and employ equally capable leaders and still show radically different execution quality. The difference lies in system configuration. Platforms that compound execution pace integration relative to capacity, delay irreversible standardization, preserve learning loops under load, and tolerate controlled variation. Platforms that plateau stack integrations aggressively, standardize early to regain control, sacrifice learning for stability, and reward predictability over adaptability. These patterns are rarely intentional. They emerge from responses to pressure, and they are why outcomes diverge across platforms running the same playbook, the heterogeneity the resource-based account exists to explain. The earliest of these forces, integration as an absorption problem, is set out in Why Integration Fails and From Integration to Execution.

Seeing the System Clearly

Execution is hard to manage precisely because it is emergent. There is no single lever; improvements in one area often create strain in another, and stability gained through standardization may cost adaptability while speed gained through control may slow learning. The goal is not optimization. It is balance under load. Organizations that hold execution quality over time do not eliminate tension. They manage it consciously. Understanding execution as a system explains why early success does not guarantee durability, why discipline can coexist with stagnation, and why execution quality is so difficult to transplant. That sets up the final reframing, because once execution is a system, its implications reach beyond operations into how the organization is understood, valued, and transferred at exit.

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Helfat, C. E., & Peteraf, M. A. (2003). The dynamic resource-based view: Capability lifecycles. Strategic Management Journal, 24(10), 997–1010.

March, J. G. (1991). Exploration and exploitation in organizational learning. Organization Science, 2(1), 71–87.

Related in the Thesis Notebook:

Absorptive Capacity under Cumulative Load · Resource-Based View Revisited

Related in this section:

When Execution Becomes Defensive · Learning Breaks Before Performance Does · Standardization Is a One-Way Door · From Integration to Execution · Why Integration Fails

What Target Selection Actually Fixes in Place

Every acquisition embeds assumptions into the organization, often without explicit acknowledgment. It determines how tightly decisions will be coupled, how much leadership attention will be consumed, how quickly complexity will compound, where uncertainty will reside, and how much optionality will remain once momentum builds. These outcomes are not driven primarily by integration quality. They are shaped by what the organization chooses to absorb, and when. Target selection fixes the shape of the future operating problem even when the details remain unknown.

Design Under Constraint, Not Optimization

Selection does not occur under ideal conditions. Opportunity sets are constrained by timing, market cycles, seller readiness, and competition, so leaders rarely choose from a wide menu of perfectly aligned options. But constraint does not remove agency. It relocates it. In constrained environments the most important decisions are not about selecting the best target but about how the system will interact with what is available. Fit, distance, diligence, and early signals are not filters that produce the right answer. They are lenses that determine how much strain, ambiguity, and irreversibility the system will inherit. Target selection is not about correctness. It is about consequence, because a target’s value is buyer-specific and turns on the platform’s capacity to deploy resources against it (Kaul & Wu, 2016).

How the Pieces Fit Together

Seen together, the section’s essays describe a single design logic. Fit determines interaction risk, not ease, because compatibility reduces friction while often increasing coupling, the question opened in Why We Acquire: Motives Before Targets and From Identification to Selection. Distance shapes the timing of commitment, since preserved distance delays irreversibility and protects learning. Diligence compresses uncertainty rather than resolving it, deciding where ambiguity will live next. And early signals reveal tendencies before the system hardens, so ignoring them is an active choice about future strain. None of these operates independently. Together they define the architecture of the post-close system, which is already carrying load by the time integration begins.

Why Integration Is a Poor Place to Fix Design Errors

Many post-mortems focus on execution: integration was rushed, governance unclear, bandwidth stretched, synergies slow. These diagnoses are often accurate and incomplete. Integration does not fail in isolation. It fails when the system it inherits is already over-coupled, under-buffered, and carrying unresolved uncertainty. At that point execution becomes compensatory rather than additive, leaders rely on effort instead of structure, and workarounds replace learning until performance holds only until it does not. The mistake was not in integration. It was in what the system was asked to absorb.

Target Selection as a Commitment Decision

Every acquisition commits the organization structurally, through coupling and decision rights; temporally, through sequencing and irreversibility; and cognitively, through assumptions about what is now known. These commitments are made early, compound quietly, and are hard to unwind once momentum takes over, because the resources and routines they set in motion accumulate along path-dependent flows that cannot be reversed at will (Dierickx & Cool, 1989). What makes them binding is that they rarely look like commitments when made; they enter as assumptions about how often leaders will intervene and how much ambiguity the organization can tolerate while still moving. Once embedded, those assumptions harden into operating facts. By the time strain is felt, the organization is no longer deciding whether to carry these commitments but how to survive them. Selection converts uncertainty into obligation long before it converts strategy into results.

The Design Question Beneath Selection

Viewed this way, the central question shifts. It is no longer whether this is a good business, nor even whether it fits the strategy. It becomes: what kind of system will this force us to become next? That question has no single correct answer, but ignoring it guarantees that design decisions will be made implicitly, through momentum, familiarity, and process rather than judgment. Selection does not reward certainty. It rewards clarity about constraint, which is also why the research treats the pre-deal phase as an unfolding process rather than a one-time event (Welch et al., 2020).

Why This Closes the Section

The purpose of this section has not been to refine filters or improve screening. It has been to show that selection is where buy-and-build systems are quietly shaped, often before leaders realize design decisions are being made at all. Once targets are chosen, distance collapses, diligence concludes, and signals are discounted, the system moves forward with its architecture largely fixed, and everything that follows, integration strain, leadership overload, sequencing fragility, even exit outcomes, unfolds from that starting design. The deeper logic of why accumulated resources, not individual assets, decide outcomes is the subject of the resource-based account.

Looking Ahead

If target selection is system design, then integration is not the execution of a plan. It is the first test of the design choices already embedded. The next section examines what happens when those designs meet operating reality, where structure meets capacity and strategy meets absorption limits.

References

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Kaul, A., & Wu, B. (2016). A capabilities-based perspective on target selection in acquisitions. Strategic Management Journal, 37(7), 1220–1239.

Welch, X., Pavićević, S., Keil, T., & Laamanen, T. (2020). The pre-deal phase of mergers and acquisitions: A review and research agenda. Journal of Management, 46(6), 843–878.

Related in the Thesis Notebook:

The Pre-Deal Phase and Target Selection · Resource-Based View Revisited

Related in this section:

Early Signals Are Not Noise · Diligence Does Not Eliminate Uncertainty · Distance Is a Design Variable · From Identification to Selection · Why We Acquire: Motives Before Targets

Optimization Under Constraint

All systems optimize, regardless of stated intent. Optimization does not require a conscious objective function; it emerges through selection pressure, as decisions that reduce friction are rewarded and those that increase strain are deferred, reshaped, or quietly abandoned. Early in a strategy the constraints are external, namely capital, deal flow, and market structure, and under those conditions growth and acquisition volume feel like the natural objectives because the system still carries slack. As the platform matures, constraints move inward: leadership bandwidth tightens, integration capacity saturates, coordination costs rise, and tolerance for disruption falls. The system’s behavior changes even if the language around it does not. Buy-and-build does not stop optimizing. It begins optimizing for what it can reliably carry, and what it can carry is bounded by the managerial capacity it can supply to absorb expansion (Penrose, 1959).

The Real Objective Function

Once complexity accumulates, platforms implicitly optimize for a different set of outcomes: absorbability (can this be integrated without destabilizing what exists?), coordination efficiency (can decisions be executed without overwhelming leadership attention?), continuity (can performance hold while change is introduced?), and predictability (can outcomes be kept within acceptable variance rather than maximized in theory?). None of these appear as headline metrics, yet all of them govern which deals get done and how. The shift is rarely acknowledged because it is not chosen deliberately. No board votes to prioritize absorbability over growth. The system simply rewards decisions that reduce internal friction, and over time that selection pressure reshapes behavior. The strategy still sounds the same. Its operating logic is not.

Why Compounding Stops Before Failure Appears

One of the most confusing features of buy-and-build is that compounding often stops long before anything appears broken. Early integrations benefit from conditions that do not persist: excess leadership attention, informal coordination that still functions, slack in systems, and the goodwill of novelty. Those conditions let the organization compensate for structural gaps through effort. Over time effort stops scaling. Experience continues to accumulate, but capacity does not, because the capacity to absorb new resources depends on related knowledge and spare attention that load consumes (Cohen & Levinthal, 1990). This is why later acquisitions feel heavier than earlier ones even as the organization grows larger and more experienced. Compounding has stalled, not because the strategy failed but because the system has reached its absorption limit, the dynamic developed in the absorptive-capacity note and in Integration Capacity Is the Binding Constraint.

Optionality and Irreversibility as Deferred Load

Flexibility is widely treated as a virtue: integration can wait, structures can stay light, decisions can be framed as reversible. But optionality is not free. Every deferred decision must be carried somewhere, and in buy-and-build it is carried as ambiguity about roles, authority, integration depth, and operating norms, consuming leadership bandwidth until leaders become the integration layer rather than converting complexity into capability. What began as flexibility quietly becomes load (The Hidden Cost of Optionality develops this). The mirror image is irreversibility. Many decisions cannot be undone, not because they are formally locked in but because reversing them would require more coordination and disruption than the organization can tolerate once it has moved on, the boundary at which a staged commitment stops behaving like a freely exercisable option (Adner & Levinthal, 2004; Irreversibility in Buy-and-Build Systems).

Strategy Drift Without Abandonment

As optionality accumulates and irreversibility hardens, the platform experiences a subtle but profound shift: the strategy does not change, but its behavior does. Selection criteria adapt under load, easier-to-absorb targets advance, integration principles bend to preserve momentum, and governance thickens. Each adaptation is locally rational; together they produce a different strategy. This is strategy drift, not a loss of focus but an emergent property of a system optimizing under constraint, and it is the realised-versus-intended distinction at the level of the whole platform (Mintzberg & Waters, 1985; Strategy Drift in Serial Acquisition Platforms). Because performance often stays acceptable, drift rarely triggers alarm even as it narrows the range of futures the platform can pursue.

When Optimization and Narrative Diverge

This is where tension emerges. Externally the platform still describes itself in aspirational terms, expansion, capability building, adjacency capture, while internally decisions are filtered through load, disruption, and coordination cost. The divergence is not hypocrisy. It is adaptation. The danger lies in mistaking the narrative for the operating reality, believing the system is still optimizing for growth when it is optimizing for survival. When the shift goes unrecognized, leaders push for outcomes the system can no longer deliver, integrations feel heavier despite experience, and diagnosis focuses on execution rather than constraint.

Survival Is Not Failure

It is worth being precise. Optimizing for absorbability, coherence, and continuity is not inherently negative; in many cases it is exactly what lets a platform endure. Survival is not a moral failure or evidence of weak leadership. The problem is not what the system optimizes for. It is whether leaders understand that it has changed. When they recognize the shift, they can align ambition with capacity, choosing when to consolidate, when to pause, and when to redesign the system before pushing further. When the shift goes unrecognized, the gap between intent and behavior widens and frustration accumulates.

Reframing Buy-and-Build Success

Seen clearly, buy-and-build is not a strategy that maximizes growth. It is a strategy that tests whether an organization can convert growth into durable coordination capacity faster than complexity consumes it, an accumulation of hard-to-trade resource stocks rather than a sum of deals (Dierickx & Cool, 1989), which is the resource-accumulation logic at the heart of the resource-based account. Platforms that succeed do not avoid constraint; they redesign themselves around it and adjust ambition when the system’s optimizing logic shifts. Those that struggle rarely fail dramatically. They keep acquiring, integrating, and performing while quietly narrowing the futures they can pursue without breaking coherence. Understanding this does not produce a playbook. It produces judgment. Buy-and-build does not reward cleverness in isolation. It rewards clarity about what the system can, and cannot, carry next. The next essay turns to the exit, where that clarity is finally priced.

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Mintzberg, H., & Waters, J. A. (1985). Of strategies, deliberate and emergent. Strategic Management Journal, 6(3), 257–272.

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 · Real Options and Buy-and-Build · Deliberate and Emergent

Related in this section:

Strategy Drift in Serial Acquisition Platforms · The Hidden Cost of Optionality · Irreversibility in Buy-and-Build Systems · Integration Capacity Is the Binding Constraint

Most organizations experience growth first as relief. New revenue covers inefficiencies, scale absorbs mistakes, and performance improves even as coordination becomes more complex. Early in a buy-and-build journey, growth often masks underlying fragility rather than exposing it. There is an old reason for this: a firm can only grow as fast as it can supply the managerial capacity to absorb the expansion, and growth that outruns that capacity does not build advantage so much as borrow against it (Penrose, 1959), the same limit the Notebook develops as the resource-based account of how platforms actually compound.

Operators feel the tension early. They sense the organization moving faster than it is stabilizing: processes lag, decision rights blur, integration work stretches longer than expected. But results stay strong enough that raising concerns feels unnecessary, even obstructive. Growth provides cover. From a deal team’s perspective the signals reinforce confidence, because the platform is expanding, synergies look achievable, and the strategy is being executed. Stability, by contrast, can look like hesitation, time spent consolidating rather than deploying capital.

But stability is not the absence of motion. It is the presence of coherence. Stability means roles are clear enough for decisions to decentralize rather than concentrate, that integrations are absorbed rather than endured, and that learning accumulates faster than complexity. None of those outcomes show up in topline metrics, and all of them depend on the capacity to metabolize what has already been taken on (Cohen & Levinthal, 1990), the dynamic examined in the absorptive-capacity note.

As a result, organizations often grow past their ability to create value. When growth outpaces stabilization, the system begins to leak. Leaders compensate through attention, teams solve problems informally, exceptions multiply, and performance still holds but the margin for error narrows. Value creation becomes increasingly dependent on effort rather than design, the bandwidth being spent in exactly the way described in the bandwidth-debt note.

This is not obvious from the outside. Growth creates a compelling narrative, reassures stakeholders, and validates prior decisions, and questioning it feels counterintuitive when markets reward expansion and patience is scarce. Yet many buy-and-build platforms do not fail because growth stops. They fail because growth continues while value creation quietly degrades. The symptoms appear later: margins plateau despite scale, integration costs persist, leadership turnover rises, decision quality declines. At that point organizations often try to reignite growth, mistaking stagnation for the problem rather than instability, which compounds the error.

Stability is misread as complacency because its benefits are indirect. It does not create excitement; it creates capacity. It lets the organization metabolize what it has already taken on and turns activity into advantage rather than exhaustion. The resources that actually carry value, namely reputation, routines, and integration capability, are accumulated through deliberate, path-dependent investment and cannot be conjured by adding revenue (Dierickx & Cool, 1989). Experienced operators understand this instinctively. They know pauses are not empty but productive: stabilization lets systems catch up to ambition, converts hard-earned experience into repeatable capability, and keeps leaders from becoming permanent bottlenecks.

For investors the distinction is harder but more important. Growth is easy to model and stability is not, yet stability determines whether growth produces durable value or transient performance. A platform that stabilizes deliberately can often grow faster later, because it is not constantly repairing itself. The paradox is that slowing down at the right moment frequently accelerates long-term outcomes. This does not mean avoiding growth. It means sequencing it, and recognizing that expansion without consolidation is not momentum but drift, which in complex systems is rarely neutral, as the companion note on how risk fails quietly argues.

Value creation depends on what remains after growth pressure subsides. If the organization is clearer, more capable, and better able to decide, growth has done its work. If it is more fragile, more centralized, and more dependent on a few individuals, growth has merely postponed a reckoning. Stability is not stagnation. It is the discipline that allows growth to mean something. In buy-and-build, the most valuable periods are often the least visible ones, the moments when the organization stops expanding just long enough to make sense of what it has already become.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

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:

Bandwidth Debt: The Cost Leaders Don’t See · Why Risk Rarely Fails Loudly

This note is about that capacity, and about why it does not scale with experience as smoothly as the plan assumes. The lens is absorptive capacity, the idea that a firm’s ability to take in and use new resources depends on what it already knows and can do. Read into a serial-acquisition setting, it explains a pattern the deal-by-deal view misses: integration capacity, not the supply of targets or capital, is usually the binding constraint on how fast a platform can grow, and under sustained load that capacity can plateau or even degrade.

What absorptive capacity is

Cohen and Levinthal (1990) introduced absorptive capacity to explain why some firms exploit external knowledge better than others. Their claim was that the ability to recognise the value of new information, assimilate it, and apply it depends on prior related knowledge. You cannot absorb what you have no foundation to understand, and that foundation is built by earlier learning. The idea was developed for innovation, but it maps cleanly onto acquisition. A platform’s ability to absorb an add-on, to fold its operations, people, and customers into the whole without breaking either, depends on the related capability it has already accumulated.

This connects directly to the resource-based account in the first note of this Notebook. If integration capability is a strategic asset built through path-dependent accumulation (Dierickx & Cool, 1989), absorptive capacity is the mechanism by which that asset is built and the limit on how fast it can be used. Each integration both draws down the platform’s capacity and, if handled deliberately, adds to it.

Why experience does not automatically compound

The assumption that experience compounds founders on the evidence. The relationship between acquisition experience and performance is U-shaped rather than linear: after a first deal, inexperienced acquirers over-generalise what they learned to dissimilar targets, and only with more experience do they learn to discriminate (Haleblian & Finkelstein, 1999). Experience can teach the wrong lesson as easily as the right one.

What separates platforms that learn from those that merely repeat is deliberateness. Capabilities improve when firms invest in articulating and codifying what they learn, not when they simply accumulate repetitions (Zollo & Winter, 2002), and integration capability specifically improves when experience is codified into tools and routines (Zollo & Singh, 2004). The capability can be built on purpose, through a dedicated M&A function and structured learning processes (Trichterborn et al., 2016), and successful serial acquirers develop a distinct capability in the identification and selection phase through structured feedback (Grant et al., 2022). None of this is automatic. It is the difference between a platform that runs a real post-deal review and one that does not.

The acquisition-programme perspective sharpens the point. Performance is best understood at the level of the programme rather than the single deal, and both the rate and the variability of acquisitions bear on it, moderated by the acquirer’s size, scope, and experience (Laamanen & Keil, 2008). Pace is not free.

Cumulative load: when capacity plateaus or degrades

Here is the part the optimistic plan omits. Absorptive capacity is finite at any moment, and integrations consume it: executive attention, the time of the few people who can actually run an integration, the bandwidth of shared functions. When integrations overlap, as they must in a platform acquiring on a cadence, they draw on the same constrained pool at once. If deals arrive faster than capacity rebuilds, the platform runs a deficit, and the symptoms look like integration debt: systems half-converged, acquired managers leaving, synergies booked in the model but not in the business. Integration is a process with strategic, sociocultural, and learning dimensions, not a one-off event (Graebner et al., 2017), and a process starved of attention degrades.

The capability can also decay outright. Capabilities have lifecycles; they are founded, they develop, and they can mature and decline (Helfat & Peteraf, 2003). Under sustained load, the integration capability that took three deals to build can erode in one overloaded year, as the experienced people who embodied it burn out or leave and the routines stop being maintained. Asset-mass efficiencies, the advantage of already holding a stock (Dierickx & Cool, 1989), run in reverse once the stock is drawn down faster than it is replenished. This is the mechanism behind the stall: not a shortage of targets or money, but a platform absorbing more than it can metabolise.

A worked illustration: the fourth add-on

Consider a platform, stylised but familiar, three add-ons into a building-products roll-up. The first three went well: each was integrated by the same small core team, onto a branch and procurement template that improved with every pass. Encouraged, and under pressure to deploy capital, the sponsor accelerates and signs two more add-ons to close in the same quarter as a delayed systems migration on the third.

The fourth add-on is, on paper, the best target yet. It still underperforms. The core integration team is now running three integrations at once and supervising a migration; the most capable operator is doing the work of two; the shared procurement function cannot onboard a fourth supplier base while re-platforming the third. Nothing is wrong with the target. The platform has simply exceeded its absorptive capacity, and the deficit shows up as the fourth deal’s shortfall and as slippage on the earlier deals it can no longer attend to. A year later, two of the original team have left, and the capability that made the first three work has to be rebuilt. The binding constraint was never the pipeline.

The objection: can’t you just add capacity?

The obvious rejoinder is managerial: if integration capacity is the constraint, hire more of it. Bring in operating partners, build a bigger integration team, professionalise the function. This is right as far as it goes, and the best platforms do exactly that. But it underestimates how much of the capacity is not purchasable on demand.

Absorptive capacity is partly tacit and relational. It lives in people who know the platform’s systems, in working relationships that took years to form, and in routines that are codified but never fully (Cohen & Levinthal, 1990; Zollo & Singh, 2004). You can add headcount, but you cannot add, in a quarter, the related knowledge that lets new hires absorb a target rather than merely staff it, because time-compression diseconomies make rapid accumulation expensive and imperfect (Dierickx & Cool, 1989). Worse, each addition raises coordination load, since a larger integration organisation is itself something to integrate. Capacity scales, but sublinearly, which is why pace, not just capability, has to be managed. The honest position is that capacity can be expanded deliberately and slowly, not summoned to match an opportunistic cadence.

Four propositions

Stated plainly, so they can be argued with and tested against cases:

1. Capacity is the binding constraint. In serial acquisition, integration capacity rather than target supply or capital usually limits how fast a platform can profitably grow.

2. Experience compounds only when deliberate. Acquisition experience improves performance only when it is codified into routines; raw repetition can entrench the wrong lessons.

3. Load degrades capability. Under sustained, overlapping integration load, absorptive capacity can plateau or decline, and the loss shows up as integration debt rather than as a single bad deal.

4. Capacity scales sublinearly. Integration capacity can be expanded deliberately but not on demand, because much of it is tacit, relational, and time-bound; added capacity also adds coordination load.

Why this matters

Read this way, the central management problem of buy-and-build is not finding the next deal but pacing acquisition to the rate at which capacity can absorb it. That is the operator-side argument of Integration Capacity Is the Binding Constraint, and it is the discipline the resource-based and target-selection notes both point toward: the resource that decides outcomes is the one that cannot be bought, and it can be exhausted. It also sets up the next note, on real options, which shows how the optionality language platforms borrow from finance tends to assume a reversibility and a spare capacity that, under cumulative load, are simply not there.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Graebner, M. E., Heimeriks, K. H., Huy, Q. N., & Vaara, E. (2017). The process of postmerger integration: A review and agenda for future research. Academy of Management Annals, 11(1), 1–32.

Grant, M., Nilsson, F., & Nordvall, A.-C. (2022). Pre-merger acquisition capabilities: A study of two successful serial acquirers. European Management Journal, 40(6), 932–942.

Haleblian, J., & Finkelstein, S. (1999). The influence of organizational acquisition experience on acquisition performance: A behavioral learning perspective. Administrative Science Quarterly, 44(1), 29–56.

Helfat, C. E., & Peteraf, M. A. (2003). The dynamic resource-based view: Capability lifecycles. Strategic Management Journal, 24(10), 997–1010.

Laamanen, T., & Keil, T. (2008). Performance of serial acquirers: Toward an acquisition program perspective. Strategic Management Journal, 29(6), 663–672.

Trichterborn, A., Zu Knyphausen-Aufseß, D., & Schweizer, L. (2016). How to improve acquisition performance: The role of a dedicated M&A function, M&A learning process, and M&A capability. Strategic Management Journal, 37(4), 763–773.

Zollo, M., & Singh, H. (2004). Deliberate learning in corporate acquisitions: Post-acquisition strategies and integration capability in U.S. bank mergers. Strategic Management Journal, 25(13), 1233–1256.

Zollo, M., & Winter, S. G. (2002).Deliberate learning and the evolution of dynamic capabilities. Organization Science, 13(3), 339–351.

What Leadership Debt Is, and Is Not

Leadership debt is not burnout, weak management, or a failure of governance. It is the future leadership capacity required to sustain operating choices made earlier. Like other forms of organizational debt it is incurred unintentionally, invisible while performance is strong, and difficult to unwind once embedded. It explains why platforms that look efficient early often feel constrained later, despite having more people, more structure, and more experience.

How Operating Models Borrow from Leadership

Buy-and-build operating models are designed under pressure. They have to integrate quickly, manage heterogeneity, preserve optionality, and deliver near-term results, and to do all of that, leadership effort is frequently used as a substitute for system maturity. Decisions are centralized to move faster, conflicts are resolved through senior judgment rather than process, exceptions are allowed to avoid friction, and work is sequenced opportunistically rather than deliberately. These choices are rational and often necessary. They also create obligations, because substituting personal effort for designed information-processing capacity only defers the coordination load rather than removing it (Galbraith, 1974).

Centralization as a Temporary Advantage

Centralized decision-making is one of the most common sources of leadership debt. Early on it reduces coordination cost, speeds execution, and ensures consistency across new acquisitions, with leadership absorbing complexity so the organization does not have to. Over time, the same centralization concentrates decision flow, delays learning at the edges, and increases dependence on senior judgment. What began as a speed advantage becomes a capacity constraint. The debt accrues not because centralization is wrong but because it is rarely unwound.

Exceptions That Never Return to the Rule

Exceptions are another quiet source of debt. In integration-heavy environments they preserve momentum: handle this case manually, this deal is different, standardize later. Leadership intervenes to resolve edge cases quickly, but exceptions create memory, requiring explanation, arbitration, and periodic re-justification. As they accumulate, leadership becomes the repository of organizational logic, and decisions increasingly depend on who remembers why something was done a certain way. Leadership effort replaces institutional knowledge.

Cadence That Accelerates Before It Stabilizes

Operating cadence often accelerates faster than learning stabilizes. Reporting cycles tighten, reviews become more frequent, meetings multiply, and leadership stays close to execution to manage risk. This creates responsiveness but also interruption, and leadership becomes the synchronizing mechanism for work that has not yet been modularized, stabilizing time through presence rather than structure. As cadence accelerates, leadership capacity is consumed just to keep the system coherent, which is the operating-system view set out in Operating Cadence Is a Leadership System. This is another form of borrowing.

Why Leadership Debt Compounds

Leadership debt compounds because the system adapts around it. As leadership becomes more central, teams escalate earlier, decisions wait for approval, and ambiguity is deferred upward. These adaptations preserve performance and increase future leadership demand, so each cycle makes leadership more indispensable and less scalable. By the time the debt becomes visible, it is no longer optional, because the system depends on it. Attention itself is the finite stock being drawn down, and it cannot simply be topped up by adding people (Cohen & Levinthal, 1990).

Why Leadership Debt Is Hard to Unwind

The debt is hard to repay because it is embedded in habits, expectations, and informal authority. Removing it requires slowing down, redistributing decision rights, tolerating short-term friction, and letting learning replace judgment, and these moves often feel like regressions, especially when performance has been strong. As a result the debt is rarely addressed directly. It is managed through substitution, by adding layers, inserting roles, and increasing oversight, and those responses shift the debt rather than eliminate it, because the stocks that would have to be rebuilt accumulate slowly and path-dependently (Dierickx & Cool, 1989).

Leadership Debt and the Illusion of Maturity

One paradox of leadership debt is that it often accumulates fastest in platforms that appear mature. Processes exist, governance is defined, performance is stable. What is less visible is how much leadership effort is required to keep those systems functioning. Maturity is not the presence of structure. It is the absence of leadership dependency, and leadership debt reveals itself precisely when leaders step back, or when ownership changes.

From Debt to Audit

Leadership debt does not cause immediate failure. It causes fragility, and fragility becomes visible under stress: overlapping integrations, leadership transitions, or exit. At that point the question is no longer whether leadership is strong but whether leadership capacity has been embedded or merely borrowed. The next essay examines how ownership change exposes leadership debt, and why buyers read leadership dependency as a structural risk, not a personal one.

Closing

Operating models do not just shape execution. They shape the future demand placed on leadership. Choices made to accelerate early performance often defer complexity rather than eliminate it, and leadership absorbs that complexity temporarily. Leadership debt accumulates quietly: created by success, reinforced by adaptation, revealed only when the system is tested. Understanding it is not about assigning fault. It is about recognizing leadership as a finite resource, and treating operating-model design as the mechanism that determines whether that resource compounds or constrains over time.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

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 Becomes a Bottleneck Before Performance Does · Authority Does Not Scale the Way Complexity Does · Operating Cadence Is a Leadership System

The Trigger: Learning Fatigue

Defensive execution emerges after learning has slowed. When an organization loses the capacity to absorb new insight without disruption, it begins to protect what already works. Exploration feels risky, exceptions feel dangerous, and reopening decisions feels expensive. At that point execution is no longer about improvement. It is about preservation. This is not a conscious choice; it is a rational response to sustained load, and it follows directly from the learning breakdown traced in the previous essay, where the slack that learning requires has already been consumed (Cohen & Levinthal, 1990).

How Defensive Execution Manifests

Defensive execution has a recognizable pattern. Variance is treated as risk: local discretion is reduced and standard responses are favored over situational judgment, so doing it the approved way matters more than doing it the right way. Escalation increases: decisions once made locally move upward, and leaders become checkpoints rather than enablers as bottlenecks form quietly. Metrics harden: KPIs shift from learning tools to enforcement tools, green dashboards become the objective, and missing a metric matters more than understanding why. Change becomes costly: adjustments require more approval, more coordination, more justification, and adaptation slows. None of this looks like failure. It looks like control.

A Short Illustration

A platform takes one bad integration surprise on its fifth add-on. The response is sensible: tighter approval gates, a standard playbook everyone must follow, and a rule that exceptions go to the operating committee. The next year runs smoothly. Then a genuinely good add-on appears that does not fit the playbook, and the platform passes on it, not because anyone judged it weak but because absorbing it would mean reopening the controls the team just installed. The discipline that prevented the last failure has quietly become the reason a good opportunity is declined. Nothing looks broken on the dashboard. The range of moves has simply narrowed.

Why Defensive Execution Feels Responsible

From the inside, defensive execution feels prudent. Leaders have lived through integration strain, seen small disruptions cascade, and know the cost of surprises, so tightening execution feels like protecting the organization from itself. That is why it is so hard to challenge: it is framed as professionalism, discipline, and risk management, and in the short term it often works. But it also locks the organization into a narrower range of future moves, the same loss of reversibility the optionality argument warned about (Real Options and Buy-and-Build draws the boundary).

The Illusion of Maturity

One of the most dangerous misreadings in buy-and-build is mistaking defensiveness for maturity. Mature execution absorbs variation without panic, adapts systems deliberately, uses metrics to learn rather than only enforce, and maintains optionality under pressure. Defensive execution suppresses variation, avoids reopening decisions, treats learning as disruption, and prioritizes stability over adaptability. From a distance the two can look identical. The difference becomes clear only when conditions change, because a capability that is no longer renewed has entered the decline phase of its lifecycle even as it still looks orderly (Helfat & Peteraf, 2003).

The Cost That Accumulates

Defensive execution accumulates cost quietly. Over time, opportunities are declined because they do not fit the system, integrations are sequenced conservatively to avoid strain, synergies are pursued only where risk is minimal, and leaders spend more time protecting performance than extending it. The organization does not stagnate immediately. It plateaus. Execution stays competent, but upside narrows, and the deliberate work of converting experience into renewed capability quietly stops (Zollo & Winter, 2002).

Why This Matters Systemically

Defensive execution is not a failure of leadership character. It is a system response to cumulative integration load, early standardization commitments, slowed learning loops, and constrained capacity. Once the posture sets in, reversing it is difficult: relaxing controls reintroduces uncertainty, encouraging exploration risks destabilization, and leaders who try to reopen the system often meet resistance, not because teams disagree but because the organization has learned to value safety over growth. This is the final stage before execution becomes structurally rigid, and it is the downstream cost the standardization essay flagged (Standardization Is a One-Way Door; the load behind it is examined in the absorptive-capacity note).

Looking Forward

Defensive execution does not announce itself as a problem. It announces itself as discipline, and its consequences appear later, when the organization is evaluated not on past performance but on its ability to adapt, integrate, and operate under new conditions. Those implications are addressed in the capstone and exit lens that follow. For now the insight is clear. Execution does not fail when it becomes defensive. It fails when defensiveness becomes the operating mode.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Helfat, C. E., & Peteraf, M. A. (2003). The dynamic resource-based view: Capability lifecycles. Strategic Management Journal, 24(10), 997–1010.

March, J. G. (1991). Exploration and exploitation in organizational learning. Organization Science, 2(1), 71–87.

Zollo, M., & Winter, S. G. (2002). Deliberate learning and the evolution of dynamic capabilities. Organization Science, 13(3), 339–351.

Related in the Thesis Notebook:

Absorptive Capacity under Cumulative Load · Real Options and Buy-and-Build

Related in this section:

Learning Breaks Before Performance Does · Standardization Is a One-Way Door

Why Early Signals Are Easy to Ignore

Early signals are weak by definition. They are ambiguous, they lack context, they conflict with the investment thesis, and they do not fit cleanly into diligence frameworks or operating dashboards. Most importantly, they surface before the organization has decided where uncertainty will live. After diligence concludes and commitment accelerates, the system orients toward execution, and attention shifts from interpretation to delivery. In that posture weak signals feel like distractions rather than inputs. Ignoring them feels disciplined. It is not. The research on the pre-deal phase makes the same point structurally, treating selection as an unfolding process rather than a one-time event whose questions close at signing (Welch et al., 2020).

Signals as Pre-Commitment Information

Early signals matter precisely because they appear before the system hardens. They emerge before integration plans are locked, before leadership bandwidth is fully allocated, and before roles, expectations, and decision rights are fixed. At this stage the organization still has degrees of freedom: small adjustments are possible, boundaries can be clarified, pace can be moderated. Once integration accelerates, those options narrow. Early signals are not forecasts. They are directional indicators of how the system will behave under load. They do not predict outcomes; they reveal tendencies.

The Misclassification Problem

The most common mistake is not ignoring signals. It is misclassifying them. Signals are often dismissed because they cannot be proven, but proof is the wrong standard, because early signals are not evidence, they are conditions. A leadership team that avoids conflict early is unlikely to become decisive under pressure. An organization that struggles to deliver basic information on time will not improve when complexity increases. A founder who resists transparency before close will not embrace it after authority shifts. These are not certainties; they are trajectories, and the behavioral-learning evidence is that experience teaches discrimination only when these patterns are read rather than over-generalized away (Haleblian & Finkelstein, 1999). Treating signals as noise does not make them disappear. It delays recognition until the system has fewer ways to respond.

Why Institutions Struggle with Signals

Institutional processes are poorly designed to handle early signals. Investment committees reward clarity, diligence rewards documentation, and integration planning rewards decisiveness. Signals disrupt all three, introducing ambiguity at the moment the organization is trying to converge, and raising them can feel like reopening questions diligence has already settled. As a result signals are noted but not elevated, discussed but not built into decisions, acknowledged but not allowed to slow momentum. The system moves forward not because the signals were weak but because responding to them felt inconvenient. There is also a confidence trap: the more thorough the process feels, the more readily decision-makers assume anything still unresolved must be minor (Roll, 1986).

Signals and the Illusion of Progress

Early signals are often masked by progress. Revenue grows, customers stay, integration milestones are met, and these create confidence that whatever felt uncertain has resolved or was never material. But progress can coexist with fragility. In buy-and-build, performance often holds while underlying strain accumulates, because signals are absorbed through extra effort, informal workarounds, and leadership heroics. This creates a dangerous loop: early signals are discounted, the system compensates, results stay acceptable, confidence rises, and the next signals are dismissed faster. By the time performance degrades, the system has already lost flexibility, the cumulative-load dynamic developed in the absorptive-capacity note.

Responding to Signals Without Overreacting

Taking early signals seriously does not mean acting on every concern. The goal is not responsiveness; it is registration. Strong platforms do not treat signals as triggers, they treat them as inputs into design, asking what a signal suggests about interaction risk, where it would surface under load if it persists, what assumptions it challenges, and what flexibility should be preserved as a result. Sometimes the right response is adjustment, sometimes pacing, sometimes simply refusing to collapse distance too early. Ignoring signals is a choice. So is preserving room to learn from them.

Signals as a Bridge Between Selection and Integration

Early signals sit at the boundary between target selection and integration. They are often the last information available before decisions become operationally binding, because once integration accelerates the system becomes less capable of reflection. This is why they deserve disproportionate attention: they arrive when the cost of response is lowest and the cost of dismissal is highest. Signals do not become clearer with time. They become louder, and louder signals are harder to respond to without disruption. This is the same handoff the previous essay set up, where diligence reshapes uncertainty rather than resolving it (Diligence Does Not Eliminate Uncertainty, and the boundary it draws in The Limits of Diligence).

Why This Matters for Target Selection

Target selection does not end at close. It continues through how early signals are interpreted, elevated, and acted upon, and ignoring them is not neutrality but an implicit decision to carry that uncertainty forward unchanged. In constrained environments leaders rarely have perfect information, and early signals are often the only indication that something important is misaligned. Treating them as noise does not preserve objectivity. It preserves momentum.

What Comes Next

Early signals reveal tendencies, not outcomes, but tendencies shape what becomes possible as the system evolves. The final essay in this sequence brings the threads together, fit, distance, diligence, and signals, to show how target selection is the first irreversible system-design decision, long before integration begins, which is the argument the target-selection note develops at the level of theory.

References

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Haleblian, J., & Finkelstein, S. (1999). The influence of organizational acquisition experience on acquisition performance: A behavioral learning perspective. Administrative Science Quarterly, 44(1), 29–56.

Roll, R. (1986). The hubris hypothesis of corporate takeovers. The Journal of Business, 59(2), 197–216.

Welch, X., Pavićević, S., Keil, T., & Laamanen, T. (2020). The pre-deal phase of mergers and acquisitions: A review and research agenda. Journal of Management, 46(6), 843–878.

Related in the Thesis Notebook:

The Pre-Deal Phase and Target Selection · Absorptive Capacity under Cumulative Load

Related in this section:

Diligence Does Not Eliminate Uncertainty · The Limits of Diligence

Drift Without Decision

Drift is often framed as a failure of discipline: chasing too many opportunities, deviating from core principles, losing focus. In a platform that framing is incomplete, because drift occurs even when leadership stays committed and aligned. It emerges because serial acquisition changes the conditions under which decisions are made. Each acquisition reshapes the system, its constraints, interfaces, and priorities, and over time the organization adapts locally to manage complexity. Those adaptations accumulate into global change. No single decision causes drift. It is the sum of many reasonable responses to immediate pressure. This is the realised-versus-intended distinction at the heart of strategy itself: what an organization actually does is part deliberate and part emergent, formed through a stream of decisions rather than a single plan (Mintzberg & Waters, 1985), the same lens the Notebook applies to the add-on thesis in Deliberate and Emergent.

How Drift Enters the System

Drift enters through mechanisms that feel operational rather than strategic. Target selection shifts under constraint: as integration load rises, deals that fit the original thesis but strain the system are deferred, easier-to-absorb targets move up the list, and the platform gradually acquires what it can handle rather than what it set out to build. Integration principles bend to preserve momentum, exceptions multiply, and temporary accommodations persist until the integration model has evolved by necessity rather than design. Leadership attention reallocates toward what can be resolved quickly, so long-horizon capability building gives way to near-term stabilization. Governance is added to manage complexity, cadence tightens, and escalation paths multiply. Each adjustment makes sense in isolation. Together they produce a strategy that behaves differently than intended, which is exactly why performance is best judged at the level of the acquisition programme rather than the single deal (Laamanen & Keil, 2008).

A Short Illustration

A platform sets out to consolidate the strongest independents in its category. Its first three add-ons fit. By the fourth, the integration team is stretched, so a clean-but-complex target is passed over for a smaller one that bolts on easily. The same logic repeats twice more. Two years on, the platform owns a portfolio of easy-to-absorb businesses rather than the category leaders its thesis named, and no meeting ever decided to change the thesis. Each pass was the right call under the load of that quarter. The strategy drifted through a series of locally rational selection choices, which is why it never felt like a decision at all.

Why Drift Feels Rational at Every Step

Drift persists because it is locally optimal. At each decision point leaders are not choosing between strategy and drift; they are choosing between viable options under constraint, and the system rewards decisions that reduce immediate friction and penalizes those that add load, even when the latter align better with long-term intent. This is why drift rarely triggers alarm. Performance may stay acceptable, growth continues, metrics look fine, and there is no obvious failure to correct. The strategy has not been rejected. It has been reinterpreted through the lens of capacity.

The Role of Optionality and Irreversibility

The previous essays showed how optionality accumulates load and how commitments become irreversible. Drift is where those dynamics converge. Optionality delays commitment and increases ambiguity; irreversibility locks in the adaptations made under pressure, the boundary at which a staged commitment stops behaving like a freely exercisable option (Adner & Levinthal, 2004). Together they narrow the feasible strategy set, and over time the organization stops choosing among strategic alternatives and starts operating within the path it has already created, a path-dependence that the resources and routines accumulated along the way make costly to leave (Dierickx & Cool, 1989). Drift is not a loss of control. It is control exercised under shrinking degrees of freedom.

When Drift Becomes Visible

Drift usually becomes visible only in hindsight. The signals are recognizable: the platform no longer pursues the opportunities it once called core; value creation leans more on cost management than capability expansion; acquisitions are justified as adjacent in increasingly loose terms; leadership describes the business as complex rather than building. By the time these are explicit, the system has often adapted too far to revert easily. The strategy can be restated, but not reinstated without significant disruption.

Why Drift Is So Hard to Reverse

Reversing drift requires capacity the organization no longer has. To realign with original intent, the platform would have to absorb additional integration work, unwind accommodations made to preserve momentum, reallocate leadership attention away from stabilization, and tolerate short-term performance volatility. These are precisely the things the system has evolved to avoid, which is why many platforms live with drift, not because it is desirable but because the alternative feels riskier than continuing on the current path.

Managing Drift Without Pretending It Can Be Eliminated

Drift cannot be eliminated in a serial-acquisition system. It can only be managed, and managing it starts from recognizing that strategy is not only articulated but enacted through thousands of small decisions made under constraint. The relevant question is not whether drift exists but whether it is occurring within acceptable bounds. That means periodically asking how the system has changed the strategy we think we are executing, which adaptations are intentional and which are merely tolerated, and what choices we would make differently if capacity were not the binding constraint. These questions do not guarantee correction, but they make drift visible before it becomes irreversible.

The next essay shifts to a deeper reframing: if buy-and-build is not primarily optimizing for growth, speed, or deal volume, what is it optimizing for instead?

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Dierickx, I., & Cool, K. (1989). Asset stock accumulation and sustainability of competitive advantage. Management Science, 35(12), 1504–1511.

Laamanen, T., & Keil, T. (2008). Performance of serial acquirers: Toward an acquisition program perspective. Strategic Management Journal, 29(6), 663–672.

Mintzberg, H., & Waters, J. A. (1985). Of strategies, deliberate and emergent. Strategic Management Journal, 6(3), 257–272.

Related in the Thesis Notebook:

Deliberate and Emergent: How the Add-On Thesis Forms · Real Options and Buy-and-Build

Related in this section:

The Hidden Cost of Optionality · Irreversibility in Buy-and-Build Systems

This is why risk is so persistently misunderstood. Most organizations look for it where it is easiest to observe: pricing errors, leverage, customer concentration, execution misses. Those risks matter, but they are rarely the ones that undo otherwise sound platforms. The more consequential risks sit between decisions rather than inside them. They live in interaction effects, and a sequence of individually sensible investments is not the same as a portfolio of cleanly separable, reversible options (Adner & Levinthal, 2004).

As acquisitions accumulate, so do small mismatches: between governance and scale, between integration demands and leadership capacity, between strategic intent and operating reality. None is fatal on its own. Each can be managed, worked around, or deferred. Together they reshape the system in ways that are difficult to reverse. The danger is not that the risks are unknown. It is that they are normalized.

Early success plays a central role in that normalization. When results are strong, organizations update their beliefs about what is safe, tolerance for strain rises, and what once felt risky begins to feel routine. The system adapts not by becoming more resilient but by becoming more permissive. This is the quiet face of overconfidence, the well-documented tendency for past success and managerial conviction to inflate what acquirers believe they can absorb (Roll, 1986).

Operators recognize the pattern intuitively. They feel when the organization is leaning more heavily on informal coordination, when leaders are intervening more often, when problems are solved through effort rather than design. These signals rarely trigger alarms; they are framed as the natural cost of growth. From the outside the picture looks reassuring. Performance holds, the thesis still works, integration milestones are met, risk models stay within bounds. Deal teams see continuity where operators feel mounting strain, and because no single decision looks reckless, the system appears safe.

This is the quiet failure mode. Risk in buy-and-build does not usually arrive as a shock. It arrives as a series of small accommodations. Governance flexes temporarily. Integration standards loosen just this once. Leaders stretch a little further than planned. Learning is postponed in favor of speed. Each accommodation buys time and consumes margin, and margin, once spent, is the capacity the system no longer has to absorb the next surprise (Cohen & Levinthal, 1990). Over time the system becomes more fragile without ever appearing fragile.

When problems finally surface, attribution becomes difficult. Was it the last acquisition, the integration team, market conditions, leadership turnover? In truth the breakdown reflects accumulated exposure rather than a single cause. Risk has been compounding out of sight. This is why corrective action is so often misdirected: organizations tighten controls, replace people, or revisit strategy, and these responses may address symptoms but rarely unwind the interaction effects already embedded in the system. By then optionality has narrowed, and choices that once existed are no longer available.

Experienced operators understand the asymmetry. Preventing quiet risk accumulation means slowing down before the metrics demand it, treating early strain as information rather than noise, and resisting the comfort of surface-level success to ask what the system is silently absorbing. The same discipline runs through the companion note on bandwidth debt, where leadership capacity is the margin being spent.

For investors this is a challenge, because quiet risk does not show up cleanly in a data room or on a dashboard. It reveals itself through patterns: rising decision centralization, persistent integration exceptions, dependence on a few individuals, declining learning velocity. None of these invalidates a deal on its own. Together they warrant attention. The goal is not to eliminate risk, which is neither possible nor desirable. The goal is to keep risk from becoming invisible, because invisible risk is the hardest to manage.

In buy-and-build, the most dangerous risks are rarely the ones debated explicitly. They are the ones embedded gradually, accepted incrementally, and recognized only in hindsight. Risk fails quietly because systems allow it to. Organizations that learn to surface these signals early do not avoid volatility entirely, but they reduce the likelihood that success itself becomes the mechanism of failure. In environments defined by accumulation rather than singular bets, paying attention to how risk hides is as important as knowing where to look for it.

References

Adner, R., & Levinthal, D. A. (2004). What is not a real option: Considering boundary conditions for the application of real options to business strategy. Academy of Management Review, 29(1), 74–85.

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

Roll, R. (1986). The hubris hypothesis of corporate takeovers. The Journal of Business, 59(2), 197–216.

Related in the Thesis Notebook:

Real Options and Buy-and-Build · Absorptive Capacity under Cumulative Load

Related in this section:

Bandwidth Debt: The Cost Leaders Don’t See · When Discipline Feels Conservative but Is Enabling

There are two ways buy-and-build is run, and the distinction matters. In the first, a predefined roll-up thesis drives everything: a sponsor commits to consolidating a fragmented sector and then selects a platform and add-ons to execute that plan. In the second, the sponsor acquires a promising platform first and constructs the add-on thesis afterwards, refining it as the hold period unfolds. The platforms worth studying are mostly the second kind, and it is in that mode that the gap between plan and reality is widest. This note uses process theory to describe how the thesis really forms.

Deliberate and emergent strategy

The cleanest language for this comes from Mintzberg and Waters (1985), who distinguished deliberate strategy, the part that is intended and realised as planned, from emergent strategy, the part that forms through a stream of decisions in the absence of, or despite, intention. Real strategies, they argued, are neither purely one nor the other but lie on a continuum, and the most useful mode for an uncertain environment is what they called an umbrella strategy: leadership sets broad boundaries and lets the specifics emerge within them. A platform-first buy-and-build is an umbrella strategy almost by definition. The sponsor sets a direction, consolidate around this platform in this sector, and the realised sequence of add-ons emerges from the opportunities that actually arrive.

Why this needs process theory

Describing how a thesis forms over time requires tools built for sequences, not snapshots. Process research treats organisational phenomena as sequences of events whose order and timing carry explanatory weight, rather than as variables measured at a point (Langley, 1999; Van de Ven & Poole, 1995). It also insists on moving from narrative to mechanism: a chronology of what happened is only the surface, and explanation requires the generative structure beneath it (Pentland, 1999). This is exactly what the target-selection literature lacks. The pre-deal phase has been modelled as a discrete, static event rather than an unfolding process (Welch et al., 2020), which is precisely the framing a process account of buy-and-build has to replace.

The acquisition-programme perspective supplies the link to performance. The right unit of analysis is the programme, not the single deal, and both the rate and the variability of acquisitions across the sequence bear on how it performs (Laamanen & Keil, 2008). Selection criteria, on this view, are not fixed inputs; they are outputs of a process that updates with each deal.

A worked illustration: the thesis that bent

Take a platform that begins with a clear deliberate thesis: consolidate independent installation contractors in a regional building-products market, betting that scale in labour and scheduling will lift margins. The first two add-ons are chosen to fit that plan. They also teach the platform something its plan did not contain: the real margin pressure, and the real source of customer loyalty, sits upstream in distribution, not in installation labour.

A purely deliberate platform ignores this and keeps buying installers. A purely opportunistic one chases whatever is for sale. The platform that does well does neither: it keeps the umbrella, consolidation in this region, but bends the thesis toward owning distribution, and its next add-ons are distributors rather than installers. The realised strategy is part deliberate, the regional consolidation held throughout, and part emergent, the shift to distribution learned from the first deals. Neither the original plan nor pure opportunism would have produced it.

The objection: isn’t this just undisciplined drift?

The sharp objection is that emergent strategy is a flattering name for a lack of discipline, a way to dignify chasing deals and rationalise it after the fact. The risk is real, and it is the same hazard the target-selection note raised: a flexible thesis can excuse buying whatever appears. But the deliberate-emergent distinction is not a licence to drift; it is a description of where the discipline has to sit. In an umbrella strategy the boundaries are firm even though the specifics are open, and the test of a well-run emergent process is whether the thesis updates through structured learning, post-deal reviews that change the criteria, rather than through opportunism that merely reacts. Mintzberg and Waters (1985) themselves separate emergent strategy, which is coherent even though unplanned, from what they call unconnected strategy, which is not. The discipline of a platform-first roll-up is not a fixed plan; it is a governed process for revising the plan, and a platform that cannot tell the difference between learning and drifting will not survive either.

Four propositions

Stated plainly, so they can be argued with and tested against cases:

1. Thesis as output, not input. In platform-first buy-and-build, the add-on thesis is built and revised across the hold period; selection criteria are outputs of a process, not fixed inputs.

2. Realised strategy is mixed. The realised sequence of add-ons is part deliberate and part emergent, and treating it as either pure plan or pure opportunism misdescribes it.

3. Process carries the explanation. The order and timing of early deals shape which later deals are seen and chosen, so selection must be studied as a sequence, not a discrete event.

4. Discipline is in the updating. Emergent strategy is disciplined when the thesis updates through structured learning within firm boundaries, and undisciplined when it merely reacts to what is for sale.

Why this matters

Seeing the add-on thesis as a deliberate-emergent process explains something the tidy story cannot: why two sponsors who buy the same platform end up with different companies. The difference is not the plan they started with but the process by which they revised it. This is the connective tissue of the Notebook. The resource-based view says advantage accumulates across the sequence; the target-selection note says each choice embeds the next; and process theory says the criteria themselves evolve. For the dissertation this is the central claim, that target selection in buy-and-build is a path-dependent, recursive process rather than a series of independent fit judgments, and the rest of the empirical work exists to trace how that process actually runs.

References

Langley, A. (1999). Strategies for theorizing from process data. Academy of Management Review, 24(4), 691–710.

Laamanen, T., & Keil, T. (2008). Performance of serial acquirers: Toward an acquisition program perspective. Strategic Management Journal, 29(6), 663–672.

Mintzberg, H., & Waters, J. A. (1985). Of strategies, deliberate and emergent. Strategic Management Journal, 6(3), 257–272.

Pentland, B. T. (1999). Building process theory with narrative: From description to explanation. Academy of Management Review, 24(4), 711–724.

Van de Ven, A. H., & Poole, M. S. (1995). Explaining development and change in organizations. Academy of Management Review, 20(3), 510–540.

Welch, X., Pavićević, S., Keil, T., & Laamanen, T. (2020).The pre-deal phase of mergers and acquisitions: A review and research agenda. Journal of Management, 46(6), 843–878.

Why Leadership Bottlenecks Are Hard to See

Leadership bottlenecks do not present as visible constraints. They do not announce themselves through missed targets or operational failures. Instead they surface as subtle changes in how the organization functions: decisions take longer to resolve, escalations increase, coordination needs more senior involvement, learning loops slow, and exceptions proliferate. None of these necessarily impairs performance in the short term. Platforms often keep growing while leadership capacity is already saturated, because strong teams compensate, leaders stretch, and informal coordination fills gaps. That adaptive capacity is precisely what delays recognition of the bottleneck.

The Illusion of Headroom

Buy-and-build creates the illusion of leadership headroom. Early success reinforces the belief that leadership capacity expands with scale: leaders handle more, systems look resilient, performance improves. What is actually happening is load redistribution, not capacity expansion. Leadership absorbs increasing volumes of unresolved novelty, exception handling, arbitration between competing priorities, and sequencing decisions authority cannot predefine. As long as leaders can absorb this load, performance holds. But capacity is finite, and the binding limit on a firm’s growth is ultimately the managerial capacity it can supply to absorb expansion, not the capital or the opportunity in front of it (Penrose, 1959), which is the engine behind the resource-based account of how platforms grow.

Why Performance Lags Leadership Saturation

Performance is a lagging indicator. It reflects executed decisions, accumulated momentum, and prior coordination success. Leadership bottlenecks affect decision latency, judgment quality, and learning velocity, and these degrade quietly at first. Organizations keep executing yesterday’s decisions while tomorrow’s accumulate, so when performance finally reflects leadership strain, the underlying bottleneck has already hardened. This is why leadership interventions so often feel too late when results soften. The deeper reason is structural: only variety can absorb variety, and a leadership structure cannot regulate a system that generates complexity faster than the structure can process it (Ashby, 1956; Galbraith, 1974).

Effort Is Not Capacity

One of the most persistent misreadings of leadership strain is the conflation of effort with capacity. When bottlenecks appear, leaders are usually working harder than ever: longer hours, faster responses, more meetings, deeper involvement in operations. From the outside, commitment looks strong. From the inside, capacity is already depleted. Increased effort does not increase leadership capacity. It temporarily masks its exhaustion, in the same way a depleted stock of attention cannot be topped up on demand (Cohen & Levinthal, 1990).

Bottlenecks as a System Outcome

Leadership bottlenecks are often personalized. When decisions slow or coordination falters, explanations gravitate to individuals: the CEO is stretched, the team is thin, the bench is shallow. Sometimes that is true. More often the bottleneck is systemic, because authority cannot absorb novelty fast enough, cadence surfaces decisions too frequently, and operating models generate more unresolved complexity than the system can process. Replacing leaders may move the bottleneck’s location. It rarely removes it.

Why Bottlenecks Tighten Over Time

Once leadership becomes a bottleneck, the system adapts around it. Teams learn to escalate earlier, decisions wait for senior input, informal approvals become embedded, and leaders become increasingly central to flow. These adaptations preserve performance but increase dependence. Over time the bottleneck tightens: fewer decisions resolve locally, more issues require cross-functional arbitration, and leadership attention fragments further. The system becomes both more dependent on leadership and less capable of relieving its load.

The False Signal of Stability

One of the most dangerous signals in buy-and-build is apparent stability. Performance is steady, initiatives progress, the organization appears to be coping. Beneath that surface, decision queues lengthen, ambiguity accumulates, and learning slows. Leadership strain is no longer episodic; it is structural. This is the point at which leadership bottlenecks are most costly to address, because the system has already adapted to their presence.

Why Leadership Bottlenecks Are Rarely Designed Away

Leadership bottlenecks persist because they are not typically designed. They emerge from the interaction of authority structures, cadence choices, integration sequencing, and accumulated operating decisions. Because no single choice creates the bottleneck, no single intervention removes it. Organizations respond reactively, adding layers, inserting roles, clarifying governance, or accelerating reporting, and these responses often increase coordination demand and consume still more leadership capacity.

Setting Up Leadership Debt

Leadership bottlenecks do not disappear on their own. They accumulate consequences. Each adaptation made to preserve performance, whether centralization, exception handling, or informal coordination, creates future leadership obligations, and those obligations compound. What begins as temporary strain becomes leadership debt: capacity borrowed from the future to maintain present performance. The next essay examines how leadership debt accumulates, why it is hard to unwind, and how early success can quietly lock in long-term leadership constraints.

Closing

Leadership does not fail when performance declines. It fails earlier, quietly, invisibly, and adaptively. By the time results reflect leadership strain, the bottleneck is already embedded in the system. Understanding this timing mismatch matters not to assign blame but to recognize leadership as a constrained system whose limits must be designed for, not discovered after the fact.

References

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

Cohen, W. M., & Levinthal, D. A. (1990). Absorptive capacity: A new perspective on learning and innovation. Administrative Science Quarterly, 35(1), 128–152.

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:

Authority Does Not Scale the Way Complexity Does · Leadership Is a Constraint, Not a Trait · Decision Rights, Not Alignment, Scale Platforms · Operating Cadence Is a Leadership System