Naming the next bottleneck

If your bottleneck moved, you've just created a new one. That isn't a setback. It's the reason the Deployment Framework is a loop and not a project. This lesson finds where the limit has gone, names it, and gets the leadership team ready to restate the aim for the next 90 days.

Fixing one bottleneck exposes the next

Every piece of work has a slowest step. Make that step faster and something else becomes the slowest. You saw it in module 1: fix review, and drafting becomes what everything waits on. On day 90 you get to see it in your own organisation.

The new bottleneck is often less obvious than the old one. The old one had a queue in front of it that everybody could see. The new one may be a step that was coping fine until more work started arriving, or a rule that nobody has questioned in years.

Where the next one hides

Look in three places first.

• The step after the old bottleneck. It's now receiving more work than it ever has. Watch its queue, and its rework: if rework rises at the step after the bottleneck, AI output is flooding it.
• A rule built around the old bottleneck. Approvals, sign-offs and checks were often designed for the old pace of work. When the pace changes, the rule becomes the limit.
• Outside the line. Sometimes the work can now deliver more than customers take. Then the bottleneck is the market, and the aim may need to point at growth.

Name the step, never the person, even when the step is one person's calendar. The friction list records work, and so does this.

Goldratt's Theory of Constraints, which the framework borrows openly, ends its five steps with that warning. The habits, rules and attention you built around the old bottleneck don't move when the bottleneck does. The person who led it wants to keep improving it. The meeting that reviewed it keeps meeting. The approval that protected it keeps approving. Left alone, they become the next thing the work waits on.

Pick from the friction list

You don't need to start from scratch. The friction list already holds the candidates: where work waits, piles up or gets redone, recorded since module 4. The day-90 review in lesson 3 added its findings. Choose the one that most holds the aim back, the same way you did on day 14: trace back from the customer to where the work waits.

If Improve's exit was “it didn't move”, the next loop may keep the same bottleneck. Either you keep improving it, or the gap goes to Build through the front door and the next loop runs alongside the build.

Restate the aim at the quarterly meeting

The next bottleneck isn't confirmed by the person who runs the loop. It's confirmed by the leadership team, at the quarterly meeting: half a day, once a quarter. The framework sets its agenda. Restate the aim with the outside view, check the conversion ledger, confirm or name the bottleneck, fund builds, and look at roles that changed and reviews that are due.

The outside view is what keeps the aim honest. Customers want different things than they did 90 days ago. A competitor may have moved. Your pricing model may reward the time you've freed, or punish it: a firm that bills by the hour can lose revenue by working faster, unless the aim says where that time goes.

A quarterly rhythm is fast enough to keep up and slow enough to measure. Restating the aim every quarter, in the room, with the numbers in front of you, is how the leadership team stays aligned on what the next 90 days are for.