The Fix

Chapter 17: The Authority to Decompose

Scaling from one autonomous unit to many requires a transitional fund ring-fenced from the annual budget cycle and a CTO-CEO decision pair that collapses boundary decisions to two people. The chapter specifies how the CTO is measured and what remains central after the transition.

The CTO of a Nordic insurer had the first autonomous unit running for four months. Claims resolution time was down 31%. Deployment frequency had tripled. The evidence was unambiguous, and she needed three more units by end of year to reach the tipping point described in the previous chapter: the point at which the autonomous model becomes self-evidently better than what it replaced, and the question shifts from “should we restructure?” to “why does everything else still work the old way?”

She opened the budget request for the payments unit. The decomposition work required EUR 1.4 million over six months: untangling the shared database that five product lines wrote to directly, establishing contract boundaries with three adjacent services, staffing the unit with a domain expert and two engineers who understood the payments regulatory landscape. The CFO's question was reasonable: which business unit's P&L should absorb the cost? Payments was shared across four product lines. No single product owner would fund decomposition that benefited the other three. The investment that would make the payments unit possible did not fit inside any existing budget line, because the budget model priced departments, not processes, and the payments process did not belong to any department.

She escalated. The CEO agreed the investment was necessary. The CFO agreed in principle. The process to secure cross-business-unit funding took eleven weeks. By the time the budget was approved, the senior engineer she had identified for the payments unit lead had accepted an offer elsewhere. He had been carrying twelve years of payments domain knowledge that the organisation had never asked him to write down. The window for the second unit moved from Q2 to Q4. The claims unit continued to operate, producing evidence that made the surrounding dysfunction visible. The surrounding dysfunction continued to operate, producing evidence that it could outlast any change that required its own budget model to fund it. The previous chapter described how to launch one autonomous unit: selecting the process, drafting the governance charter, protecting the unit's autonomy through the first ninety days. This chapter describes the budget and authority structure that makes the transition from one unit to twelve possible within the window where executive attention holds.

Consider what the CTO's conversation with the CFO looks like when she arrives not with a budget request routed through the normal cycle but with a ring-fenced reconstruction fund, pre-authorised by the CEO, sized to the decomposition work required.

The CFO's first objection is structural rather than financial: which P&L absorbs the cost? The payments decomposition benefits four product lines. No product owner will fund work that benefits the other three. The cost has to sit somewhere, and the CFO's reporting model requires that somewhere to have a name.

The CEO answers the objection directly. The P&L question is precisely what the fund resolves. No business unit funds cross-cutting decomposition because no business unit owns the cross-cut. The fund sits under the CTO's authority for a bounded period, ring-fenced from the annual budget cycle, with a twelve-month cap and a decline curve that transfers operational cost to the units as they become self-sustaining. The CFO's reporting obligation is met: the fund has a line, a cap, a taper schedule, and measurable outcomes attached to each draw. What it does not have is a product owner, because the work it funds is structural, and structural investment that requires a product owner to justify it will never be justified, which is why the payments unit does not yet exist.

When the CFO asks what happens if the twelve months produce insufficient working units, the answer is the one she expects: the fund closes. The CTO accepts that constraint because she knows the alternative. An open-ended fund becomes a permanent dependency. A capped fund forces sequencing discipline: the hardest decomposition first, the boundaries that unlock the most subsequent units, the work that cannot wait.

The payments unit began decomposition the following Monday.

...

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