Your improvement and training plan

This is the plan the bottleneck lead works from between day 15 and day 90: what changes at the bottleneck, what it should give back, how everything else is paced to it, who is trained on what and when, and the dates it gets checked. It ends where Improve ends, with three possible exits.

Anything still missing is flagged below, with a link back to the lesson where you add it.

Your improvement plan: 0 of 8 parts done0%

Bottleneck and its lead →Written prediction →Redesign →More from the bottleneck →Pacing rules →Training cohorts →Protected hours →Check dates →

Organisation name

Improvement and training plan · The Deployment Framework

Your organisation

Improve: days 15–90 of your first loop

The bottleneck

Name your bottleneck and write your prediction in module 4.

Bottleneck lead: Not set yet. Add it
Prediction: Not set yet. Add it
Protected hours: Not set yet. Add it
Expected hours freed: Not set yet. Add it

1 · Redesign the work first

No redesign yet. Add it

2 · Get more from the bottleneck

No moves chosen yet. Add it

3 · Pace everything else

Cap: Not set yet. Add it
Release: Not set yet. Add it
Upstream's spare time: Not set yet. Add it
When the cap is passed: Not set yet. Add it

4 · Train people on their own work

No cohorts yet. Add it

A record is kept for every cohort: dates, who took part, the workflow, the approved tool, the hours and the coach. It counts as evidence of AI literacy.

5 · Check every two weeks

At every check, the bottleneck lead looks at: output and cycle time at the bottleneck, rework there and at the next step, whether work arrives complete, the queue against the cap, and whether something else is now the bottleneck.

Day	Date	Also ask
28	Set day 0	First check. Expect the early dip. Is work arriving complete, and is the cap holding?
42	Set day 0	Is the dip passing? Have the moved tasks landed with the teams that took them on?
56	Set day 0	Is there a gain at all? Hold it against the kill criteria.
70	Set day 0	Has something else become what everything waits on?
84	Set day 0	Last check before the re-measure. Are the training records complete?
90	Set day 0	Re-measure over days 60–90 against the prediction, and take one of Improve's three exits.

6 · Improve's exit

Exit 1

It moved

Go back to Find. Fixing one bottleneck exposes the next, so name it. A new bottleneck can be named at any check.

Exit 2

It didn't move, and the gap is worth paying for

Raise it at the front door for Build, with what you learned. Redesign and approved tools have now been tried.

Exit 3

It didn't move, and it isn't worth paying for

Keep improving, or accept the level and name the next bottleneck.

Bottleneck lead

Runs the loop

Sponsor, protects the hours

What happens next

Improve runs until the measurement window closes, and most bottlenecks have weeks of improvement in them. But some gaps won't close without new money or engineering time, and people will start making and asking for things as soon as the training begins. Both need somewhere to go.

Module 6 sets up the front door: one place where anyone can raise anything, with a first answer within 10 working days. It also covers the two questions that decide what anything made with AI needs, and the one-page case for whatever turns out to be worth paying for.

Your organisation

Get the print-ready improvement plan

What happens next