Part III — Cultivating Flow · Chapter 23 · First Public Draft
Multiplying What's There
Cultivating technology so it scales the right capability.
Technology multiplies whatever is already there. Which makes it a poor first move and an excellent second one — and makes the discipline almost entirely about sequence.
What changes. Technology stops being the thing you buy to fix an organizational problem and becomes the thing that multiplies whatever the organization already is.
Ask what the tool assumes before asking what it does. Every platform encodes a way of working — who approves, what a team owns, where a decision sits. Buying it buys the assumption, and the assumption outlasts the contract.
Fix the ownership before you scale the technology. Scaling a capability nobody owns produces more of a thing nobody owns. This is the single most reliable way to spend a large budget and change nothing.
Instrument the delivery path, then act on the two friction measures. Lead time for changes and deployment frequency are, in this paper’s terms, friction measures wearing engineering clothes. They are already well defined, already collectable, and the research linking them to commercial performance is stronger than anything else available.
Do not let the pipeline take the blame for the organization. If delivery is technically excellent and things still take nine months, the problem was never in the pipeline. Look at what had to be decided, and by whom, and how far it travelled.
If your delivery is slow and your ownership is clear, this paper has little to offer and Accelerate has a great deal. If your delivery is technically excellent and things still take nine months, the problem was never in the pipeline.