Definition
PDCA is a four-stage iterative cycle for improvement and problem solving:
- Plan — Study the current situation, understand the problem, analyze root causes, and develop a hypothesis for improvement. Define what you expect to happen.
- Do — Implement the plan on a small scale. This is a test, not a full rollout. Execute the change and collect data.
- Check — Compare actual results against what you predicted in the Plan stage. Did the change produce the expected improvement? What did you learn?
- Act — If the change worked, standardize it — make it the new standard method. If it did not work, analyze why and begin the cycle again with a revised plan.
The power of PDCA is not in any individual step but in the cycle — the discipline of repeating Plan-Do-Check-Act continuously, each cycle building on the learning of the previous one. Improvement is not a one-time project; it is an ongoing process of hypothesis, experiment, verification, and standardization.
Japanese Origin
Contrary to the standard narrative, PDCA was not brought to Japan by W. Edwards Deming. What Deming taught in 1950 was the Shewhart Cycle — a product-focused wheel of design, manufacture, sell, and research. The four-letter acronym PDCA was developed inside Japan over the following decade by Japanese engineers and management thinkers, most notably Shigeru Mizuno and Kaoru Ishikawa, who reconstructed Deming’s ideas alongside other influences into something broader and more practical.
In Japanese, PDCA is typically written as PDCAサイクル (PDCA saikuru) using the English acronym directly. The English letters were deliberately chosen by Ishikawa for simplicity and portability — they were easier to remember and teach than the Japanese terminology. PDCA is also referred to as the 管理のサイクル (kanri no saikuru, “management cycle”) or 管理の輪 (kanri no wa, “management wheel”).
Within Toyota, PDCA is not a technique to be deployed for specific projects — it is the thinking discipline expected of every manager and supervisor. Planning without checking is wishful thinking. Doing without planning is recklessness. Checking without acting is waste. The cycle demands all four.
History
PDCA has a longer and more complex history than most practitioners realize. The standard account — “Deming taught PDCA to the Japanese” — compresses a century of development by multiple contributors into a single attribution. What follows draws on a 2016 research paper by Junya Onishi and Wataru Fukumoto of Japan’s Policy Research Institute, as well as the original Japanese-language sources they cite.
The American Roots (1903-1950)
Frederick Taylor (1903) — Taylor separated planning from execution in Shop Management, establishing that planning was a distinct function. Japanese management scholars studying Taylor’s work called this the basis for Plan-Do-See (計画-実施-検討) style management. Ironically, the very thing Taylor is most criticized for — separating thinking from doing — set the stage for cyclical improvement thinking.
Management process school (1916-1951) — Henri Fayol (1916) identified core management functions including planning and controlling. Alvin Brown (1947) argued that management activities should be understood as a circular rotation, not a straight line. R. T. Livingston (1949) described a “Cycle of Enterprise.” William Newman’s Administrative Action (1951) included a circular diagram of management functions and was later translated into Japanese. This tradition established that management is an ongoing cycle, not a sequence you complete once.
CCS management courses (1949-1950) — Homer Sarasohn and Charles Protzman, working under the Civil Communications Section of the American occupation, ran management seminars for Japanese executives beginning in 1949 — before Deming’s arrival. Their courses covered industrial management fundamentals, systems thinking, and quality as a management responsibility. These were the first postwar channel through which American management thinking entered Japan.
Walter Shewhart (1924-1939) — Shewhart created the control chart at Bell Labs in 1924 and described a three-stage model for manufacturing: specification, production, and inspection. His 1939 book mapped these directly onto the scientific method: specification as hypothesis, production as experiment, inspection as test. This made the cycle scientific, grounded in statistical evidence — a different contribution from the management thinkers who made it circular.
W. Edwards Deming in Japan (1950) — Deming, who had edited Shewhart’s 1939 book, was invited to Japan by JUSE in 1950 to teach statistical quality control. What he presented was the Shewhart Cycle — a product-focused wheel of design, manufacture, sell, and research. He drew it as a circle to emphasize continuous improvement. The Japanese honored him by calling it the “Deming Wheel” (デミングの輪). But the bulk of his eight-day course was statistical process control. The wheel was a relatively small part of a course aimed primarily at engineers and statisticians. JUSE established the Deming Prize (デミング賞) in 1951.
The Japanese Reconstruction (1952-1964)
The transformation of the Deming Wheel into PDCA was accomplished inside Japan over a decade of work by Japanese thinkers who merged two separate traditions — the quality tradition from Shewhart and Deming and the management tradition from Fayol, Newman, and Juran.
Shigeru Mizuno (1952-1959) — Mizuno, a quality and management scholar, is the hidden protagonist of the PDCA story. As early as 1952, he was interpreting the Deming Cycle for a Japanese audience. By 1954, he had begun translating the quality cycle into general management language using four Japanese terms: 企画 (kikaku, planning), 作業 (sagyō, work), チェック (chekku, checking), 処置 (shochi, corrective measures). This was strikingly close to the final PDCA form — a full decade before Ishikawa named it. In a landmark 1959 paper with Hiroshi Tomizawa, Mizuno formally distinguished the quality cycle (Deming’s product-focused wheel) from the management circle (applicable to all organizational activity), and unified both under a common four-stage structure.
Joseph Juran (1954) — Juran’s lectures at JUSE shifted the conversation from statistical methods to management’s responsibility for quality. He emphasized that quality was a leadership function, not merely a technical one. This strengthened the management interpretation of the cycle and catalyzed the shift from quality-specific to management-general PDCA.
Kaoru Ishikawa (1964) — In New Introduction to Quality Control (1964), Ishikawa gave the cycle the name the world would adopt: Plan, Do, Check, Action — PDCA. He was not inventing from scratch — the four-part structure had been in Japanese circulation for a decade, developed primarily by Mizuno. What Ishikawa did was codify it, simplify it, and make it practical enough to spread. He explicitly positioned PDCA as replacing the older Plan-Do-See, arguing that “See” was too passive. PDCA replaced it with two demanding steps: “Check” (deliberate evaluation) and “Action” (corrective measures or standardization). He also broke it into six practical steps for use by frontline workers in QC circles.
PDCA was in use at companies like Toyota before Ishikawa’s 1964 publication. Toyota introduced company-wide TQC in 1961 with JUSE faculty — including Mizuno and likely Ishikawa — directly involved in the training and implementation. Ishikawa’s book codified for a broad audience what JUSE had already been teaching inside companies.
Deming’s Reaction
When Deming encountered PDCA in the 1980s, he did not recognize it as his own work. In a 1980 roundtable at the U.S. Government Accountability Office, he was asked how PDCA related to his Deming Circle. His response: “They bear no relation to each other.” In a 1991 letter: “What you propose is not the Deming Cycle. I don’t know the source of the cycle that you propose. How the PDCA ever came into existence I know not.”
Deming’s confusion was genuine. He did not speak, read, or write Japanese. The decade of careful intellectual work by Mizuno, Tomizawa, and Ishikawa — merging his product-focused Shewhart Cycle with the management process tradition into a broader general-purpose framework — had taken place entirely in Japanese-language publications that Deming had no access to. Despite his continued connection to Japan through the Deming Prize and annual visits to the awards ceremony, the ongoing education inside Japanese companies was conducted by JUSE faculty and Japanese scholars, not by Deming. When he finally saw the result, he understandably believed something had been lost in translation.
In later years, Deming advocated for Plan-Do-Study-Act (PDSA), objecting specifically to “Check” (which he felt implied simple pass/fail inspection rather than the deeper scientific learning Shewhart had intended). PDSA found a following in healthcare and some quality improvement communities, but PDCA had already become embedded in the Deming Prize criteria, in company training standards, and in daily practice worldwide. The terminology debate was never fully resolved.
What matters most, however, is not the words. The underlying message Deming brought to Japan in 1950 — that improvement is cyclical, that it must be grounded in data, and that quality is built through continuous learning — was thoroughly absorbed by Japanese industry. Mizuno, Ishikawa, and their colleagues did not corrupt Deming’s teaching. They extended it, generalized it, and made it practical for an entire nation’s management system. The result was more powerful than what any single contributor had envisioned.
Adoption at Toyota
Toyota adopted PDCA as part of its company-wide TQC implementation beginning in 1961. But PDCA at Toyota is not merely a quality tool — it became the underlying logic of the entire management system:
- A3 problem solving is PDCA on a single sheet of paper. The left side of the A3 is Plan (current condition, problem statement, root cause analysis, proposed countermeasures). The right side is Do-Check-Act (implementation plan, results, follow-up).
- Hoshin kanri (policy deployment) is PDCA at the strategic level. Annual goals are planned, deployed, checked against results, and adjusted.
- Daily management is PDCA at the operational level. Standards are set (Plan), followed (Do), audited (Check), and updated when problems are found (Act).
- Kaizen is PDCA at the process level. Every improvement follows the cycle: understand the current condition, plan a change, test it, verify results, standardize.
How It Actually Works
Plan — The Most Important Step
At Toyota, the Plan stage receives the most time and attention. A common guideline is to spend 60-80% of the total effort on Plan — deeply understanding the current condition, collecting data, analyzing root causes, and developing well-reasoned countermeasures before implementing anything.
This is counterintuitive for action-oriented organizations that want to “just do it.” But Toyota’s experience is that thorough planning prevents the cycle of implementing a solution, discovering it does not work, implementing another solution, discovering that does not work either, and oscillating without progress. Slow, thorough planning leads to faster overall improvement.
Key activities in Plan:
- Go to the genba and observe the current condition directly
- Collect data — not opinions, not assumptions, but measured facts
- Define the gap between current condition and target condition
- Analyze root causes (5-Why, cause-and-effect diagram)
- Develop countermeasures that address root causes, not symptoms
- Predict the expected result — what specifically should change?
Do — A Test, Not a Rollout
The Do stage is an experiment, not full implementation. The countermeasure is tested on a small scale — one line, one shift, one machine — to see whether the predicted result actually occurs. This limits the blast radius if the change does not work.
Check — Did It Work?
Compare actual results to the prediction made during Plan. This comparison is the learning mechanism. If the result matches the prediction, you understood the problem correctly. If it does not, the gap between prediction and result tells you what you do not yet understand.
This is where most organizations fail. They implement changes (Do) and move on to the next project without checking whether the change actually produced the expected improvement.
Act — Standardize or Adjust
If the change worked: standardize — update standardized work, train everyone on the new method, and make the improvement permanent. If the change did not work: analyze why, and begin a new PDCA cycle with updated understanding.
The Act stage is also where the cycle connects to the next cycle. Standardization is not the end — it is the starting point for the next round of improvement.
Common Mistakes
Treating PDCA as Plan-Do-Plan-Do. The most common failure. Organizations plan a change, implement it, then move on to planning the next change — skipping Check and Act entirely. Without checking results, there is no learning. Without acting (standardizing), there is no retention. The organization is busy but not improving.
Rushing through Plan. The pressure to show progress drives teams to skip root cause analysis and jump to solutions. “We know what the problem is, let’s just fix it.” Shallow planning leads to countermeasures that address symptoms, not causes. The problem recurs, and the team starts over — losing more time than thorough planning would have required.
Confusing Do with full rollout. Do is a test, not deployment. Implementing a change across the entire operation before verifying it works on a small scale creates risk and makes it difficult to determine whether the change was effective.
Not defining expected results in Plan. Without a specific, measurable prediction, the Check stage has nothing to compare against. “We expect the defect rate to decrease” is not a prediction. “We expect the defect rate to decrease from 2.5% to below 1.0% within two weeks” is a prediction that can be checked.
Treating PDCA as a project management tool. PDCA is a thinking discipline, not a project template. It works at every level — from a team leader solving a daily problem in 30 minutes to an executive aligning a three-year strategic plan. When organizations turn PDCA into a form to fill out, they lose the thinking and keep only the paperwork.