PDCA is How We Improve the Industry

PDCA: The Improvement Engine That Can Transform Construction If You Complete All Four Steps

The construction industry is genuinely hard. Confrontational, personally draining, riddled with waste. Rising material and labor costs. Shrinking margins. A waning supply of skilled people. These challenges are not accidents; they are symptoms of an industry that has not yet made continuous improvement a cultural norm. And the most direct path from those symptoms to something better is a practice most people have heard of and most organizations only partially do.

Plan, Do, Check, Act. PDCA. The iterative improvement cycle that sits at the heart of Lean thinking and that, when practiced in full, gives any organization a mechanism for making tomorrow better than today. When practiced in part which is how most teams use it, it generates activity without compounding learning.

Where PDCA Comes From

The concept of PDCA emerged from scientific methodology: develop an idea through observation, test it through experimentation, and refine or abandon the idea based on results. Dr. Walter Shewhart transformed that linear sequence into an iterative cycle. Edward Deming Shewhart’s student developed and popularized it in the 1960s, and was specific about the intention: it is not about completing one cycle and moving on. It is about cycling continuously until the intended result is achieved, with each cycle generating learning that makes the next cycle more effective.

Deming’s preferred framing was Plan-Do-Study-Act, with Study emphasizing that the Check phase is not just a verification step but a genuine learning exercise. Some practitioners use Adjust rather than Act, which better captures the intent: the fourth step is not just action, it is intentional adjustment based on what was learned, either standardizing what worked or returning to the Plan phase with better understanding.

The Four Steps in Full

Plan is where most of the work should happen, even though it is consistently where the least time is invested. The planning phase has five specific components: defining value from the customer’s perspective or the goal to be achieved, understanding existing standards and best practices that serve as the baseline, clarifying the gap between current performance and the target using measurable data, getting to the root cause of the gap rather than the symptom, and identifying the specific countermeasures not solutions, but countermeasures that address the root cause.

The word countermeasures rather than solutions is deliberate and important. A solution implies the problem is finished. A countermeasure implies the improvement is tested, verified, and then either standardized or adjusted. That framing keeps the continuous improvement flywheel spinning rather than treating each fix as a final answer. Intentionally developing countermeasures is what makes the cycle iterative rather than episodic.

The tools that support the Plan phase are numerous and worth knowing. Conditions of satisfaction ensure the problem being solved actually addresses what customers value. Gemba walks going to see the problem firsthand, talking to the people closest to it, ground the analysis in reality rather than in assumptions. Process mapping makes the actual flow of work visible to everyone simultaneously. The 5 Whys drives from symptom to root cause through repeated inquiry. Cause and effect diagrams structure the identification of potential root causes. And the A3 is the one-page format that holds the entire PDCA cycle in a single visible document, forcing all phases to be completed rather than allowing the cycle to stop after Do.

Do is where countermeasures are implemented but on a test basis. Not a full rollout. A controlled experiment with limited scope so that the cost of learning from an ineffective countermeasure is minimized. The implementation plan identifies who does what by when. The data to be collected during the test is specified in advance so the Check phase has something to measure against. The scientific method is followed: execute the plan, observe the results, record the data.

Check is the most overlooked phase and the one that makes PDCA genuinely continuous rather than cyclical only in theory. The Check phase asks three questions: what did you expect to happen, what actually happened, and what did you learn? The gap between expectation and outcome is the information, it tells the team whether the countermeasure addressed the root cause effectively, whether there were unintended consequences, and what needs to be different in the next cycle.

Most teams skip Check because they assume the countermeasure worked. They move on. And then six months later the same problem surfaces again because the countermeasure was never verified, the root cause was never confirmed as addressed, and no learning was institutionalized. Only performing Plan and Do wastes most of the value of the effort already invested.

Act or Adjust is the decision step that closes one cycle and either opens the next or locks in the improvement. If the Check phase reveals that the countermeasure did not produce the intended result, the team goes back to Plan with better information: the original root cause analysis was incomplete, or the countermeasure addressed the wrong cause, or unintended consequences need to be accounted for. If the Check phase confirms the countermeasure worked, the team standardizes, updates the process documentation, trains people to the new standard, and ensures the improvement is accessible to everyone who needs it rather than living in the memory of the team that ran the cycle.

