Executive Summary

Software-dependent corporates govern through representations that were never designed to be tested against the system. This summary condenses the book’s thesis, the six demands a board should make before any AI investment, and why the choice between the writer path and the reader path cannot wait.

Thesis. Software-dependent corporates govern through representations that were never designed to be tested against the system: narratives that replace reality, portfolio labels with no executable boundary, architecture that advises but does not bind, processes that were never written down. These are not failures of intelligence but the structural consequence of separating “the business” from engineering, coping mechanisms whose cost structure has changed. AI makes bounded reconciliation cheap enough to repeat. The gap between what the organisation says and what the system does becomes measurable, and the cost of leaving it unmeasured compounds. The correction combines four things boards usually govern separately: process ownership, binding artefacts, continuous reconciliation, and explicit protection of the resulting boundaries. The combination—not any single component—is the model proposed here.

Diagnosis. Products exist in portfolios but have no coherent boundary in the code. Architecture describes aspirations rather than systems. Capital attaches to labels while value is created at process boundaries that the financial model cannot observe. In the organisations this book targets, coordination can plausibly absorb a large minority of technology-delivery capacity. Chapter 6 uses 30 to 40% as a testable estimate calibrated against adjacent research, not as an established industry average. Experienced engineers leave, taking irreplaceable process context. Regulatory exposure compounds silently until the moment it is tested. AI-assisted development decouples output rate from team size without decoupling drift risk. Boards that reduce engineering headcount on the basis of delivery velocity metrics are measuring the wrong variable.

Six demands. Before approving material AI investment that will affect a critical business process, the board should require six items for that process: a ranked process inventory, a structured process definition, a single named owner, a versioned contract inventory, a reconciliation report against the code, and a cost-to-outcome trace. The diagnostic that follows sets out each in full. If management cannot produce them for one critical process within 30 days, the proposed investment builds on a foundation the organisation has never inspected.

Scope. The structural model is most applicable to software-dependent corporates above approximately two hundred people, with more than thirty services, and without a single founder who carries process ownership personally. Safety-critical industries and deeply unionised structures have contextual constraints the transition must work within rather than around. Chapter 17 addresses these boundaries directly. Partial adoption (contracts without full restructuring, process definitions without the transitional fund) produces partial benefit rather than failure.

No organisation is named in this book as having run the full model, charter, fund, decision pair, and continuous reconciliation together. The model is a synthesis: its components are evidenced separately, while the complete combination and the outcome figures in its composites are testable hypotheses.

Technology maturity. End-to-end organisational reconciliation is not a commodity product. Bounded reconciliation for one defined process is feasible now, with domain review; continuous cross-unit synthesis and causal decision tracing require custom engineering and remain immature. The governance decision advocated here is to create the ownership and artefacts that make current tools useful and future tools trustworthy.

...

See also: Full contents · Preview chapters · Illusions of Work