Continuous improvement is a loop, not a suggestion box that empties into a graveyard. Whether you are evolving a flow system or a quality system, the job is the same: see a defect or a delay, find a cause, change one thing, check whether the system actually moved, then standardise or try again. A mural of sticky notes is not kaizen. It is stationery.
Kaizen: evolve the system, not the heroics
Kaizen is small, ongoing change by the people who do the work — to the process, the policy, the definition of done, the hand-off, the check. It is not a transformation programme with a logo, and it is not asking individuals to 'be more careful' after a miss. If the system produces the error, coaching a person is how you keep the error and add shame.
Flow teams improve the board, the limits, the entry criteria, the review SLA. Quality teams improve the standard, the inspection point, the supplier check, the training that actually matches the work. Same idea: the system is allowed to change. A process you cannot edit is a museum. Museums do not ship.
Respect shows up as time to improve. A team at 100% utilisation will not kaizen; they will apologise. Put improvement on the capacity plan — a slice of the week, a slot on the board — or admit you only wanted the poster. Unused talent was a waste two lessons ago. It is also a quality failure: the people who saw the root cause were not allowed to act.
PDCA, and root cause before you add a step
Plan–Do–Check–Act is the smallest honest loop. Plan a change and a measure. Do it on a limited slice. Check the measure and the side effects. Act: adopt, adjust, or drop. Skipping Check is how organisations collect initiatives. Skipping Act is how they run the same pilot until the sponsor changes.
Root cause before corrective action. Five whys, a fishbone, a look at the last three incidents — whatever gets you past the first convenient villain. 'Add an approval' is the most popular non-cause in corporate life. Sometimes the cause is an unclear standard, a tool that cannot do the job, a WIP policy that forces haste, or a measure that rewards starting. Fix that. Do not grow a process garden on top of a guess.
Corrective action repairs this instance and the condition that produced it. Preventive action stops a related miss you have not had yet. Both need an owner and a check date. 'Lessons learned: communicate better' is neither. It is a toast. Quality control found the defect; improvement is what you do to the system so the next lot does not fail the same way.
One improvement at a time — then look
If you change the WIP limit, the review policy, and the vendor SLA in the same week, you have anecdotes, not evidence. Pick the constraint that is hurting now — the ageing Review band, the repeating defect type, the rework loop — and change one policy. Hold the others still long enough to see the CFD, the escape rate, or the cycle-time tail move.
Retrospectives, quality huddles, and kaizen events fail the same way: twenty actions, no owners, no Check. Leave with one change, one measure, one date. Park the rest on a backlog of improvements that is allowed to be short. A long improvement backlog is inventory. You already know what inventory does to cycle time.
Standardise what worked so the improvement is not a folk memory. Update the working agreement, the quality procedure, the board policy, the checklist. Then the next person does not have to be a hero. If you cannot point to the written change, you did not finish Act. You had a good conversation. Conversations do not survive a reorg.
Course complete — what's next
Kaizen changes the system in small steps. PDCA keeps you honest. Root cause before you add a gate. One improvement, one measure, then write down what you adopted. The loop serves lean flow and quality alike — waste, defects, and delay are cousins.
If this closes Kanban & Lean Flow, take one policy change onto a live board this week. If you are in Quality Management, the same loop is what you will report next: a metric without a change story is decoration. Either way, do not collect twenty actions. Finish one.