An Example from Design and Construction

The PDCA cycle is operating every time a design team produces and refines a model. The architect interprets what the customer wants and develops a design intent, this is Plan. The team uses that design to create a working model, this is Do. The team runs clash detection and coordinates with trade partners to confirm the design works as intended, this is Check. And the model is updated to resolve the issues discovered until it is ready for fabrication, this is Act. The cycle repeats until the design is resolved. When teams do this well, each iteration is faster and more productive because the Check phase genuinely informs what changes the next iteration needs to make.

Here are the warning signs that a team’s PDCA practice is incomplete:

• Countermeasures are implemented and never followed up on to verify whether they worked.
• The same problems surface repeatedly on different projects or in different phases of the same project.
• Improvements are documented in lessons-learned logs but never make it into the standard work that governs how the next project begins.
• The Check phase is replaced with an assumption that the change worked because nothing visibly went wrong immediately.
• Learning stays with the individual who ran the improvement cycle rather than becoming organizational knowledge.

The Specific Challenge in Construction

The AEC industry has historically been good at planning and doing. The improvement opportunity is concentrated in Check and Act. One reason is organizational: projects end and teams disperse before the Check phase can fully assess whether the changes made during the project actually held and produced lasting results. Another reason is cultural: the industry’s orientation toward immediate results makes the time investment of a genuine Check phase feel like overhead rather than production.

Both of these are system problems, not people problems. Organizations that create the structural conditions for Check and Act, project retrospectives, communities of practice, shared A3 libraries, standing monthly improvement reviews build the mechanisms that make PDCA work as a continuous cycle rather than as a two-step process. The team that checks whether its countermeasures worked and adjusts accordingly is the team that compounds its improvement over time. Every cycle generates learning that makes the next cycle more effective. The value is not in any single cycle; it is in the accumulation.

At Elevate Construction, the PDCA cycle is embedded in the weekly work planning process, in the retrospective practice at the end of every training event, and in the A3 problem-solving framework that runs through project consulting engagements. Percent plan complete is not tracked to assign blame, it is tracked to generate the Check that informs the Adjust. Root cause analysis of missed commitments is not a bureaucratic exercise; it is the system design update that prevents the same miss from recurring. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

To survive and improve, we must practice all four steps. Plan with genuine depth. Do on a test basis. Check with honest measurement. Act by standardizing what works or returning to Plan with better information.

On we go.

Frequently Asked Questions

What is the difference between a countermeasure and a solution in PDCA thinking?

A solution implies the problem is finished and the work is done. A countermeasure implies the improvement is a tested response to a root cause, one that will be verified in the Check phase and either standardized if effective or adjusted if not. The framing keeps the improvement cycle continuous.

Why is Check the most overlooked phase?

Because most teams assume their countermeasure worked and move on once it is implemented. Without a deliberate Check, the gap between what was expected and what actually happened is never examined which means the learning that would make the next cycle more effective never happens.

What is the role of standardization in the Act phase?

When the Check phase confirms a countermeasure worked, standardizing means updating the process documentation, training people to the new standard, and ensuring the improvement is accessible to everyone who needs it, not just to the team that ran the cycle. Without standardization, the improvement lives in memory and disappears when the team moves on.

How does PDCA connect to A3 problem solving?

The A3 format is structured around the PDCA cycle, the sections of an A3 correspond to Plan, Do, Check, and Act. Using the A3 forces all four steps to be completed rather than allowing the cycle to stop after Do, which is what happens when there is no structured framework requiring follow-up.

Why does PDCA need to be iterative rather than a single cycle?

Because complex problems rarely yield their full root cause in one cycle. The learning from the first cycle especially from the Check phase reveals aspects of the problem that were not visible before the first countermeasure was tested. Each cycle generates better understanding that makes the next cycle more effective.