The New Bottleneck on MinimumCD Practice Guide

Why Coordination, Not Coding, Sets the Pace

Mon, 01 Jan 0001 00:00:00 +0000

AI changed the economics of creating software. It did not touch the physics of delivering it. Value still flows through a system of people, tools, and decisions, and in most enterprises that system is governed not by how fast anyone writes code but by how long work waits. The constraint is coordination, not creation. This page is the physics behind that claim.

Three Forces Set the Speed of Any Flow

Coordination cost is not a vague complaint. When work crosses people and teams, three forces govern how long it takes.

Use AI to Find Friction Before You Use It to Go Faster

Mon, 01 Jan 0001 00:00:00 +0000

The obvious use of AI is to generate more code. The bigger win is to remove the dependencies that dominate lead time. This page covers the four principles a leader needs for that to work, and the five properties that turn the Golden Rule into specific moves.

Four Principles

Principle 1: Treat AI as a Diagnostic Before an Accelerator

The first capability AI gives an enterprise is not speed; it’s visibility. When an agent struggles to make a small change, it reveals where the system depends on implicit knowledge, a dependency you could not see before. If generated tests are brittle, behavior was never specified. And when code is ready but cannot move, that constraint was downstream all along.

Where the Bottleneck Moves

Mon, 01 Jan 0001 00:00:00 +0000

AI compresses the making phases of delivery hardest and barely touches the rest. So as creation cost falls, the constraint does not disappear. It moves outward to the phases AI does not cheapen. This page gives you a shared map of the delivery lifecycle and the five categories of bottleneck that map onto it, each with its agent-speed signal and the intervention pattern that removes it.

The Product Delivery Lifecycle

To turn “where does work stop?” into a classification you can act on, you need a shared map of the journey, one stable enough that business, engineering, security, and audit can all point to the same place and mean the same thing. Stripped to its spine, the product delivery lifecycle (PDLC) has seven phases, and it loops, because delivery is a cycle, not a line.

The Bottleneck Removal Loop

Mon, 01 Jan 0001 00:00:00 +0000

The principles describe how to think. The loop describes what to do, repeatedly. Like the delivery lifecycle itself, bottleneck removal is not a project with an end state. It is a cycle you run, and keep running, because every constraint you remove exposes the next one. This page is the playbook.

The Loop

graph LR
 P1["1. Identify<br/>& Diagnose"] --> P2["2. Re-engineer<br/>the Bottleneck"]
 P2 --> P3["3. Document<br/>& Share"]
 P3 --> P4["4. Iterate to<br/>the Next Constraint"]
 P4 -.-> P1

 style P1 fill:#e8f4fd,stroke:#1a73e8
 style P2 fill:#fce8e6,stroke:#d93025
 style P3 fill:#e6f4ea,stroke:#137333
 style P4 fill:#fff4e5,stroke:#e8710a

Use AI in every phase, not only to write code, but to solve old coordination problems in new ways.