The Fix

Chapter 19: From Pretence to Autonomy

The transition is primarily political rather than structural. This chapter describes what it does to the three populations it threatens most: middle management whose coordination roles disappear, finance teams who lose narrative authority, and product managers whose competence was shaped by the dysfunction the model resolves.

The claims management unit ran for fourteen months. For the first eight, it was the CTO's best argument: resolution times down thirty-one percent, customer satisfaction from 3.2 to 4.1, the gap between how claims were supposed to work and how they actually worked narrower than the organisation had ever achieved. Three other teams had asked how to adopt the model.

Then the CTO was promoted to a group role. His replacement came from the consulting division, capable and respected but focused on other priorities, with no particular investment in the autonomous unit model.

The encroachments arrived individually, each framed as procedural: line-item visibility, standard performance reviews, quarterly priority presentations. Without the sponsor's backing, each charter reference produced a conversation rather than a resolution. By month eleven, the unit lead was spending more time defending the model than operating it.

At month fourteen, a reorganisation absorbed the unit back into the functional structure. The process definition was archived. Resolution times returned to their previous levels within two quarters. The official narrative was that the claims process had been “successfully integrated” and the “learnings had been captured.” The unit lead left the company four months later.

The model had worked. The political infrastructure had not survived its sponsor. The payments unit was among the first to operate autonomously. Within four months, a pattern emerged: its contract required consuming units to submit fully validated payment requests, which was structurally correct, but the consuming units faced the same incentive to minimise their own validation costs and let the payments unit reject what it could not process.

A contract arms race followed. The payments unit tightened its schemas; the consuming units added retry logic. Payment failures increased, and each unit's metrics looked healthy in isolation while the cross-unit customer journey degraded.

The fix was structural: the three units redesigned the contract together, splitting validation responsibilities so that each unit validated what it owned. A shared validation event allowed consumers to pre-check payment-specific fields. The arms race stopped, and the customer experience recovered within a quarter.

The model had produced both the failure and the fix, but only because the people involved treated the contract as a hypothesis to be tested rather than a boundary to be defended. The previous two chapters described the mechanism for scaling: the transitional fund, the CTO-CEO decision pair, the pull-based relationship between central services and the units they serve. This chapter describes the human reality of that scaling, because the transition is primarily political rather than structural.

...

See also: Full contents · Preview chapters · Illusions in the Boardroom