Structural Correction

Chapter 16: The Transition and Its Failure Modes

The transition’s quarter-by-quarter timeline and the specific failure modes that end it. If the unit’s time spent on coordination obligations is rising quarter over quarter, the charter is advisory regardless of what the governance dashboard reports.

Each executive role is affected differently by structural correction: what stops being governable by narrative, what new artefacts become decisive, what to stop rewarding, and what to authorise. First, the shift that applies to all of them.

Most executives reached their position by operating at distance from mechanism: synthesising across functions, weighing trade-offs, allocating capital without holding every operational detail. This distance is how leadership scales, and over time it becomes identity. When processes become explicit and contracts become binding, machine-readable artefacts shorten the path between commitment and consequence, and executive distance stops working the same way. The executive who is comfortable experiences this as increased control; the one who is not experiences it as the loss of interpretive insulation, the capacity to reframe outcomes, diffuse responsibility, and manage contradiction through narrative rather than mechanism. For many executives that capacity is not peripheral but the primary basis on which the organisation selected them. Boards are not always the victims of this resistance; sometimes they are co-participants, preferring the smoothed narrative to confronting structural problems they have tolerated.

Quarter one is analytical: a small team maps the three to five processes that represent the majority of customer value and cost, producing both the process map, what happens, in what order, with what decision points and failure modes, and the overlay of which teams, services, and databases participate in each. The overlay is where the dysfunction is exposed, and it reveals that most processes share more infrastructure than anyone documented. Those shared dependencies determine the contract boundaries the second unit will need; the mapping is a precondition for the second unit, not the first.

Quarter two launches the first autonomous unit under its charter. The first enforcement test arrives within weeks: the change advisory board pushes back on the unit's deployment cadence, and the sponsor either confirms the deployment authority clause or equivocates. If she confirms, the board learns the charter is binding; if she equivocates, the unit learns it is advisory. This moment, not the charter's signing, is when the unit's authority is established, and most transitions that fail can trace the failure to it. By the first quarterly review, the CFO sees envelope spending connected to measurable results for the first time: claims resolution time down, cost per claim down, and a conversation about outcomes rather than activities.

Quarters three and four launch units two through four through contiguous expansion, each sharing a contract boundary with an existing one. Each new unit reveals dependencies the first did not encounter, and each boundary dispute is resolved through the five-day resolution clause or it is not; if it is, the organisation has a mechanism for resolving cross-unit disagreement without a committee. By the CEO's third-quarter review, three units are producing outcome data, and the strategic narrative is testable against it: claims that do not correspond to unit performance are visible because the artefacts exist, not because anyone chose to surface them. The transition has a human cost, and the organisation owes displaced people honesty, redeployment into a unit where their process knowledge has value, or an honest separation, not six months of role ambiguity that delays the same outcome. By the end of year one, the organisation should have four to six units, a functioning contract model, and the strongest result of all: remaining problems that are genuine rather than artefacts of structural incoherence.

The first unit delivers early improvements, but the sponsor is promoted after quarter two, and her replacement sees the charter as an anomaly rather than a precedent. Within three months the deployment authority routes back through the change advisory board, prioritisation is absorbed into the quarterly planning cycle, and the unit's data analyst is reassigned. The charter still exists; the authority it describes does not. The organisation calls this evidence that autonomy “does not work at our scale.” It is evidence that sponsorship is the first thing the existing structure removes.

...

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