Starting a Programme
The first ninety days, without a purchase. What to measure, what to fix first, and the order that produces credibility.
Procedure
Running a programme
The first ninety days without a purchase, the ranking that returns most soonest, and the failures that recur — each visible early and each with a specific correction.
8 notes
Choosing What to Fix
A list of forty findings and one person. The ranking that gets the most back soonest, and the trap of doing the interesting one first.
Procedure
Who Owns the Toolchain
Nobody, one person, or a team. Each arrangement fails differently, and the failure modes are predictable enough to plan around.
Analysis
Buying, Building and Configuring
Most of the available gains come from configuration you already own. What a product genuinely adds, and when building your own is defensible.
Analysis
Getting Improvements Adopted
A faster path nobody uses is not faster. Why developers keep the old way, and what actually moves people across.
Analysis
How These Programmes Fail
A short list of recurring failures, each visible early, each with a specific correction.
Analysis
Stopping It Coming Back
Build performance decays continuously. The checks that catch a regression while it is still attributable to one commit.
Procedure
What Changes as the Codebase Grows
Practices that work at ten engineers fail at two hundred, and the transition points are predictable enough to plan for.
Analysis