Lesson 2: Connecting KK Results to the SDCA-PDCA Cycle: From Countermeasure to New Standard

Opening: When a Countermeasure Is Not Enough

Imagine this scenario: the maintenance team at a mid-sized automotive parts plant spends three weeks running a focused Kobetsu Kaizen event on a recurring breakdown affecting a critical stamping machine. They identify the root cause — inadequate lubrication frequency — apply a targeted countermeasure, and watch OEE climb from 67% to 81%. The team celebrates, the numbers look great, and the project is closed. Three months later, the same breakdown pattern returns. Why? Because the countermeasure was implemented but never converted into a standard. The improvement lived in someone’s memory, not in the system. This is one of the most common and costly mistakes in continuous improvement: confusing a temporary fix with a lasting change. The bridge between a successful Kobetsu Kaizen result and permanent operational improvement is the deliberate, disciplined connection to the SDCA–PDCA cycle.

Understanding the SDCA–PDCA Cycle and Its Role in Sustaining Improvement

To understand how Kobetsu Kaizen results become permanent, we must first understand the two interconnected improvement cycles that form the backbone of Lean operations: SDCA (Standardize–Do–Check–Act) and PDCA (Plan–Do–Check–Act). These are not competing methodologies — they are complementary gears in the same improvement engine, each turning at the right moment depending on whether a process is being stabilized or improved.

The PDCA cycle drives improvement. In the context of Kobetsu Kaizen, this means:

• Plan: Determine and classify the problem, quantify losses using the 16-loss framework, analyse root causes, and define targeted actions using tools such as 5-Why analysis, fishbone diagrams, and Pareto charts.
• Do: Execute the countermeasures according to the 5W1H action plan — defining what must be done, how, by whom, and by when.
• Check: Confirm that the results match the targets defined during the goal-setting phase. Were the losses reduced? Did OEE, yield, or cycle time improve as expected?
• Act: Prevent recurrence by standardising successful countermeasures and reflecting on the improvement process itself to feed future KK events.

The SDCA cycle, on the other hand, is responsible for holding the gains. Once a countermeasure has proven effective and has been validated through the Check phase of PDCA, SDCA takes over:

• Standardize: Identify what standards need to be created or updated. Write clear, simple, and visual standards that preserve the new know-how.
• Do: Train operators and team leaders on the new standard. Execute the process as specified.
• Check: Verify that the standard is being respected consistently across all shifts and operators.
• Act: Correct deviations immediately and improve the standard when new knowledge or conditions emerge.

A standard, in Lean terms, is defined as “the best, safest, and easiest way to achieve and maintain a defined quality level.” It should be simple, clear, and visible at the point of use. It must assure quality, cost, delivery, and safety — and it must be the single reference point, not one of several competing guidelines. Without this anchor, every KK improvement is at risk of erosion over time.

From Countermeasure to New Standard: A Four-Step Transition

The transition from a KK countermeasure to a new operational standard is not automatic. It requires intentional action at the end of every improvement project. Here is a structured four-step approach that plant managers and team leaders can follow:

1. Validate the countermeasure results. Before standardising anything, confirm that the countermeasure has delivered the expected results consistently over time — not just for one shift or one day. Use the KK Board’s visual tracking tools and compare actual performance against the SMART goals set at the beginning of the project. Only a verified result earns the right to become a standard.
2. Identify which standards are affected. A single countermeasure may touch multiple documents: a machine cleaning and inspection checklist, an operator work instruction, a maintenance schedule, or a visual management board. Map all the documents and practices that need to be created or revised.
3. Write and publish the updated standard. Involve the operators who performed the work — they understand the practical nuances best. The new standard must be written in plain language, supported by visuals where possible, and located at the point of use. It must reflect the actual best practice, not a theoretical ideal.
4. Train, confirm, and sustain. Communicate the change to all relevant team members. Conduct targeted training. Then use the SDCA Check phase to audit compliance actively in the following weeks. Assign clear responsibility for monitoring and corrective action when deviations occur.

This four-step transition is what transforms Kobetsu Kaizen from a project into a permanent capability upgrade for the operation. It is also the mechanism by which organisational knowledge is preserved — so that when team members rotate or leave, the improvement does not leave with them.

Practical Case Study: Elara Plastics Manufacturing

Elara Plastics Manufacturing, a fictional mid-size injection moulding facility, was experiencing high scrap rates on one of its high-volume product lines — approximately 4.2% versus a target of 1.5%. A Kobetsu Kaizen team was formed, and the team followed the structured KK process using the eight steps on the KK Board.

During the root cause analysis phase, the team used a 5-Why analysis combined with a fishbone diagram and identified that the primary driver of scrap was inconsistent mould temperature at start-up — a loss classified under start-up losses in the 16-loss framework. The countermeasure was straightforward: define a precise warm-up sequence with specific time intervals and temperature checkpoints before the first production shot.

The team implemented the countermeasure, and after two weeks of monitoring, scrap dropped to 1.3% — below target. This is where many teams would have stopped. Instead, the Elara team initiated the SDCA transition. They updated the operator work instruction for mould set-up, added a visual temperature control card to the machine, revised the shift start-up checklist, and conducted a 30-minute training session for all three shifts. A team leader was assigned to audit compliance for the following four weeks.

Six months later, scrap on that line remained at 1.4% — the improvement had held. More importantly, when two new operators joined the team, they were trained directly from the updated standard. The knowledge was in the system, not just in the memory of the original KK team.

Key Takeaways

• Countermeasures without standardisation are temporary fixes. The SDCA cycle is the mechanism that converts KK results into lasting operational improvements and prevents recurrence of the original problem.
• PDCA drives improvement; SDCA holds the gains. Both cycles are essential and sequential — a KK project is only complete when the successful countermeasure has been embedded into a new or revised standard.
• Standards must be simple, visual, and owned. A good standard preserves know-how, enables consistent performance across all operators and shifts, and is located where the work actually happens.
• Validation before standardisation is non-negotiable. Only confirmed, sustained results should be codified into standards. Premature standardisation of an unproven countermeasure can lock in a flawed practice.
• The SDCA–PDCA connection is the engine of continuous improvement. Each completed KK cycle raises the performance baseline, and the next improvement cycle starts from a higher, more stable foundation — which is the true meaning of continuous improvement in