A team runs a small factory for four production weeks. Between each week there is a kaizen break: the team studies its own numbers, changes how the line works, and runs again. The lean lessons come out of the results — you never need to lecture them.
The first week runs on head-office settings: big batches, no limits on work piling up, checking quality only at the end, and staffing spread by habit. It will go badly. That is the point — do not warn them.
After each week the team sees its results and one improvement idea. Give them 5–8 minutes to argue, change the settings, and predict their next result out loud. The prediction is where the learning happens.
Teams control staffing, batch size, work-in-progress limits and where quality is checked. Most teams double their profit by Week Three and triple it by Week Four.
Compare team trend charts. Ask: What was your bottleneck, and how did you find it? What happened to waiting time when batches got smaller? What did checking quality early really cost — and really save?
The factory can never go faster than its slowest station. Adding people anywhere else only creates piles of waiting work. (Theory of Constraints.)
Big batches feel efficient but make every unit wait for its group. Cutting batch size is the fastest way to cut delivery time. (Little’s Law, one-piece flow.)
A limit on work-in-progress feels like a brake, but it stops the line drowning the bottleneck and makes problems visible immediately. (Pull systems, kanban.)
Catching a fault where it happens costs seconds. Catching it at final test throws away all the work every station added after the fault. (Jidoka.)