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

Opening: When a Fix Stays a Fix — and Nothing Changes

It’s a scenario plant managers know all too well. A Kobetsu Kaizen project wraps up successfully: the team identified the root cause of a recurring breakdown, implemented a targeted countermeasure, and OEE improved by eight percentage points. Everyone celebrates. Two months later, the same failure mode reappears. The countermeasure worked — but it was never converted into a standard. Nobody documented the new maintenance routine, nobody trained the operators on the updated procedure, and the original problem crept back in through the gap between a good solution and a lasting change. This is exactly where the SDCA-PDCA cycle becomes indispensable: it is the bridge that transforms a one-time improvement into organizational knowledge and sustainable performance.

Understanding the SDCA-PDCA Architecture

To connect Kobetsu Kaizen results to lasting improvement, you first need to understand how SDCA and PDCA work together as a system — not as two separate tools, but as two complementary gears driving the “wheel of improvement.”

PDCA (Plan-Do-Check-Act) is the improvement cycle. It starts from a recognized problem or loss, drives analysis, implements countermeasures, and verifies results. In Kobetsu Kaizen, PDCA governs the entire project journey: from the initial problem selection and the identification of the 16 losses, through root cause analysis using tools like the 5-Why or fishbone diagram, to the execution of the countermeasure plan (What? How? Who? By when?) and the confirmation of results.

SDCA (Standardize-Do-Check-Act) is the stabilization cycle. It takes over once PDCA has delivered a validated result. Its purpose is to lock in the improvement: identify what standards are needed, write those standards clearly, train the people who must follow them, execute against the standard, check for compliance, and act to correct any drift. As the knowledge base defines it, a standard is “the best, safest, and easiest way to achieve and maintain a defined quality level.”

The critical insight is the sequence: PDCA raises the performance bar; SDCA holds it there. Without SDCA following PDCA, every improvement is temporary. Without PDCA challenging the current standard, SDCA becomes a bureaucratic exercise in maintaining mediocrity. Together, they form the continuous improvement engine that Kobetsu Kaizen is designed to fuel.

Good standards share a common set of characteristics. According to Lean methodology, they should:

• Be simple, clear, and conspicuous — visible and understandable at the point of use
• Represent the single best, easiest, and safest way to perform the task at a given moment
• Preserve know-how and prevent knowledge loss when team members rotate
• Enable performance measurement by providing a defined baseline
• Assure quality, cost, delivery, and safety outcomes
• Show the relationship between cause and effect, so operators understand why the standard exists

Connecting KK Countermeasures to New Standards: A Step-by-Step Path

The transition from a Kobetsu Kaizen countermeasure to an updated standard is not automatic — it requires deliberate action at the close of every KK project. Here is how that transition should be structured.

Step 1 — Confirm the result before standardizing. The Act phase of PDCA must verify that the countermeasure actually solved the root cause and that the improvement is stable over a defined observation period (typically a minimum of four to six weeks). Premature standardization of an unvalidated fix is one of the most common errors in practice. The Kobetsu Kaizen Board is a useful anchor here: it tracks the comparison between the target (oriented toward zero defects, zero breakdowns, zero accidents) and actual results across a three-month window, providing the evidence base needed before moving to SDCA.

Step 2 — Identify the standards that need to be created or updated. Ask: which existing procedures, work instructions, maintenance schedules, or control plans were part of the system that allowed the loss to occur? Each KK countermeasure typically touches at least one standard. A countermeasure that addressed improper lubrication frequency, for instance, requires updating the autonomous maintenance standard for that machine.

Step 3 — Write and validate the new standard. Involve the operators and technicians who will use the standard in writing it. Standards written exclusively by engineers and never validated at the gemba are rarely followed in practice. The standard must reflect reality at the point where value is created.

Step 4 — Inform and train. Distribution alone is not training. The SDCA cycle explicitly includes an information and training phase. Operators need to understand not just what the new standard says, but why it exists — what loss it prevents, and what happens when it is not followed.

Step 5 — Execute, check compliance, and sustain. SDCA does not end with the training session. Regular checks — through audits, visual management, and leader standard work — must verify that the new standard is being followed. Where deviations appear, act promptly to correct them before the old behavior re-establishes itself.

Practical Case Study: Fenix Automotive Components

Fenix Automotive Components operates a stamping line producing structural brackets for the automotive sector. Over a six-month period, the team leader on Line 4 noticed a recurring pattern of micro-stoppages linked to tool misalignment after die changes. The issue was contributing to a start-up loss of approximately 35 minutes per changeover and generating 4–6% scrap on the first production run after each setup.

A Kobetsu Kaizen project was launched. Using the Pareto diagram, the team confirmed that tool misalignment accounted for 62% of all start-up loss events on the line. The 5-Why analysis revealed the root cause: the setup checklist did not include a verification step for die centering before the first stroke, and operators had inconsistent practices because no standard existed for that specific check.

The PDCA countermeasure was straightforward: design a physical go/no-go gauge to verify die centering in under 90 seconds, and add a mandatory verification step at that point in the setup sequence. After implementation, start-up loss dropped to under eight minutes and first-run scrap fell to 0.8%. Results were confirmed over the following six weeks.

At the close of the KK project, the team did not stop at celebrating the result. They activated the SDCA cycle deliberately:

1. The setup work instruction was rewritten to include the new centering check with a photo showing correct gauge usage
2. The die change standard time was updated on the line’s visual management board
3. All four operators on the line received hands-on training, not just a document update
4. The team leader added a weekly compliance check to their leader standard work

Eighteen months later, the improvement remains in place. The gauge has since been replicated on two other stamping lines, driven by a horizontal deployment initiative — another direct benefit of a properly closed SDCA loop.

Key Takeaways

• PDCA improves, SDCA sustains: Every Kobetsu Kaizen project should formally close with an SDCA cycle that locks in the countermeasure as a new organizational standard.
• Confirmation before standardization: Never convert a countermeasure into a standard before verifying that results are stable — the Kobetsu Kaizen Board’s three-month tracking window is your evidence base.
• A standard is only real if it is followed: Writing a document is not enough. Training, visual management, and regular compliance checks are the mechanisms that make standards live at the gemba.
• Standards preserve know-how: When countermeasures are captured as standards, the organization retains the learning even after team members move on — turning individual KK results into institutional capability.
• The SDCA-PDCA cycle is the engine