pdca problem solving form

How it works

For Business

Join Mind Tools

Article • 7 min read

PDCA (Plan Do Check Act)

Continually improving, in a methodical way.

By the Mind Tools Content Team

Also known as PDSA, the "Deming Wheel," and "Shewhart Cycle"

Imagine that your customer satisfaction score on a business ratings website has dipped. When you look at recent comments, you see that your customers are complaining about late delivery, and that products are being damaged in transit.

So, you decide to run a small pilot project for a month, using a new supplier to deliver your products to a sample set of customers. And you're pleased to see that the feedback is positive. As a result, you decide to use the new supplier for all your orders in the future.

What you've just done is a single loop called the PDCA Cycle. This is an established tool for achieving continuous improvement in your business.

The PDCA approach was pioneered by Dr William Deming, and we've worked closely with The Deming Institute to produce this article. In it, we outline the key principles of PDCA, and explain when and how to put them into practice.

Click here to view a transcript of this video.

What Is PDCA?

In the 1950s, management consultant Dr William Edwards Deming developed a method of identifying why some products or processes don't work as hoped. His approach has since become a popular strategy tool, used by many different types of organizations. It allows them to formulate theories about what needs to change, and then test them in a "continuous feedback loop."

Deming himself used the concept of Plan-Do- Study -Act (PDSA). He found that the focus on Check is more about the implementation of a change.

He preferred to focus instead on studying the results of any innovations, and to keep looking back at the initial plan. He stressed that the search for new knowledge is always guided by a theory – so you should be as sure as you can that your theory is right! [1]

The Four Phases of the PDCA Cycle

With the PDCA cycle you can solve problems and implement solutions in a rigorous, methodical way. Let's look at each of the four stages in turn:

First, identify and understand your problem or opportunity. Perhaps the standard of a finished product isn't high enough, or an aspect of your marketing process should be getting better results.

Explore the information available in full. Generate and screen ideas, and develop a robust implementation plan.

Be sure to state your success criteria and make them as measurable as possible. You'll return to them later in the Check stage.

Once you've identified a potential solution, test it safely with a small-scale pilot project. This will show whether your proposed changes achieve the desired outcome – with minimal disruption to the rest of your operation if they don't. For example, you could organize a trial within a department, in a limited geographical area, or with a particular demographic.

As you run the pilot project, gather data to show whether the change has worked or not. You'll use this in the next stage.

Next, analyze your pilot project's results against the criteria that you defined in Step 1, to assess whether your idea was a success.

If it wasn't, return to Step 1. If it was, advance to Step 4.

You may decide to try out more changes, and repeat the Do and Check phases. But if your original plan definitely isn't working, you'll need to return to Step 1.

This is where you implement your solution. But remember that PDCA/PDSA is a loop, not a process with a beginning and end. Your improved process or product becomes the new baseline, but you continue to look for ways to make it even better.

The four stages of the cycle are illustrated in Figure 1, below:

PDCA Model courtesy of The W. Edwards Deming Institute®.

When to Use PDCA

The PDCA/PDSA framework works well in all types of organizations. It can be used to improve any process or product, by breaking them down into smaller steps or development stages, and exploring ways to improve each one.

It's particularly helpful for implementing Total Quality Management or Six Sigma initiatives, and for improving business processes generally.

However, going through the PDCA/PDSA cycle can be much slower than a straightforward, "gung ho" implementation. So, it might not be the appropriate approach for dealing with an urgent problem.

It also requires significant buy-in from team members, and offers fewer opportunities for radical innovation – which may be what your organization needs instead.

How to Use PDCA to Improve Personal Performance

While PDCA/PDSA is an effective business tool, you can also use it to improve your own performance:

First, Plan: Identify what's holding you back personally, and how you want to progress. Look at the root causes of any issues, and set goals to overcome these obstacles.

Next, Do: When you've decided on your course of action, safely test different ways of getting the results that you want.

Then, Check: Review your progress regularly, adjust your behavior accordingly, and consider the consequences of your actions.

Finally, Act: Implement what's working, continually refine what isn't, and carry on the cycle of continuous improvement.

The PDCA/PDSA cycle is a continuous loop of planning, doing, checking (or studying), and acting. It provides a simple and effective approach for solving problems and managing change. The model is useful for testing improvement measures on a small scale before updating procedures and working practices.

The approach begins with a Planning phase in which problems are clearly identified and understood, and a theory for improvement is defined. Potential solutions are tested on a small scale in the Do phase, and the outcome is then studied and Checked.

Go through the Do and Check stages as many times as necessary before the full, polished solution is implemented, in the Act phase of the cycle.

You've accessed 1 of your 2 free resources.

Get unlimited access

Discover more content

When work involves socializing.

How to Plan and Enjoy Work Events

Project Schedule Development

Planning the Timing and Sequence of Project Activities

Add comment

Comments (0)

Be the first to comment!

Team Management

Learn the key aspects of managing a team, from building and developing your team, to working with different types of teams, and troubleshooting common problems.

Sign-up to our newsletter

Subscribing to the Mind Tools newsletter will keep you up-to-date with our latest updates and newest resources.

Subscribe now

Business Skills

Personal Development

Leadership and Management

Member Extras

Most Popular

Newest Releases

SWOT Analysis

How to Build a Strong Culture in a Distributed Team

Mind Tools Store

About Mind Tools Content

Discover something new today

Top tips for delegating.

Delegate work to your team members effectively with these top tips

Ten Dos and Don'ts of Change Conversations

Tips for tackling discussions about change

How Emotionally Intelligent Are You?

Boosting Your People Skills

Self-Assessment

What's Your Leadership Style?

Learn About the Strengths and Weaknesses of the Way You Like to Lead

Recommended for you

Atomic habits.

By James Clear

Book Insights

Business Operations and Process Management

Strategy Tools

Customer Service

Business Ethics and Values

Handling Information and Data

Project Management

Knowledge Management

Self-Development and Goal Setting

Time Management

Presentation Skills

Learning Skills

Career Skills

Communication Skills

Negotiation, Persuasion and Influence

Working With Others

Difficult Conversations

Creativity Tools

Self-Management

Work-Life Balance

Stress Management and Wellbeing

Coaching and Mentoring

Change Management

Managing Conflict

Delegation and Empowerment

Performance Management

Leadership Skills

Developing Your Team

Talent Management

Problem Solving

Decision Making

Member Podcast

PDCA (Plan-Do-Check-Act)

What is the PDCA (Plan-Do-Check-Act) Cycle

Plan-Do-Check-Act Cycle (PDCA) is a four-step, iterative by-design method used for control and continual improvement of processes and products. It is also known as the Plan-Do-Study-Act (PDSA) cycle, Deming cycle, Control Circle/Cycle or the Shewhart cycle.

PDCA is an evidence-based participatory approach to problem-solving and is found to be an effective tool for quality improvement.

Origin of PDCA

The beginnings of PDCA emerged from the principles of the ‘Scientific Method’, which originated with Galileo but has its roots in the teachings of Aristotle. It is a method for developing ideas based on observation, then testing them through experiments and finally refining, changing, or eliminating the ideas. [2]

Dr. Walter Shewhart first adapted the scientific method for industry and presented it as a linear flow of ‘specification’, ‘production’ and ‘inspection’. In 1939, he changed the linear sequence to a cycle to show how refinement and change lead to an iterative approach to product development.

The Shewhart cycle was further developed by W. Edwards Deming in what became known as the ‘Deming Wheel’.

In 1950, Deming presented his ideas to the Japanese Union of Scientists and Engineers (JUSE) which then was popularized as the Plan, Do, Check, Act cycle or PDCA. [2]

Why use PDCA

Organizations often plan and then intend to execute, but the reality is neither linear nor predictable for this approach to be effective in reaching the target conditions.

Regardless of how well a plan is made, they must navigate a zone of uncertainty commonly referred to as the “Grey Zone.” Unforeseen problems, abnormalities, false assumptions, and obstacles will appear along the path to any target.

A good analogy is a person climbing stairs in the dark with a flashlight. Because the target condition lies beyond the reach of the flashlight, the path to attaining it cannot be predicted with exactness. Thus, the person must find that path by experimenting.

This is the central approach of PDCA. To expect uncertainty and pay attention to adjust along the way based on learnings. PDCA provides a practical means of attaining a challenging target condition by formulating hypotheses and testing them with information obtained from direct observation.

The Plan-Do-Check-Act (PDCA) cycle

The procedure or steps of experimentation in the PDCA cycle are summarized as below:

The four stages of PDCA

PDCA’s four stages constitute a scientific process of acquiring knowledge and are explained in more detail as follows:

P is for Plan

In the Planning stage, problems are identified and analyzed according to the following order:

• Select and prioritize the problems to be analyzed
• Clearly define the problem and establish a precise problem statement
• Perform situation analysis (to be used as baseline data)
• Set a measurable goal
• Perform root cause analysis (identify potential causes of problems)
• Identify intervention(s) that will address the root causes of problems
• Select an intervention and develop an action plan

D is for Do

At this stage, the team implements an action plan developed in the previous stage to make the desired changes. This involves the following steps:

• Execute the action plan on a trial or pilot basis
• Practice the proposed method(s)
• Make the changes
• Don’t strive for perfection but look for what can be done in a practical way

C is for Check

At this stage , data is collected once again to measure if the actions taken have improved the situation. It involves the following steps:

• Check whether the standard is being followed
• Measure the indicator and compare it with the baseline. Record the results
• Check what is working and what is not
• Identify systematic changes
• Practice and improve the activities as per the defined method

A is for Act

In the Act phase, interventions that are found to be effective are standardized by developing Standard Operating Procedures (SOPs), which involve the following steps:

• Continue activities that went as planned and were found effective
• Review (why) activities that did not perform well and propose changes
• Adopt the intervention(s)/ solution(s) as standard (standardize)
• Plan ongoing monitoring of the intervention(s)/ solution(s)
• Continue to look for incremental improvements and refine intervention(s)/ solution(s)
• Look for the next improvement opportunity

At the end of the fourth stage, the PDCA cycle restarts with the aim to solve another problem (or further improve the same problem) to achieve a continuous and uninterrupted improvement.

Seven steps in the PDCA cycle

PDCA cycle consists of seven steps spread over four stages, as shown:

Step 1: Selection and problem prioritization

A problem is a brief description/statement of the weakness in the process or an issue to be solved. The tool most often used in this step is a Flowchart [6] . Alternatively, if a single problem is to be selected from a set of problems, a Selection Matrix [7] or a Fish Bone Diagram [8] may be used.

Selecting a problem is an iterative process where subsequent steps could lead to further refinement of the definition. A good problem should:

• Be customer‑focused.
• Complement the company’s and division’s goals.
• Address a weakness
• Be measurable
• Have a high probability of success within a reasonable time frame (3‑4 months)
• Be well-framed in one complete sentence
• Avoid the use of abstract words, acronyms, and location‑specific lingo
• Be action‑oriented
• Avoid the use of absolutes
• Address one of the 5 evils (defects, delays, mistakes, waste, accidents).
• Avoid stating the cause in the problem definition. (This is jumping to Step 3.)
• Avoid stating the solution in the problem definition. (This is jumping to Step 4.)

Problems can be prioritized based on:

• Their impact on the business
• Whether there are enough resources available to address them
• The ease of observing changes
• The extent to which team members have control

Step 2: Situation analysis

In this step, the focus is on gathering facts about the problem. The tool most often used at this point are Checksheets [9] and Pareto Charts [10] . Following are some of the key aspects of situation analysis:

• Before collecting data, all possible causes must be brainstormed.
• Ask 4W and 1H when collecting data: – Who is involved? – What problem/type of problem occurs? – When does it occur? – Which part of the process/type of product does it involve? – How much/many products/defects/etc. are involved?
• Limit data collection to what is needed. (Often, a sample will be sufficient.)
• Stratify (group) the data in many forms [11] .
• Zero down on a few probable causes using a Pareto chart.

Step 3: Root cause analysis

A root cause is the fundamental reason behind negative process outcomes. A fishbone diagram [8] is the primary tool for root cause analysis. The root cause must be controllable and is found using the following approach:

• Answer the question, “Why did this ‘problem’ occur?”
• Brainstorm around: – Contributing factors. – The root cause of the contributing factors.
• Follow a fact-based approach. Assuming to know the cause can be counterproductive.
• Interview people who know the process.
• Construct/refer to a Flowchart of the process.
• Construct a Cause/Effect Diagram.
• Recycle back to Step 2 if required.

Step 4: Identification of intervention

This step brings ideas together to address a problem’s root cause. It is important to be open to options and think creatively. Affected individuals must be involved, and preference must be given to improving existing processes before revamping them entirely. Experiments are run to test solutions.

The proposed intervention must:

• Prevent the reoccurrence of the root cause.
• Be practical to implement, efficient and affordable.
• Be free from conflict with other processes or activities.
• Address the 4W’s and 1H (discussed in Step-2).
• Have a timeline describing the implementation schedule.
• Have management support.
• Establish metrics that will confirm that the solution worked.

Step 5: Implementation of the intervention

Putting the implementation plan into action involves carrying out the ordered steps outlined below, implementing the change itself, and collecting the information that will indicate success.

• Review the objectives of the solution(s).
• Develop an action plan.
• Share the action plan with section staff.
• Identify the potential resistance.
• Determine the prerequisite(s) of the implementation.
• Develop a step-by-step guide to implement the action plan (Usually, the time for implementation is about 2 to 3 months, while the total time for one PDCA cycle is about 6 months).
• Assign responsibility for each activity.
• Determine what information is needed to monitor progress (using a checklist).

Teams must establish checkpoints periodically to verify if the implementation is going as planned and update everyone involved on the progress.

Step 6: Checking the effectiveness of implementation

Using tracking indicators, effectiveness can be checked through the following steps:

• Review data collection methods in Step 2
• Collect data using the same methodology
• Compare frequency before and after PDCA and calculate incremental reduction/ increase rate
• Make a Run Chart to observe the trend over time [12]
• Check achievement against the target set earlier in the aim statement.

The situation before and after PDCA can also be portrayed using a graph as shown below:

A Run Chart can be used to observe improvements over time. For example, the run chart (below) shows a decreasing trend in the number of patients who did not follow prescribed medication. This indicates the PDCA measures adopted by the hospital to address the issue have shown improvements over time.

Step 7: Standardization of effective interventions

At this stage, the activities found to be effective in reducing or eliminating the problems are standardized using the following steps:

• List effective interventions identified in the previous step.
• Develop documentation (SOPs) to adopt successful intervention(s).
• Develop a checklist to assess the progress of implementing standardized activities.
• Share the plan and checklist with all concerned.

Standardization brings several benefits such as:

• Reduces variability.
• Ease in training new staff.
• Reduced chance of strain and injuries (ensures safety for internal/ external clients).
• Ease of following well-established practices reduces task time.
• Increases staff confidence & motivation.

Discipline is the key to successful standardization of an effective intervention.

PDCA at Toyota

No organization has ever come close to matching Toyota’s stellar performance in automobile manufacturing. It has cultivated a culture of excellence, efficiency, and customer satisfaction like no other.

PDCA at Toyota uses “Rapid Cycles,” where individual PDCA cycles are turned as quickly as possible, sometimes even taking only minutes each. The idea is to not wait for a perfect solution but to take the step at the earliest with available resources so that teams can spot the next challenge.

Toyota believes that a provisional step “now” is preferable to a perfect step “later”, and invests in prototypes and experiments up front, which may seem like an extra expense but has proven to reduce cost in the long run.

Toyota uses single-factor experiments, that is, to address one problem at a time and only change one thing at a time in a process. This helps see cause and effect and better understand the process.

Toyota’s success is not due to sudden innovation or having air-tight plans but the ability to execute more effectively in the face of unforeseeable obstacles and difficulties. They spot problems at the process level much earlier when the problems are still small and address them quickly while uncovering information along the way.

Example of PDCA (the Toyota way)

Consider the process of getting up and going to work with a target condition of being in the car and ready to drive 60 minutes after waking up.

Here is one possible PDCA cycle for the process:

Assume that with the above PDCA plan, a person sits in the car to find that the morning routine took 64 minutes, or four minutes over the target condition.

What has he learned about the process from this experiment?

As depicted in the figure above, not much! The total time taken was over 60 minutes (too long), but it cannot be said where in the morning routine the problem lies. Also, it is too late to make an adjustment that would still achieve the target condition.

There are two things wrong with this PDCA experiment:

• The “check” comes too late to learn anything useful or to adjust on the way.
• The target condition specifies only an outcome. (it is not actually a target condition at all.)

Many seemingly large and sudden changes develop slowly. The problem is that organizations either fail to notice the little shifts taking place along the way or they do not take them seriously.

No problem is too small for a response. To be consciously adaptive, an organization must recognize abnormalities and changes as they arise and are still small and easy to grasp.

To be able to experiment in shorter cycles, a more detailed target condition is necessary. Such a target condition must generally include the following information:

• The steps of the process, their sequence, and their times
• Process characteristics
• Process metrics
• Outcome metrics

While a longer overall PDCA cycle must check the outcome, many short PDCA cycles must check process metrics along the way. Every step on the “staircase toward a target condition” is a PDCA cycle. Each step is a hypothesis, where what is learned from testing that hypothesis may influence the next step.

Accordingly, a modified and more effective experiment for the process of getting up and going to work, beginning with a better target condition, will look as follows:

As seen from the figure, the step “Make breakfast” has taken four minutes longer than the planned time. From this, it is not only known where the problem is, but an adjustment can also be made to the remaining steps to still achieve the 60-minute outcome.

Questions critical to PDCA

PDCA phase of the improvement, after a target condition has been established, needs to answer the following five questions that are built on one another.

The sequence of these five questions acts as a device to give a routine and a mental pattern for approaching any process or situation. These questions distill part of the improvement down to a point where it becomes accessible and usable by anyone.

1. “The plan-do-check-act procedure”. Whale Design, https://www.shutterstock.com/image-vector/plandocheckact-procedure-deming-cycle-fourstep-model-2169522173 Accessed 22 Jul 2023

2. “Shewhart cycle”. Praxis Framework, https://www.praxisframework.org/en/library/shewhart-cycle Accessed 19 Jul 2023

3. “Walter A Shewhart”. Wikipedia, https://en.wikipedia.org/wiki/Walter_A._Shewhart Accessed 19 Jul 2023

4. “W. Edwards Deming Photo Gallery”. The Deming Institute, https://deming.org/w-edwards-deming-photo-gallery/ Accessed 19 Jul 2023

5. “Toyota Kata: Managing People for Improvement, Adaptiveness and Superior Results”. Mike Rother, https://www.amazon.com/Toyota-Kata-Managing-Improvement-Adaptiveness-ebook/dp/B002NPC0Q2https://www.amazon.com/Toyota-Kata-Managing-Improvement-Adaptiveness-ebook/dp/B002NPC0Q2 Accessed 19 Jul 2023

6. “WHAT IS A FLOWCHART?”. American Society for Quality, https://asq.org/quality-resources/flowchart Accessed 20 Jul 2023

7. “WHAT IS A DECISION MATRIX?”. American Society for Quality, https://asq.org/quality-resources/decision-matrix Accessed 20 Jul 2023

8. “FISHBONE DIAGRAM”. American Society for Quality, https://asq.org/quality-resources/fishbone Accessed 20 Jul 2023

9. “CHECK SHEET”. American Society for Quality, https://asq.org/quality-resources/check-sheet Accessed 20 Sep 2023

10. “WHAT IS A PARETO CHART?”. American Society for Quality, https://asq.org/quality-resources/pareto Accessed 20 Sep 2023

11. “WHAT IS STRATIFICATION?”. American Society for Quality, https://asq.org/quality-resources/stratification Accessed 20 Jul 2023

12. “Run Chart: Creation, Analysis, & Rules”. Six Sigma Study Guide, https://sixsigmastudyguide.com/run-chart/ Accessed 21 Jul 2023

13. “PDCA Manual for Quality Improvement”. Quality Improvement Secretariat (QIS), Health Economics Unit, Health Services Division, Ministry of Health and Family Welfare, http://qis.gov.bd/wp-content/uploads/2019/04/2019_02_07_1549518374_241pdca.pdf Accessed 21 Jul 2023

Leave a Comment Cancel reply

Save my name and email in this browser for the next time I comment.

How to apply the Plan-Do-Check-Act (PDCA) model to improve your business

Reading time: about 7 min

• Professional development
• Project management

Most businesses want to improve. But when it comes to actually making needed changes, many fall short. Bureaucracy, silos, and even culture can block progress and stall innovation.

The Plan-Do-Check-Act model helps break companies out of stagnancy and transition to a system of continuous improvement. Learn how the PDCA cycle works and what benefits you can gain from using it at your company.

What is PDCA?

The Plan-Do-Check-Act (PDCA) model, also known as the Deming wheel or the Deming cycle, is an iterative method for continual improvement of processes, products, or services and is a key element of lean management.

The PDCA model was developed in the 1950s by William Deming as a learning or improvement process based on the scientific method of problem-solving. Deming himself called it by another term—the Shewhart cycle—because he created the model based on an idea from his mentor, Walter Shewhart.

As all of these names suggest, the PDCA cycle is a loop rather than an end-to-end process. The goal is to improve on each improvement in an ongoing process of learning and growth.

When should you use the PDCA process?

The Plan-Do-Check-Act model is a helpful tool that can be used for a number of applications:

• Exploring and testing multiple solutions in a small, controlled trial
• Avoiding waste by catching and adapting ineffective solutions before rolling them out on a large scale
• Implementing Total Quality Management or Six Sigma initiatives
• Developing or improving a process

What is great about the PDCA cycle is that it can be applied across industries and organizational types.

Pros and cons of PDCA

The PDCA cycle has a number of advantages and disadvantages. Consider both before you decide to apply Plan-Do-Check-Act to different projects.

Versatile: You can use PDCA in a variety of business environments and for a number of applications. Potential use cases include project management, change management, product development, and resource management.

Simple and powerful: The PDCA model is simple and easy to understand, yet it is a powerful driver for meaningful change and improvement while minimizing waste and increasing efficiency.

Hard to do: Though the model is simple, the work isn’t easy. Because PDCA breaks process improvements into smaller steps, it can be slow and probably isn’t a great solution for urgent projects.

Requires commitment: PDCA is not a one-time event. It is an ongoing, continuous process and therefore requires commitment and buy-in from the top down. Without committed leadership, the PDCA cycle can’t work effectively for the long term.

The PDCA model

Sold? Learn the four stages in the PDCA cycle (which you can probably guess from the name) to start using it.

The planning stage is for mapping out what you are going to do to try to solve a problem or otherwise change a process. During this step, you will identify and analyze the problem or opportunity for change, develop hypotheses for what the underlying issues or causes are, and decide on one hypothesis to test first.

As you plan, consider the following questions:

• What is the core problem we need to solve?
• Is this the right problem to work on?
• What information do we need to fully understand the problem and its root cause?
• Is it feasible to solve it?
• What resources do we need?
• What resources do we have?
• What are some viable solutions?
• What are the measures of success?
• How will the results from a small trial translate to a full-scale implementation?

During this stage, an affinity diagram can help you and your colleagues organize a large number of ideas into groups. Once you have determined your course of action, write down your expected results. You will check your results against your hypothesis and expectations in the “Check” stage.

The next step is to test your hypothesis (i.e., your proposed solution). The PDCA cycle focuses on smaller, incremental changes that help improve processes with minimal disruption.

Test your hypothesis with a small-scale project, preferably in a controlled environment, so you can evaluate the results without interrupting the rest of your operation. You might want to test the solution on one team or within a certain demographic.

Once you have completed your trial, it’s time to review and analyze the results. This stage is important because it allows you to evaluate your solution and revise your plans as necessary. Did the plan actually work? If so, were there any hiccups in the process? What steps could be improved or need to be eliminated from future iterations?

Your evaluation at this stage will guide your decisions in the next step, so it is important to consider your results carefully.

Finally, it is time to act. If all went according to plan, you can now implement your tried-and-tested plan. This new process now becomes your baseline for future PDCA iterations.

Consider the following questions before you act:

• What resources do you need to implement the solution at full scale?
• What training is needed for successful implementation and adoption?
• How can you measure and track the performance of the solution?
• What opportunities are there for improvement?
• What have we learned that can be applied to other projects?

If the plan did not pan out as expected, you can cycle back to the planning stage to make adjustments and prepare for a new trial.

Plan-Do-Check-Act example

So what does the PDCA model look like in action? 

In 2019, the Department of Obstetrics and Gynecology at the Ningbo Women and Children’s Hospital in China applied the Plan-Do-Check-Act model to shorten the emergency decision to delivery interval (DDI) time. This is the time it takes between the decision to conduct a caesarean section and the delivery of a newborn. Shortening this time period in emergency situations is critical to saving lives and improving patient outcomes. 

Here’s how they did it:

Plan: In 2019, the hospital had an average DDI time of 14.40 minutes. Their process analysis identified three main causes impacting DDI time: 

• A defective process
• Lack of first-aid experience
• Poor cooperation among departments

Do: The team developed improvement measures for each cause including: 

• Simplifying the surgical process to speed up the pre-op routine
• Establishing a special DDI team to respond to emergency situations
• Standardizing DDI team working processes
• Creating an emergency treatment team, featuring senior doctors with clinical first-aid experience
• Implementing a variety of regular training, such as obstetrical safety meetings, emergency C-section process classes, and practical and theoretical trainings
• Conducting multi-department emergency treatment drills

Check: The hospital monitored and analyzed progress monthly, creating regular evaluation summaries and refining the cause analysis and improvement measures over time. 

Act: After refining their processes, the hospital’s improvements optimized C-section delivery processes, increased collaboration across departments, and shortened the average emergency DDI to 12.18 minutes in 2020.

Supporting Kaizen with the PDCA cycle

The Plan-Do-Check-Act model is a particularly useful tool for companies who follow the Kaizen method . Kaizen is an organizational mindset and culture focused on small, frequent changes that lead to significant improvements over time.

The PDCA cycle supports the Kaizen philosophy by providing the framework for developing and implementing continuous improvements.

Using Lucidchart to continuously improve

Lucidchart is a visual workspace that helps teams and companies map out their processes and visualize their data in new ways. Use Lucidchart to visualize your PDCA cycle and help you through each step of the process. As you plan your project, you can create a fishbone (cause-and-effect) diagram to visualize problems and potential causes.

During the “Do” stage, map out the new processes you plan to try. Use data linking to connect real-time data to your diagrams and keep track of your results. Once you have a solution you’re ready to implement, use Lucidchart to create diagrams visualizing the new processes. Lucidchart makes it easy to share documents with your team so they can quickly learn and understand the changes.

If you’re continuously improving, it can be easy to lose track of your changes over time. Keep everyone on the same page by documenting your continual progress in Lucidchart.

Learn more about how to elevate your business.

Lucidchart, a cloud-based intelligent diagramming application, is a core component of Lucid Software's Visual Collaboration Suite. This intuitive, cloud-based solution empowers teams to collaborate in real-time to build flowcharts, mockups, UML diagrams, customer journey maps, and more. Lucidchart propels teams forward to build the future faster. Lucid is proud to serve top businesses around the world, including customers such as Google, GE, and NBC Universal, and 99% of the Fortune 500. Lucid partners with industry leaders, including Google, Atlassian, and Microsoft. Since its founding, Lucid has received numerous awards for its products, business, and workplace culture. For more information, visit lucidchart.com.

Related articles

The Kaizen methodology is an easy way to engage employees and develop a culture of continuous improvement. It strives to eliminate silos, egos, and waste and instead aims for efficient and standardized processes. See why you should use Kaizen and how you can get started.

No matter how good the idea, changes won't last without a solid process improvement plan in place. Learn the essential steps involved with every process improvement plan.

Bring your bright ideas to life.

or continue with

PDCA Template

Drive systematic problem-solving and foster organizational growth with the PDCA template.

Trusted by 65M+ users and leading companies

About the PDCA Template

T he PDCA template helps you streamline continuous improvement and problem-solving processes. This dynamic template offers an organized visual representation of the Plan, Do, Check, Act cycle, allowing teams to approach challenges with clarity and purpose.

How to use the PDCA template

The PDCA template shows the Plan, Do, Check, Act cycle . This four-step management methodology is predominantly used in quality control and project management. See what each segment of the template means:

This is the initial phase where the problem is identified, and a plan for solving it is developed.

The section labeled "Plan" prompts teams to brainstorm and think about the "How, Who, What, When, Where, and Why" of the problem at hand. This ensures all aspects of the problem and potential solutions are considered.

Once a plan is in place, this step involves executing that plan. It's where strategies are implemented, and ideas are tested in a controlled environment.

The "Do" section prompts teams to take action based on their plan. The phrase "Do it! Write it down." encourages documentation of actions and results, fostering transparency and accountability.

This is the evaluation phase. Here, the "Do" phase results are assessed to determine if the plan's objectives were achieved. It provides insights into what worked and what did not.

In the template, the "Check" circle is centralized, emphasizing its importance in the cycle. The surrounding text prompts users to evaluate their results critically, asking questions like "Changes to be done? Can you improve? If so, 'How, Who, What, When, Where, Why?'"

Based on findings from the "Check" phase, necessary adjustments are made in this stage. If the solution was effective, it could be implemented on a larger scale. If not, necessary refinements are made.

The "Act" section revolves around implementation. The directive "Implement the results into the new workflow" followed by guiding questions ensures that any improvements are properly integrated and adjusted as needed.

In essence, the PDCA template offers a structured framework that helps teams identify potential solutions, test these solutions, measure their outcomes, and ultimately, implement sustainable improvements. The visual layout ensures that each phase is clearly defined, making the process understandable and actionable.

Why should you use a PDCA template?

Structured approach : It provides a systematic problem-solving and continuous improvement method.

Visualization : By mapping out each step, teams can visually track progress and pinpoint areas that need attention.

Collaboration : Multiple stakeholders can collaborate in real time, adding notes, feedback, and insights directly to the template.

Flexibility : The template is adaptable to various projects or processes, regardless of the industry or scale.

Continuous improvement : Using the template to follow the PDCA cycle reinforces an iterative approach, prompting teams to revisit and refine their strategies regularly.

Is the PDCA cycle exclusive to any specific industry?

No, the PDCA cycle is a universal methodology applicable across various industries for continuous improvement.

How often should teams revisit the PDCA template?

It's an ongoing process. Teams should revisit the template at the end of each cycle or project phase to ensure improvements are implemented and refined.

Can the template be integrated with other tools?

Yes, typically, templates can be integrated with a range of tools and platforms to enhance functionality and ease of use.

Is the template suitable for remote teams?

The template is designed to support collaboration, making it ideal for both in-house and remote teams.

Get started with this template right now.

Monthly Schedule Template

Works best for:.

Planning, Project Management

The Monthly Schedule Template is a flexible tool for long-term planning. It allows you to organize events, projects, and personal activities. You can easily adjust to accommodate changing priorities, unforeseen events, or long-term goals. This ensures sustained productivity and goal achievement.

Opportunity Canvas Template

Leadership, Decision Making, Strategic Planning

Features and capabilities — they make or break a product, which is why companies spend so much time and effort focusing on them. Sound like you? Try it with an Opportunity Canvas. This streamlined one-pager gives you and your team the power to improve your product by exploring the use cases, potential setbacks, strategies, challenges, and metrics. An Opportunity Canvas is ideal if you’ve already built a product, because you don’t need to consider the operational or revenue model.

Product Roadmap Template

Product Management, Roadmaps

Product roadmaps help communicate the vision and progress of what’s coming next for your product. It’s an important asset for aligning teams and valuable stakeholders – including executives, engineering, marketing, customer success, and sales – around your strategy and priorities. Product roadmapping can inform future project management, describe new features and product goals, and spell out the lifecycle of a new product. While product roadmaps are customizable, most contain information about the products you’re building, when you’re building them, and the people involved at each stage.

Project Status Report Template

Project Management, Documentation, Project Planning

When a project is in motion, the project manager must keep clients and shareholders updated on the project’s progress. Rather than waste time with constant meetings, leaders can send out weekly or daily project status reports to keep everyone informed. You can use the Project Status Report Template to streamline the report creation and distribution process.

666 Roadmap Template

Strategic Planning, Product Management, Roadmaps

For most companies, especially startups, it’s important to keep two perspectives in mind when planning for the future: your plan and your vision. Your plan is a close-up view of what you want to accomplish in the near future, while your vision provides a zoomed-out view of what you hope to accomplish in the long term. The 666 Roadmap encourages you to plan for the future by thinking about the next 6 years, 6 months, and 6 weeks. Use this roadmap to strategize, think about what you want to build, and focus on a concrete plan for the upcoming quarter.

Event Brief Template

Meetings, Workshops, Project Planning

For most any organization, throwing a big deal event is…a big deal. An event can bring in publicity, new clients, and revenue. And planning it can require a substantial chunk of your overall resources. That’s why you’ll want to approach it like a high-stakes project, with clearly outlined goals, stakeholders, timelines, and budget. An event brief combines all of that information in a single source of truth that guides the events team, coordinator, or agency—and ensures the event is well-planned and well-executed.

Plan, Do, Check, Act (PDCA)

PDCA is an improvement cycle based on the scientific method of proposing a change in a process, implementing the change, measuring the results, and taking appropriate action. It also is known as the Deming Cycle or Deming Wheel after W. Edwards Deming, who introduced the concept in Japan in the 1950s. It is also known as PDSA, where the “S” stands for “study”.

The PDCA cycle has four stages:

• Plan — determine goals for a process and needed changes to achieve them.
• Do — implement the changes.
• Check — evaluate the results in terms of performance
• Act — standardize and stabilize the change or begin the cycle again, depending on the results

PDCA is the foundation of continuous improvement or kaizen. Leaders set targets (plan) against a stable baseline of performance. Teams implement improvements (Do) to achieve the targets. Then they measure (Check) the change to evaluate performance against the target. If the team has achieved a measurable gain, it standardizes (Act) the new method by updating the standardized work. This ensures the improvement is stable.

History of PDCA

Walter A. Shewhart was the first to develop a repeating cycle for improvement dubbed the Shewhart Cycle:

Edward Deming expanded the Shewart cycle into a four-step pattern for Japanese audiences. The Deming cycle related heavily to the concept of product quality, innovation, and learning-by-doing over the entire life cycle of a product.

Specifically, the Deming cycle runs:

1.  Design  the product with appropriate testing. 2.  Make  the product and test it in production and in the lab. 3.  Sell  the product to the market. 4.  Test  the customer experience and redesign for improvement.

In 1951, the Japanese Union of Scientists and Engineers (JUSE) altered Deming’s framework into the more recognizable PDCA cycle. Although well over half a century has passed since the introduction of the Deming cycle to executives in Japan, most open-ended approaches still seek to repeat learning cycles as rapidly as possible, for obtaining customer feedback and making improvements in all pertinent areas.

The language may change slightly, but the basic thinking has not changed much. Consider the three-phase concept— Build ,  Measure ,  Learn —popularized by Eric Ries in his book,  The Lean Startup . His iterative process is fundamentally similar to both the original Shewhart and Deming cycles. Words may change or be slightly altered, but the timeless, classic concepts stay the same.

Additional Resources

• Test Your PDCA Thinking By Reading Your A3 Backwards
• Create a Real A3, Do More Than Fill In Boxes
• Hazards at the Huddle Board: How to Coach a Team Away from “Fast Thinking” to Disciplined PDCA
• Practical Guidance for Using Humble Inquiry in PDCA Problem Solving and Coaching
• The Key to Lean — Plan, Do, Check, Act!
• Four Types of Problems — Art Smalley

Privacy Overview

.css-s5s6ko{margin-right:42px;color:#F5F4F3;}@media (max-width: 1120px){.css-s5s6ko{margin-right:12px;}} Discover how today’s most successful IT leaders stand out from the rest. .css-1ixh9fn{display:inline-block;}@media (max-width: 480px){.css-1ixh9fn{display:block;margin-top:12px;}} .css-1uaoevr-heading-6{font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-1uaoevr-heading-6:hover{color:#F5F4F3;} .css-ora5nu-heading-6{display:-webkit-box;display:-webkit-flex;display:-ms-flexbox;display:flex;-webkit-align-items:center;-webkit-box-align:center;-ms-flex-align:center;align-items:center;-webkit-box-pack:start;-ms-flex-pack:start;-webkit-justify-content:flex-start;justify-content:flex-start;color:#0D0E10;-webkit-transition:all 0.3s;transition:all 0.3s;position:relative;font-size:16px;line-height:28px;padding:0;font-size:14px;line-height:24px;font-weight:500;-webkit-text-decoration:underline;text-decoration:underline;color:#F5F4F3;}.css-ora5nu-heading-6:hover{border-bottom:0;color:#CD4848;}.css-ora5nu-heading-6:hover path{fill:#CD4848;}.css-ora5nu-heading-6:hover div{border-color:#CD4848;}.css-ora5nu-heading-6:hover div:before{border-left-color:#CD4848;}.css-ora5nu-heading-6:active{border-bottom:0;background-color:#EBE8E8;color:#0D0E10;}.css-ora5nu-heading-6:active path{fill:#0D0E10;}.css-ora5nu-heading-6:active div{border-color:#0D0E10;}.css-ora5nu-heading-6:active div:before{border-left-color:#0D0E10;}.css-ora5nu-heading-6:hover{color:#F5F4F3;} Read the report .css-1k6cidy{width:11px;height:11px;margin-left:8px;}.css-1k6cidy path{fill:currentColor;}

• Project management |
• What is the Plan-Do-Check-Act (PDCA) cy ...

What is the Plan-Do-Check-Act (PDCA) cycle?

The PDCA cycle is a useful technique for addressing, analyzing, and solving business problems. Because the PDCA cycle is built on the process of continuous improvement, it offers a level of flexibility and iterative improvement. 

PDCA cycle history

The PDCA cycle was first introduced by Walter Shewhart , the father of statistical quality control. In his book, Economic control of quality manufactured product , Shewhart applied the scientific method to economic quality control. 

Shewhart’s thesis was further developed by W. Edwards Deming , who championed Shewhart’s work. Deming expanded on Shewhart’s idea and used the scientific method not only for quality control but also process improvement.

Deming went on to teach the method—which he called the Shewhart cycle—to Japanese engineers. There, the Shewhart cycle mixed with kaizen (the Japanese principle of continuous improvement , which was developed by Kaoru Ishikawa ), the Toyota production system, and lean manufacturing to become what we now call the Plan-Do-Check-Act (PDCA) cycle. 

Nowadays, the Plan-Do-Check-Act cycle is commonly used as part of lean project management .

This methodology has many names, including:

Plan-Do-Check-Act cycle, or PDCA cycle

Deming cycle or Deming wheel

Shewhart cycle

Control cycle

Plan-Do-Study-Act cycle or PDSA cycle 

When should you use the PDCA cycle?

The PDCA cycle is a framework for how to approach and resolve project management and process improvement problems. As a result, it can be implemented for a wide variety of projects. Teams that use the PDCA cycle effectively embrace the element of continuous improvement—rather than using the cycle for an end-to-end process, the PDCA cycle is a way to ensure continuous improvement and implement the iterative process . 

The Plan-Do-Check-Act cycle is particularly useful when you want to:

Streamline and improve a repetitive work process

Develop a new business process

Get started with continuous improvement

Rapidly iterate on change and see immediate results

Minimize errors and maximize outcomes

Test multiple solutions quickly

4 steps to use the PDCA cycle

The four steps of the PDCA process are in the name: planning, doing, checking, and actioning. Notably, this process is a cycle, so as soon as you reach the end, you can start over from the beginning again. 

The first step to any process improvement or project planning is to figure out what you need to do. Like any project plan , this includes a variety of information, including:

The project objectives

Success metrics

The project deliverables or end result

Project stakeholders

The project timeline

Any relevant project risks or constraints

You can use the PDCA cycle for a wide variety of projects. Whether you’re building a new project from scratch or using the PDCA as a quality improvement project, investing in a robust planning phase is a great way to set the project on the right track. 

Keep in mind that PDCA is a cycle. It’s okay if you don’t have all of the answers the first time around, since you’ll probably run this cycle multiple times. Each time you re-run the PDCA cycle, evaluate your project plan to ensure it’s up-to-date and accurate towards your project goals. 

Once you’ve ironed out your project plan, the next step is to try it out. Like most types of lean project management, PDCA embraces small, incremental changes. During the Do phase of the PDCA cycle, implement the project plan on a small scale to ensure it works. 

Review the test you ran during the Do phase of the PDCA cycle to ensure everything went according to plan. More likely than not, you will identify things to improve on during the Do phase. After all, it isn’t called continuous improvement for nothing! The Check phase is critical to finding these small things before they get too big and problematic. 

If necessary, revisit your project plan to ensure your project is still hitting your project objectives. Alternatively, if you realized you need to make a change to the project plan, you can also do so now. 

After the check, move to the Act phase, which includes rolling out the full project or process improvement. Don’t forget that the PDCA cycle is a cycle. If you need to, return to the Plan phase to continuously improve your project or processes. 

Pros and cons of the Plan-Do-Check-Act cycle

The PDCA cycle is a powerful tool to continuously improve, but there are also some disadvantages to using this system as well. Take a look at the pros and cons of the PDCA cycle: 

Helpful for teams looking to get started with continuous improvement

Flexible methodology for virtually any project

Quickly implement change and see results

Use the PDCA as your standard operating procedure to increase org-wide standardization without the use of a project management office (PMO)

Proven continuous improvement methodology

You need support from senior management in order for the PDCA cycle to be particularly effective

Value comes from running the cycle over and over again. Not an effective methodology if you only plan on doing it once. 

Requires time to implement and learn

Isn’t a great solution for urgent projects, since you typically expect to run the cycle multiple times

Planned-Done-Checked-Actioned

The PDCA cycle is an effective way to implement continuous improvement and problem solving. To get the most out of the PDCA cycle, set your projects up for success with project planning tools . Plan, manage, and track your team’s projects to hit your deliverables on time. 

Related resources

How Asana uses work management to optimize resource planning

Understanding dependencies in project management

Program manager vs. project manager: Key differences to know

Critical path method: How to use CPM for project management

The PDCA Cycle (30+ Plan Do Check Act Examples)

In today's busy world, everyone is looking for simple ways to do things better and faster. Enter the PDCA cycle. It's like a four-step dance for making things work smoothly.

The PDCA cycle is an improvement cycle that involves four steps: Plan, Do, Check, and Act, to help improve any business process or task.

If you want to make your work more organized or solve problems more efficiently, the PDCA cycle can be your go-to tool.

Introduction to the PDCA Cycle

The PDCA cycle is a tool that helps with project planning. It breaks down a process into manageable steps, helps you test them, and adjust to get better results.

The cyclical nature of PDCA is a simple guide to help groups and companies work better and keep improving.

It's not just a one-time thing. This PDCA model is like a circle that keeps going, helping you learn and grow. By going through the steps again and again, you can stay up to date and keep making things better.

Even though it started in factories with quality control, the PDCA cycle is now used everywhere—in hospitals, schools, tech companies, and even for personal goals. It's easy to use, and you don't need special training or tools. You just need to be ready to try new things and keep improving.

Brief History of PDCA

The origins of the PDCA cycle trace back to the early 20th century. A man named Walter Shewhart , often called the 'father of statistical quality control,' introduced the idea.

Shewhart was working in the world of manufacturing, seeking ways to make production more efficient and error-free. Remember, this was a time when factories were booming, and any way to save time or reduce mistakes was super important.

Building on Shewhart's thoughts, Dr. W. Edwards Deming further used the plan do check act cycle for something new in the mid-1900s.

Deming's work specifically dealt with rebuilding Japan's industry after World War II . He realized that for industries to succeed, they needed a simple and strong framework. And he favored the PDCA cycle as a means of problem solving and continuous improvement.

It's because of these two people who helped create the process that it's sometimes called the Deming Cycle, Deming Wheel, or Shewhart Cycle.

So, why should you care about this history? Because understanding where the PDCA cycle came from helps in appreciating its value. It's not just a trendy buzzword; it's a tested and proven method that's been helping businesses for almost a century.

4 Steps of the Plan Do Check Act Cycle

Simply put, the four stages or steps are: Plan, Do, Check, Act. In a way, this is project management plan that not only improves management practices but also eliminates ineffective elements.

This is the planning stage—the time you think and plan. You find a problem or a chance to do something and decide what you want to achieve. Basically, you set up project goals and potential solutions to business problems.

Now, it's action time. Do the plan you laid out in the previous stage. But don't just rush in! It's important to do this on a smaller scale first, like a pilot test. Consider it a 'trial run'. This way, you get to see how things work without fully committing.

After you've taken action, you pause and assess. You're looking back at the results of your 'Do' phase. Did it go as planned? Were there unforeseen hiccups? This is your moment of reflection. Remember, there are problably multiple solutions to any problem, so if this plan didn't work, you can try a new one.

Sometimes this method is called plan do study act, instead of plan do check act. So you can think of this as the time to study the data.

After looking at the results from the 'Check' step, you make changes. If things worked, you can do more of it. If not, you fix and improve. After making changes, you start the cycle again with 'Plan'.

In essence, the PDCA cycle is an ongoing journey of improvement. It's all about learning, repeating, and progressing.

The Importance of Continuous Improvement

The heart of the PDCA cycle lies in the principle of continuous improvement . In today's ever-evolving world, standing still is not an option. You either move forward, or you risk falling behind.

Continuous improvement isn't about chasing perfection. It's about the journey of getting better every day. It’s acknowledging that no matter how good a process or product is, there's always room to do better.

Here’s why it is crucial to continuously improve:

1. Adapting to Change : Just like seasons change, so do markets, customer preferences, and technologies. By continuously improving, you ensure that you're not left behind.

2. Efficiency and Productivity : Improving business processes means eliminating wastes and unnecessary steps. This results in faster outputs with fewer resources.

3. Employee Satisfaction : Believe it or not, people like being part of a system that gets better. It boosts morale and engagement. When employees see their feedback being used to make positive changes, they feel valued and involved.

4. Customer Satisfaction : Continuously improved products or services translate to happier customers. By showing that you’re committed to betterment, you not only keep loyal customers but also attract new ones.

5. Long-Term Success : Think of continuous improvement as investing in the future. Small enhancements today can lead to significant benefits in the long run.

Use-Cases of the PDCA Cycle

Let's shift our gaze from the theory of PDCA to its real-world applications. The plan do check act cycle is not limited to big businesses or specific industries; it can be used by anyone who wants to continuously improve processes.

In hospitals, patient care is the most important. By using the PDCA cycle, hospitals can make patient admissions easier, improve treatment plans, and perform better after-care procedures.

For example, if a hospital notices long wait times in the emergency room, they can Plan a strategy to make it better, Do a trial run with the new system, Check the results, and then Act to put the plan into place everywhere or change it based on the feedback from the trial run.

Schools and colleges are always looking for ways to improve student learning and involvement. The PDCA cycle can help with curriculum design, classroom management, or even in creating better ways for students to give feedback.

A school might notice students struggling with online learning. They can then make a plan to offer additional resources, test it out with a group, assess the results, and change accordingly.

Tech Startups

In the tech world, you need to keep up with changes. Startups can use the PDCA cycle to make better products, improve user experience, or market better.

Think of a new app with problems after it's launched. The company can make a plan to solve it, try the fix, see what users say, and then improve it for the desired outcome.

Personal Goal Setting

Beyond organizations, individuals can use the PDCA cycle for personal development. Whether it's fitness goals, learning a new skill, or financial planning, this cycle can be a guide.

Suppose you set a goal to read more books. You plan by setting aside time each day, try it out for a week, check if you're consistent, and then adjust based on challenges or insights.

Manufacturing

PDCA started in factories, and they can gain a lot from it. It can help improve products and make production faster.

If a factory finds more faulty products, they can use the PDCA cycle to find the problem, try fixes, see what works, and then use the best solution regularly.

Starting Your Own PDCA Cycle: Step-by-Step Guide

Let's walk through how you can start your own PDCA journey.

1. Identify a Challenge or Opportunity : Every journey begins with a destination in mind. Look for an area in your organization, project, or personal life that needs improvement or has potential for growth. It could be as simple as improving morning routines or as complex as recreating a product line.

2. Gather Data : Arm yourself with information. Understanding the current situation helps in setting realistic goals. If sales have dropped in your business, get numbers. How much? Since when? Any patterns?

3. Set Clear Objectives : Define what success looks like. If you're addressing the sales drop, decide on a target percentage increase. Be specific. Instead of saying "increase sales," aim for "increase sales by 10% in the next quarter."

4. Brainstorm Solutions : Think of strategies to meet your objective. If it's about sales, maybe you need better marketing, more training for the sales team, or even a new product feature.

5. Pilot Test : Remember the importance of the 'Do' phase being a trial run? Implement your solution, but start small. This reduces risks. Using our sales example, maybe first train a small sales team with a new technique and see how it works.

6. Evaluate Results : Once your pilot is done, check the outcomes. Did sales improve for the team that received new training? By how much? Were there any challenges?

7. Implement or Adjust : Based on your evaluation, take action and implement change yourself. If the new sales training worked well, roll it out for everyone. If not, revisit your strategies, adjust, and test again. This is the act phase.

8. Document Everything : Keep a record of your entire PDCA process. This not only helps in future cycles but also creates a way for your team to look at what worked, what didn't, and make incremental changes in their process improvement.

9. Loop Back : The PDCA cycle isn’t a one-time thing. After 'Act', circle back to 'Plan'. Maybe after addressing sales, the next cycle focuses on having your customers came back again and again.

10. Celebrate and Reflect : Lastly, every time you complete a cycle, take a moment to acknowledge the progress. Celebrate wins, no matter how small. And always reflect on lessons learned for future cycles.

Common Mistakes and How to Avoid Them

The Shewhart cycle is an iterative process. In other words, it's a continuous process improvement.

But, just as a juggler learns best from dropped balls, understanding common mistakes in the PDCA cycle can prepare you to avoid or address them before they happen.

1. Skipping the Planning Phase : In eagerness to act, it's tempting to jump straight into action. But remember, a house built on shaky foundation won't stand for long.

Strategy : Always invest time in thorough planning. This phase sets the tone for the entire cycle.

2. Ignoring Data : Operating on gut feelings or assumptions can lead you down the wrong path. The PDCA cycle relies on data-driven decisions.

Strategy : Consistently gather relevant information. Then analyze it. Let numbers guide your actions.

3. Setting Vague Objectives : Broad goals like "improve customer service" lack direction. Instead, be specific in your initial plan.

Strategy : Always aim for SMART (Specific, Measurable, Achievable, Relevant, Time-bound) objectives. Instead of "improve customer service," aim for "reduce customer complaints by 15% in the next two months."

4. Neglecting the 'Check' Phase : It's easy to move from action to adjustments without pausing. But without assessment, you might miss valuable insights.

Think of it like the scientific method, where you have a controlled environment and by looking at the success criteria you can make sure you avoid recurring mistakes.

Strategy : Always allocate time to evaluate results. It's this reflection that powers informed adjustments.

5. Resisting Change : Sometimes, looking at the data will show a need for significant changes. Resistance can slow or stop progress.

Strategy : Cultivate a growth mindset . Embrace changes as opportunities to learn and grow.

6. Stopping After One Cycle : Viewing the PDCA cycle as a one-off can limit its benefits. Remember, it's about continuous improvement.

Strategy : Always loop back. Each cycle offers a chance to refine further.

7. Working in Silos : Keeping the PDCA process in only one department or individual can limit its scope and effectiveness.

Strategy : Promote collaboration. Encourage cross-departmental input and feedback.

8. Fearing Failures : Not every cycle will lead to positive results. Fear of failures can slow innovation and risk-taking.

Strategy : Reframe failures as learning opportunities. Every setback is a setup for a better comeback.

9. Neglecting Documentation : Forgetting to record your processes and outcomes can lead to repeated mistakes.

Strategy : Maintain a detailed log of every PDCA cycle. This becomes a reference point for the next stage.

10. Overcomplicating the Process : The PDCA cycle is inherently simple. Overloading it with complexities can reduce its effectiveness.

Strategy : Stick to the basics. Keep the cycle streamlined and straightforward.

Pros and Cons of the PDCA Cycle

While the PDCA cycle has many benefits, it's important to be aware of its limitations too. Let's weigh both sides of this coin to give you an more rounded view.

Pros of the PDCA Cycle

1. Simplicity : At its core, the PDCA cycle is a straightforward four-step process. This makes it easy to understand, adopt, and communicate across teams.

2. Versatility : Whether it's a multinational corporation or your personal fitness goal, the PDCA cycle can be applied anywhere. Its universality is one of its strongest points.

3. Data-Driven : By relying on data and evaluations, the PDCA cycle reduces guesswork and ensures decisions are supported by hard evidence.

4. Continuous Improvement : The continuous loop promotes regular refinement, ensuring that internal and external processes and strategies are always evolving and improving.

5. Risk Mitigation : By emphasizing small-scale testing in the 'Do' phase, the PDCA cycle helps to identify potential issues or ineffective elements early on, reducing the chances of large-scale failures.

6. Empowers Teams : Since it's a collaborative work process, the PDCA cycle encourages team input and feedback, leading to more inclusive and holistic solutions.

Cons of the PDCA Cycle

1. Time-Consuming : Especially during the initial phases, the PDCA cycle can be time-intensive as teams gather data, plan, and test.

2. Potential for Overanalysis : The 'Check' phase, if not kept in check, can lead to "paralysis by analysis," where teams get too caught up in evaluating data and delay actionable steps.

3. Dependency on Data : While being data-driven is a strength, it can also be a limitation if there's a lack of quality data. Poor data can lead to bad decisions.

4. Requires Commitment : For the PDCA cycle to be effective, it requires consistent commitment from the team. Occasional or half-hearted attempts might not yield good results.

5. Scope for Subjectivity : While the process is data-driven, interpretations of the data can be subjective , leading to potential biases in decisions.

Real-Life Examples of the PDCA in Action

Stories have a way of making concepts stick. With strategic planning, people can reduce costs, have quality improvement, and progress regularly.

Let's step into the real world and explore some stories that show the PDCA cycle making a noticeable difference.

1. A Coffee Shop's Quest for the Perfect Brew : A local coffee shop noticed a dip in their morning sales. Using the PDCA approach, they planned a way for customers to tell them what they want. They then introduced new coffee blends on a trial basis.

After assessing customer feedback and sales data, they found that introducing cold brews and specialty lattes was a hit. The shop adjusted its menu, retrained its baristas, and saw a 20% rise in sales the following month.

2. School Attendance Improvement : A school was finding that students were absent a lot. The management planned a survey to understand the reasons. From the feedback, they introduced a mentorship program and more engaging extra-curricular activities.

After testing these out for a semester, there was a noticeable increase in student attendance. The school then acted by making these changes permanent and continued to monitor attendance rates for further improvements.

3. Tech Firm's Bug Battle : A tech startup's app had a lot of bugs after a major update. The team planned a way for users to report issues. They then put out smaller patches to address the most common problems.

Checking user reviews and bug reports, they realized the need for a more in-depth testing phase before updates. Acting on this, they changed their testing protocols, leading to more stable updates in the future.

4. Personal Fitness Journey : Mike wanted to get in shape. He planned a workout routine and a diet. For the first two weeks, he tested a mix of cardio and weights.

Checking his progress, he realized he enjoyed weight training more and saw better results with it. He then acted by focusing more on strength training and adjusting his diet to support muscle growth. By the full end to end process of three months, Mike had lost 15 pounds and increased his muscle mass.

5. Hospital's Patient Care Boost : A city hospital wanted to make it so patients could leave sooner after treatment. They planned by gathering data on current discharge processes.

They tried to improve processes by bringing a digital system to one department. Using this system, they found that paperwork was processed faster meaning patients could leave sooner. The hospital acted by implementing the digital system hospital-wide.

Frequently Asked Questions (FAQ)

1. What is the PDCA cycle? The PDCA cycle is a four-step method used to improve processes and systems. The steps are Plan, Do, Check, and Act.

2. Where did the PDCA cycle originate? The PDCA cycle has its roots in the early 20th century, introduced by Walter Shewhart and further refined by Dr. W. Edwards Deming.

3. Can the PDCA cycle be used outside of manufacturing? Yes, while it started in manufacturing, today the PDCA cycle is used in various sectors like healthcare, education, tech startups, and even for personal goals.

4. Why is the 'Check' phase crucial in the PDCA cycle? The 'Check' phase involves assessing results. It's essential for understanding what's working and what needs adjustment, ensuring the cycle's effectiveness.

5. What are the main benefits of the PDCA cycle? The PDCA cycle promotes continuous improvement, risk mitigation, data-driven decisions, and inclusivity in feedback and solutions.

6. Are there any common mistakes to avoid when implementing PDCA? Yes, some common mistakes include skipping the planning phase, setting vague objectives, and neglecting the 'Check' phase. It's crucial to be aware of these to make the most of the PDCA cycle.

7. How can I start implementing the PDCA cycle in my organization or personal life? Begin by identifying a challenge or opportunity. Gather data, set clear objectives, and then proceed through the Plan, Do, Check, and Act steps. Remember, it's a continuous cycle, so always loop back to the planning phase after acting.

8. Are there any real-life examples of the PDCA cycle in action? Absolutely! From coffee shops refining their brews to tech startups improving apps based on user feedback, the PDCA cycle has been effectively implemented in various scenarios.

9. How does the PDCA cycle encourage continuous improvement? By its very design, the PDCA cycle promotes revisiting and refining processes. By constantly looping back to the planning phase, it ensures that operations are always evolving based on feedback and results.

We've traveled quite a bit through the world of PDCA, haven't we? From its history to how it works and where it's used, we've covered a lot of ground. Now, let's wrap up what we've learned.

The PDCA cycle is like a step-by-step guide for making things better. Think of it as a map that helps you find better ways to do things. Each step, from planning to acting, helps you get better and learn from any mistakes.

In today's world, things change a lot and fast. That's why having a way to keep improving is super important. The PDCA cycle helps you do just that.

Whether you're in charge of a big company, a small team, or just trying to reach your own goals, the PDCA cycle can help.

Related posts:

• 70+ SMART Goal Examples (For Students, Losing Weight, Saving Money...)
• David Kolb (Psychologist Biography)
• 121+ Strengths Examples for Job Interviews
• 250+ Flirty Bet Ideas (For Couples + Consequences)
• 183+ Opportunities Examples for SWOT Analysis (Huge List)

Reference this article:

About The Author

Free Personality Test

Free Memory Test

Free IQ Test

PracticalPie.com is a participant in the Amazon Associates Program. As an Amazon Associate we earn from qualifying purchases.

Follow Us On:

Youtube Facebook Instagram X/Twitter

Psychology Resources

Developmental

Personality

Relationships

Psychologists

Serial Killers

Psychology Tests

Personality Quiz

Memory Test

Depression test

Type A/B Personality Test

© PracticalPsychology. All rights reserved

Privacy Policy | Terms of Use

Continuous Improvement Toolkit

Effective Tools for Business and Life!

A3 Problem Solving Template

A3 thinking is a logical and structured approach to problem solving adopted by Lean organizations around the world. It can be used for most kinds of problems and in any part of the business. This A3 template uses a four stages model that is based on the PDCA management philosophy. It makes the problem-solving progress visible to the entire team while allowing the lessons to be learned by others.

This template is a Microsoft Excel spreadsheet that you can use and modify to meet your specific requirements. For example, you may expand the implementation or follow-up plans by increasing the number of rows. The template is available in two variations: a user-friendly straightforward version, and a more detailed one that requires providing in-depth information.

A3 Template (32 KB)

A3 Template – Simple (216 KB)

A3 Template – Detailed (340 KB)

Related Templates

Written by:

CIToolkit Content Team

PDCA Problem Solving Kit: Analyze Causes

$  0 – $  50

The PDCA toolkit contains problem-solving templates in 34 languages to identify and eliminate root causes. By doing so, problems are effectively corrected and reoccurrence prevented. PDCA templates guide users through the Shewhart-cycle or Deming-wheel “plan-to-check-act” in five stages: (a) Record the problem, (b) Analyze the problem using the Ishikawa or Fishbone diagram, (c) Identify the root-causes using the 5-why method, (d) Take action to eliminate or reduce identified root causes, (e) Validate effectiveness, update standards, and formally close the process.

Description

Additional information, pdca templates in 22 languages.

To simplify implementation across countries and regions, we made the PDCA problem-solving templates available in English, Spanish, Portuguese, German, Dutch, French, Italian, Danish, Swedish, Norwegian, Finnish, Slovak, Czech, Hungarian, Russian, Bulgarian, Polish, Indonesian, Arabic, Turkish, Japanese, Chinese. Download now at start systematically solving problems.

(ar) العربية PDCA

PDCA čeština (cs)

PDCA dansk (da)

PDCA Deutsch (de)

PDCA english (en)

PDCA español (es)

PDCA suomi (fi)

PDCA français (fr)

PDCA magyar (hu)

PDCA Bahasa Indonesia (id)

PDCA italiano (it)

PDCA 日本語 (ja)

PDCA Nederlands (nl)

PDCA Norsk (nn)

PDCA polski (pl)

PDCA português (pt)

PDCA slovenčina (sk)

PDCA svenska (sv)

PDCA Türkçe (tr)

PDCA 中文 (zh)

Related products

Gemba Walk Guide: Go-See-Understand

Titanic Root Cause Analysis Poster: Learn the Method

LEAN6 Six Sigma Toolkit: Boost Quality

TRANSLEAN Lean Toolkit: Boost Efficiency

• MY LCI Login
• LCI Design & LCI Engineering Design Award
• Our Mission & Vision
• Our Strengths
• History of LCI
• How We Serve
• Board of Directors
• LCI Congress 2024
• Lean in Design Forum 2024
• Respect For People
• Communities
• New to Lean
• Learn by Pathway
• For Designers
• For Constructors
• Field Crew Huddle
• Assessments
• Classroom Learning
• Instructor Program
• LCI Publications
• Learning Videos
• Partner Programs
• Simulations
• Certification FAQs
• Certification Practice Quiz
• Designation Directory

• Lean Construction
• Lean Design
• Lean Project Delivery
• What is Lean?
• Founder’s White Papers
• Lean Construction Journal
• LCI Research
• Newsletter Archives
• Past Event Presentations
• Blog & Buzz
• Lean Consultant Members
• Member Directory

A3: Thinking, Reports, Examples & Templates

A3 thinking, an introduction to a3.

In the design and construction industry – as in all industries – complex problems arise daily. Each project contains hundreds of decisions containing thousands of variables, and sorting them out to arrive at the best outcome is critical.

A3 problem solving provides teams with a strategy to effectively and efficiently deal with problems that they encounter and decisions that need to be reached. In true Lean fashion, A3 process improvement brings the entire team into the collaborative problem-solving process and allows teams to embrace out-of-the-box solutions.

What is A3?

An A3 is a one-page report prepared on a single 11 x 17 sheet of paper that adheres to the discipline of PDCA thinking as applied to collaborative problem solving, strategy development or reporting. The A3 includes the background, problem statement, analysis, proposed actions, and the expected results.

The History

A3 thinking was developed by Toyota in the 1940s. Toyota believed that any problem should be capable of being explained and solved using one sheet of paper (an 11 x 17 sheet being the largest sized paper that is capable of being faxed and closest in size to the traditional A3). 

The company also believed that if a problem is too complex to fit onto an A3 report, it should be broken down into smaller bits that would be solved individually. If your problem cannot fit onto an A3, you should reconsider the scope of what you are hoping to accomplish.

Who Uses A3 Strategies?

Today, A3 strategies are deployed across various industries that employ Lean thinking such as:

• Design & Construction
• Manufacturing
• Project Management
• Engineering & Architecture
• Service Industries

LCI’s Meaning of A3

A3 thinking is an extremely useful tool when utilized correctly. By distilling the entirety of a problem on a single sheet of paper, A3 Lean thinking forces team members to collaborate and rationalize through the problem solving process. A3 thinking makes for more effective problem solving and produces written explanations that can then be passed on to senior management. An effectively completed A3 report will also build management’s confidence in the team and its ability to solve problems.

A3 Reporting

A well-written A3 report should show and explain the consideration that went into the counter-measure to the problem listed. Properly executed plans include the input of team members from all across the stakeholder spectrum and should allow members to emerge as leaders in its problem solving. A3 papers can also be referenced later, allowing the lessons learned during the process to be shared with future project teams.

Understanding A3 Thinking

A3 thinking does not provide a solution to the problem your team is facing. Rather, it guides your team’s process to help it reach the best possible countermeasure with the tools it has at its disposal.

An A3 report is to be filled out by one person on the team – the “champion” – who will gather assessments and intel from other members in a collaborative fashion. Bringing all of the knowledge and expertise of the team to bear when solving a problem is the best way to come to a satisfying outcome.

Problem Solving: An A3 Process

A3 thinking allows for many different types of decision-making. But ultimately, all decisions are fundamentally a form of problem solving. For example, A3 thinking can be deployed to guide the team in optimizing decisions during the design phase, or for solving a constructability challenge.

The First Step to A3 Thinking

The first step of the A3 process for problem solving is to correctly identify the problem. From unexpected lead times on materials to communication breakdowns among design teams, “problems” are in no short supply in the design and construction industry. Before engaging in A3, ask yourself the following questions about the problem you are working to solve.

Questions to Facilitate the Process

• What are you trying to address or solve?
• What is the current situation?
• What are clear Conditions of Satisfaction (CoS) I can develop?
• Where can I brainstorm and analyze the 5 whys/root cause ideas?
• What’s a recommendation I can put forth?
• What is my plan to implement the recommendation above (if applicable)?

State plan to check and adjust using the PDCA cycle.

More on the PDCA Cycle

PDCA stands for Plan, Do, Check, Adjust. Explore each element of this acronym for more information about how it supports both the problem solving questions above as well as A3 problem solving as a whole.

Identify an issue in your process and exercise continuous improvement by planning your course of change.

Perform your case study by applying the corrective actions outlined in the “plan” stage in an experimental manner.

Follow the performance of your experiment and measure it to determine whether it is having the desired effect.

If your plan worked, implement the change to the necessary areas of your process. If it did not, determine what you will do differently next time and repeat the cycle.

A3 Reports for Solutions

While A3 reports broadly follow the PDCA cycle, the actual journey of an A3 process is a bit more granular. Let’s analyze the various steps and sections of an A3 report.

Describe the problem, theme, or issue. List out all of the details including the champion’s name, date, and the names of all of the collaborators who will be helping with the report.

Establish the business context & importance. Provide additional information on the problem being addressed.

Current State

Describe what is currently known about the problem. Note potential variables and roadblocks that may stop your team from solving this problem and additional information you hope you acquire.

Future State or Goal

Identify the desired outcome for your experiment. Identify the Conditions of Satisfaction (CoS) for the project.

Analyze the situation and underlying cause.

Recommendation

Provide a recommendation for process improvement that your team can implement for the future.

Create a follow-up/review process.

A3 Examples

A3 thinking is frequently applied in Lean design and Lean construction during all phases of the process for the purposes of making sound decisions. In the example below, A3 thinking is applied to the process of learning Lean design and construction techniques.

A3 Template

The Lean Construction Institute seeks to educate companies all throughout the design and construction industry on Lean practices and methods. Here is our A3 template which you can use to guide your decision-making processes.

A3 Training

The Lean Construction Institute offers A3 training as well as tools , events , education , and networking opportunities for Lean practitioners in design and construction all around the world. Whether you’re a Lean expert or are just learning about Lean for the first time, LCI can provide the tools you need for problem solving and continuous improvement in your business.

Lean Assessments

How strong is your Lean knowledge? Take a Lean assessment to determine your current state so you have a baseline for improvement. Lean assessments are available for individuals, teams, and organizations alike. Whether you’re new to Lean or are an experienced Lean practitioner, Lean assessments are a great way to get started at LCI!

William R. (Bill) Seed, Executive Editor

Executive Editors: Kristin Hill, Katherine Copeland and Christian Pikel

More lean topics.

From 5s to IPD, explore more popular Lean design and construction topics below.

• What is the (PDCA) Plan, Do, Check, Act Cycle?
• Learn Lean Sigma
• Improvement Methodology

PDCA (Plan, Do, Check, Act) is a time-tested methodology that forms the backbone of continuous improvement in various industries. The PDCA cycle, which embraces simplicity and systematic progression, facilitates problem-solving and process improvement by following four distinct stages. These stages create a circular flow that promotes continuous refinement and adaptation.

The PDCA cycle provides a structured approach that can be tailored to various scenarios, whether you’re looking to address specific organizational challenges, standardize processes, or foster innovation. This article delves into the essence of PDCA, examining its four phases, applications, and why it is such an effective tool for continuous growth and improvement. Join us as we unpack the PDCA cycle’s dynamics, providing insights and practical advice on how to effectively apply this time-tested methodology in your organization or project.

Table of Contents

What is pdca.

PDCA (Plan, Do, Check, Act) is a four-step methodology for continuous improvement and problem solving in a variety of organizational processes. It starts with planning (Plan) a change or solution, then doing (Do) it on a small scale. The results are then evaluated (Check) to determine the effectiveness of the plan, leading to the final action (Act) of either broadly implementing the change or revising the plan. The cyclical nature of PDCA encourages continuous refinement and adaptation, making it a versatile tool for improving quality, efficiency, and innovation in a wide range of industries and settings.

Why use PDCA?

The PDCA (Plan, Do, Check, Act) cycle is an indispensable tool in the world of process improvement and project management, and here’s why it’s so widely embraced:

1. Simplicity and Structure:

PDCA offers a simple and structured approach that anyone can follow. Its four-stage cycle – Plan, Do, Check, Act – provides clear guidelines that can be applied to various problems and processes. This simplicity makes it accessible to team members at all levels, fostering inclusivity and alignment.

2. Adaptability:

The cycle is not confined to a specific industry or project type. It’s a flexible framework that can be adapted to different contexts, whether it’s manufacturing, logistics, or healthcare. This adaptability makes it a universal tool for continuous improvement.

3. Continuous Improvement:

Unlike linear models, PDCA operates in a continuous loop. After the Act stage, the cycle repeats, allowing for ongoing refinement and optimization. This iterative nature ensures that improvements are sustained and built upon, leading to long-term growth and excellence.

4. Risk Mitigation:

By encouraging small-scale testing and careful analysis (Do and Check stages), PDCA helps in identifying and mitigating risks early in the process. This controlled approach minimizes the chances of large-scale failures and promotes a culture of thoughtful experimentation.

5. Enhanced Communication and Collaboration:

The clear structure of the PDCA cycle facilitates communication and collaboration within teams. Everyone knows the stage of the process and their role in it, leading to greater synergy and efficiency.

6. Problem-Solving and Innovation:

PDCA’s systematic approach encourages problem-solving and innovation. By continuously evaluating and adapting the plan, organizations can discover new solutions and approaches that may not have been apparent at the outset.

What are the four phases of the PDCA cycle?

The PDCA cycle has four key stages as can be seen in the graphic below.

Stage 1 – Plan – identify and define the problem, creating a plan for the change.

Stage 2 – Do – Test the potential solutions from the plan.

Stage 3 – Check – Study the results, analyze the results and understand what you have learnt.

Stage 4 – Act – Take action based on the outcome of the previous step. If the change worked implement what was learnt from the test into the full process. If the change does not produce the required results repeat the cycle with a different plan.

Within the planning stage, it is important to have a clear understanding of what the problem is you are trying to solve. Ensure those involved all have a clear and consistent understanding.

Once a consistent understanding has been established, you need to create a plan.

Within your plan is important to consider:

• What are the goals?
• How are we going to do it?
• What resources do we need?
• Who is responsible for taking action?
• When are the actions going to be done?

Start implementing the plan as set out in the previous stage. Ensure everyone knows their role and responsibility, consider creating an effective communication plan for all stakeholders as changes to the process are likely and you need to ensure those involved understand what is happening and why.

You might find that the plan needs to adjust during this step as you implement your plan, therefore it is advised to start small and then expand once you are confident in the plan.

Review the results of the trial from the previous stage, did this produce the expected results?

Ensure you review the results with the team involved as they will be able to provide insight and understanding of the results based on their involvement.

Ensure you have collected sufficient data so that the test is statistically significant and not just a one-time result with may not be repeated.

Once everything has been tested and reviewed if the results meet the expected outcome it is time to implement the solution full-time into the process. Ensure all stakeholders are fully aware of what the change is and what they need to do to sustain the change. Tools such as Standard Operating Procedures (SOPs) or other training aid are useful in this step. During this stage it is useful to continue to check the process for a period of time after to ensure all issues have been resolved and that the problem does not reappear elsewhere.

Once this improvement is closed out you can repeat the cycle with further improvements to continually make improvements to the process.

If the results from the test do not meet the expected outcome return to the plan stage and repeat the process with a different potential solution.

When to use the PDCA cycle?

When an organization is looking to improve its processes or when a specific problem needs to be addressed, the PDCA cycle is frequently used. In this answer, we will go over when and how to use the PDCA cycle for project improvement.

• When there is an issue or problem: The PDCA cycle is frequently used to solve problems or issues that an organisation may be experiencing. When a problem arises, the PDCA cycle can be used to identify the root cause of the problem, develop a solution, implement the solution, and then evaluate the results to determine if the problem has been solved. This can assist organisations in addressing issues quickly and effectively while minimising their impact on the business.
• When continuous improvement is required: When an organisation wants to continuously improve its processes or products, the PDCA cycle is used. Organizations can use the PDCA cycle to identify areas for improvement, develop and implement a plan to address those areas, and then evaluate the results to see if the changes have resulted in an improvement. This can assist organisations in remaining competitive and meeting their customers’ changing needs.
• When standardisation is required : The PDCA cycle can also be used to standardise processes within an organisation. Organizations can use the PDCA cycle to identify best practices, develop standard processes, implement those processes, and then evaluate the results to ensure that the processes are functioning as intended. This can assist organisations in increasing efficiency, reducing waste, and ensuring consistent quality.
• When innovation is required: The PDCA cycle can also be used to drive innovation within an organisation. Organizations can use the PDCA cycle to generate new ideas, test those ideas, evaluate the results, and then implement the best ideas. This can assist organisations in staying ahead of the competition and discovering new ways to meet their customers’ needs.

The PDCA methodology is usually best suited to situations where the improvement needs a small amount of resouces and is a less intense problem. Whereas if these are greater you may consider A3 , 8D , DMAIC or DFSS for your project.

In conclusion, the PDCA cycle is a useful methodology for improving processes, products, and services within an organisation. It can be used in a variety of situations, including when there is a problem or issue, when continuous improvement is required, when standardisation is required, and when innovation is required. Organizations can use the PDCA cycle to quickly identify areas for improvement, develop and implement plans to address those areas, and then evaluate the results to ensure that the desired outcomes are met.

To summarise, the PDCA cycle is a valuable methodology for organisational continuous improvement. It is a straightforward approach that can be applied to small or simple change projects and is also known as the Deming cycle or Shewhart cycle. The PDCA cycle’s four stages: Plan, Do, Check, and Act, provide a logical sequence of steps for problem-solving. It enables controlled trials of potential solutions with adequate analysis prior to full implementation.

PDCA is useful for keeping the project team on track, facilitating communication, and keeping stakeholders focused. It is ideal for simple improvement projects that do not require extensive analysis. It is a powerful tool for organisations seeking to improve their efficiency and achieve continuous improvement.

• Moen, R. and Norman, C., 2006. Evolution of the PDCA cycle .

Daniel Croft

Daniel Croft is a seasoned continuous improvement manager with a Black Belt in Lean Six Sigma. With over 10 years of real-world application experience across diverse sectors, Daniel has a passion for optimizing processes and fostering a culture of efficiency. He's not just a practitioner but also an avid learner, constantly seeking to expand his knowledge. Outside of his professional life, Daniel has a keen Investing, statistics and knowledge-sharing, which led him to create the website learnleansigma.com, a platform dedicated to Lean Six Sigma and process improvement insights.

Free Lean Six Sigma Templates

Improve your Lean Six Sigma projects with our free templates. They're designed to make implementation and management easier, helping you achieve better results.

5S Floor Marking Best Practices

In lean manufacturing, the 5S System is a foundational tool, involving the steps: Sort, Set…

How to Measure the ROI of Continuous Improvement Initiatives

When it comes to business, knowing the value you’re getting for your money is crucial,…

8D Problem-Solving: Common Mistakes to Avoid

In today’s competitive business landscape, effective problem-solving is the cornerstone of organizational success. The 8D…

The Evolution of 8D Problem-Solving: From Basics to Excellence

In a world where efficiency and effectiveness are more than just buzzwords, the need for…

8D: Tools and Techniques

Are you grappling with recurring problems in your organization and searching for a structured way…

How to Select the Right Lean Six Sigma Projects: A Comprehensive Guide

Going on a Lean Six Sigma journey is an invigorating experience filled with opportunities for…

A3 Problem Solving

– The A3 Report –

⇓   Introduction to A3

⇓   What is A3

⇓   Why Implement A3

⇓   How to Implement A3

⇓   A3 Services

Introduction to A3 Problem Solving

In order for any business to be successful, they must strive to improve quality and efficiency as well as build a problem solving continuous improvement culture. The A3 Report is a very useful problem solving and continuous improvement tool.  It was first used by Toyota and is quickly gaining popularity in industry today. Companies must start to view problems as opportunities for improvement. The A3 Report format allows the entire problem identification, clarification, analysis and resolution steps to be documented on one single sheet of paper.

What is A3 Problem Solving

The name “A3” is actually derived from a standard European paper size similar to 11” by 17”. The A3 Report is based upon the Plan, Do, Check, Act (PDCA) Method. The PDCA process is sometimes referred to as the Deming Wheel or Deming Circle. The A3 Report incorporates this basic premise to problem solving and continuous improvement.

Why Implement A3 Problem Solving

Some problem solving tools involve numerous pages of information, multiple charts and graphs and lengthy reports. The A3 Report format can be used to more effectively communicate all of the pertinent information with greater visual impact. While the A3 Report is an effective communication tool, it is actually much more valuable as a problem solving and critical thinking tool that can be used to drive continuous improvement. The A3 Report fosters a problem solving / continuous improvement mindset within the participating team members. It is an excellent tool for managers and supervisors to share problem solving techniques with their teams. With resources being limited, completion of a formal A3 Report may not be applicable to every problem. Its use should be determined based upon the size of the problem and its impact on the business or organization. The A3 Report and the A3 way of thinking are valuable tools for Lean initiatives and for integrating a problem solving culture throughout the organization.

How to Implement A3 Problem Solving

The A3 Report usually consists of multiple steps following a PDCA structure of Plan, Do, Check, Act. The number of steps can vary due to the different formats being used for the A3 Report. The exact number of steps used is not as important as the end result. The A3 Report can utilize various forms depending upon the organizations needs and preferences. The following paragraphs provide information regarding the basic steps and some tools used to complete the A3.  One thing that all of the forms seem to have in common is that they follow the PDCA problem solving process.  The basic steps and where they fall into the PDCA structure are listed below:

• Define the Problem:

The first step is to define the problem or identify the need for improvement:

• Define the ideal state, the operational standard or the desired condition
• Describe the current situation or status
• How is the current status different from the desired state or operational standard?
• What value will be realized by completion of the A3 exercise?
• Containment:

In some A3 formats, a section is included for immediate countermeasures or containment actions. The purpose of containment is to prevent further problems from occurring or prevent the current problem from causing negative effects to other processes, products or departments.

• Breakdown the Problem:

Next, the team should breakdown or further define the problem. Ask any relevant 5W (What, When, Where, Who, Why) and 2H (How, How many / How often) questions. There also may be more than one issue contributing to the problem or more detail required to properly address the problem. Prioritize the issues and identify the point of occurrence or escape point.

• Define goals:

The A3 team should set goals regarding the improvement desired as a result of the exercise. This could include a percentage of improvement in process throughput, reduction in number of defects per unit or processing time. The goals should be specific, measureable, realistic, achievable and timely. Many companies are adopting the SMART goal approach.

• Root Cause Analysis:

The team should perform a Root Cause Analysis (RCA) of the problem by using various quality tools. The tools could include, but are not limited to data analysis or completing a Cause and Effect or Ishikawa diagram followed by a 5 Why exercise. Whatever method selected, it is important to get past the symptoms of the problem and down to the root cause.

• Countermeasures:

Permanent countermeasures or corrective actions must then be determined to address the root cause. The countermeasures must be clearly defined, achievable by the person responsible and have a due date. Corrective actions that do not have an owner or due date are seldom achieved.

• Implementation:

A plan for implementation of the corrective actions should be developed. The plan should include the team members, resources and time required to complete each task. In some cases, support from outside resources or test facilities are required. Some countermeasures may require repair or replacement of tooling or other capital expenditures. Therefore, proper levels of management should be kept informed throughout the process to assure adequate resources are available for implementing any corrective actions.

• Monitoring and Validation:

The A3 team should next confirm the effectiveness of the countermeasures. This can be accomplished in many ways, including but not limited to additional quality checks, Statistical Process Control (SPC) data, process or product audits and customer feedback.

• Standardize and Improve:

During this phase of the A3, the team should take action to standardize the process changes or improvements. The team must update all standard work, work instructions and process control plans, etc. In addition, it is a good practice to perform a short Things Gone Right / Things Gone Wrong (TGR/TGW) exercise and document in the A3 report what went well during the process and what could use improvement. The management team should also promote continuous improvement of the A3 tool within the organization.

Common problems to avoid with the A3 Report:

• The background is not well developed
• The problem statement is not well defined or unclear
• The ideal state or target condition is actually an action item, not the desired result
• Analysis does not drill down to the root cause(s)
• Ineffective countermeasures that will not prevent the problem from re-occurring
• Validation and monitoring methods are not well documented or there is a lack of evidence of improvement

Always remember that the A3 process and report are about fostering critical thinking. Encourage A3 thinking within your organization. The A3 process should be focused on improvement through developing the skills of the people. A3 thinking promotes problem solving, communication and mentoring of the teams.

The A3 Report is an effective visual tool for driving improvement and promoting a problem solving way of thinking. The format can and does vary depending upon the company or organization. The format you select is not as important as the results of the exercise. As long as the form contains the basic steps for problem identification, root cause analysis, corrective action and monitoring improvement or performance, it will be a very effective tool. The A3 Report has its roots in the automotive industry but is branching out into many different applications and industries from manufacturing to healthcare.

A3 Problem Solving Services

A3 Services from Quality-One include A3 Problem Solving Consulting, A3 Problem Solving Training and A3 Problem Solving Project Support, such as Facilitation and Auditing. Our experienced team of highly trained professionals will provide a customized approach for developing your people and processes based on your unique needs. Whether you need Consulting to assist in the design of your A3 process, Training to help understand and drive improvement through the A3 report, or hands-on Project Support for building and implementing your A3 process by utilizing our experienced Subject Matter Experts (SME) to work with your teams, Quality-One can help you promote A3 thinking in your organization.

Learn More About A3 Problem Solving

Quality-One offers Quality and Reliability Support for Product and Process Development through Consulting, Training and Project Support. Quality-One provides Knowledge, Guidance and Direction in Quality and Reliability activities, tailored to your unique wants, needs and desires. Let us help you Discover the Value of A3 Consulting, A3 Training or A3 Project Support.

Contact Us | Discover the Value!

(248) 280-4800 | [email protected]

Remember Me

• Don't have an account? Register
• Lost your password? Click here
• Already have an account? Log in

• Search Search Please fill out this field.

What Is the PDCA Cycle?

How the pdca cycle works, the pdca cycle and kaizen, benefits of the pdca cycle, examples of the pdca cycle, the bottom line.

• Business Essentials

What Does PDCA Stand For in Business? Plan-Do-Check-Act Cycle

The Plan-Do-Check-Act (PDCA) Cycle is a four-step problem-solving iterative technique used to improve business processes. Originally developed by American physicist Walter A. Shewhart during the 1920s, the cycle draws its inspiration from the continuous evaluation of management practices and management’s willingness to adopt and disregard unsupported ideas.

The method was popularized by quality control pioneer Dr. W. Edwards Deming in the 1950s who coined the term “Shewhart” Cycle after his mentor. It was Deming who realized the PDCA Cycle could be used to improve production processes in the United States during World War II.

Key Takeaways

• The PDCA Cycle is a four-step technique that is used to solve business problems.
• Many managers unknowingly use the PDCA Cycle as it encompasses much of the same framework as strategic management.
• The last step of the PDCA Cycle (act) calls for corrective actions to stimulate and sustain continuous business improvement.
• The PDCA process is similar to the Japanese business philosophy of Kaizen.
• Many large corporations, such as Toyota and Nike, have seen dramatic growth after implementing PDCA or Six Sigma methodologies.

The PDCA Cycle can help differentiate a company from its competitors, particularly in today’s corporate world, where businesses are always searching for ways to streamline their processes, reduce costs, increase profits, and improve customer satisfaction.

Many managers apply the PDCA Cycle unknowingly to help direct their organizations as it encompasses the basic tenets of strategic planning. The four components of the PDCA Cycle are outlined below.

A well-defined project plan provides a framework for operations. Importantly, it should reflect the organization’s mission and values. It should also map the project's goals and clearly indicate the best way to attain them.

This is the step where the plan is set in motion. The plan was made for a reason, so it is important for players to execute it as outlined. This stage can be broken down into three sub-segments, including training of all personnel involved in the project, the actual process of doing the work, and recording insights, or data, for future evaluation.

Typically, there should be two checks throughout the project. First, checks alongside implementation ensure the project's objectives are being met. Second, a more comprehensive review of the project carried out upon completion addresses the successes and failures so that future adjustments can be made.

The final step is to take corrective action once past mistakes have been identified and resolved. The PDCA Cycle is repeated and can be redefined perhaps to better results under new guidelines.

Given its cyclical nature, the PDCA Cycle is something businesses can institute once and then use to continuously iterate and improve their operations.

The PDCA process is similar to the Japanese business philosophy of Kaizen , which, when translated, means "change for the better" or "continuous improvement." Kaizen is where all employees are involved in improving productivity by finding efficiencies in the work environment. Like the PDCA cycle, Kaizen aims for continuous improvement through small, incremental changes.

Examples of changes that might be made through Kaizen or PDCA are using new systems, eliminating waste, or implementing just-in-time delivery. Not all changes need to be small or incremental.

The concept behind PDCA and Kaizen is that the culture of an organization changes as the employees learn to be problem solvers and critical thinkers. The PDCA cycle tests employees' ideas, adjusts them, and then implements them if they have potential. The cycle is an iterative process that continually tests concepts and promotes improvements.

Companies looking to enhance their internal and external processes often deploy the PDCA methodology to minimize errors and maximize outcomes. Once established, companies can repeat the PDCA Cycle and make it a standard operating procedure. The final stage of the methodology, "Act," takes corrective actions and makes the methodology ideal for continuous improvement efforts.

Lean methods like PDCA and Kaizen helped Nike to double its profits from around $100 billion in 2015 to over $200 billion in 2021.

The Mayo Clinic

The Mayo Clinic, a nonprofit, world-class hospital and research center, conducted a quality improvement study that looked at wait times for patients who were possible candidates for large cochlear implant surgery. The idea was to employ Kaizen principles to remove barriers and improve access for patients.

The study looked at the refining of specific treatments, the management of patient records, and waiting room times. Ultimately, there were positive outcomes for patients.  Among the results, median cycle time for candidacy testing decreased from 7.3 to 3 hours, and total inventory of clinic stock was reduced by 31%.

Is PDCA the Same As Total Quality Management (TQM)?

Total quality management (TQM), which is the precursor to Six Sigma , includes the philosophy of PDCA, but it goes one step further.

According to Smartsheet, which quotes Marlon Walters, the Founder and CEO of Horizon Group Consulting, "With TQM, you have to wait for your customers to confirm that it’s good. With Six Sigma, at the end of the day, you don’t guess if your product is better. You know it. If you properly identify your market and your product has the best fit for the niche, you know you have the best product from a process perspective."

Kaizen, or PDCA, is more of a philosophy for how to organize the larger workplace and how to engage coworkers. It is less about waiting for customer feedback or results. Both PDCA and TQM consider the whole company responsible for continuous improvement.

What Is the Difference Between PDCA and Six Sigma?

The difference between PDCA and Six Sigma is that Six Sigma is an all-encompassing management principle that includes PDCA as part of its structure. PDCA explains how to enact Six Sigma, it is the plan, do, act, check process. Six Sigma calls this the DMAIC method (define, measure, analyze, improve, and control).

According to Walters, PDCA is people-oriented while Six Sigma is process-based. For example, the term "define" in Six Sigma removes the human element, and the term "measure" puts the focus on data.

What Is the Difference Between PDCA and PDSA?

PDCA stans for plan, do, check, act, whereas PDSA stands for plan, do, study, act. They are both iterative, four-stage problem-solving models used to improve a process. The main difference between the two is that PDCA, which was developed before the PDSA model, has the "check" stage. In this stage, the team determines whether what they intended to achieve has actually occurred by checking expected results with the actual results. So, PDCA has a built-in check for every cycle in the process.

The PDCA Cycle, PDSA, Kaizen, and Six Sigma are all proven ways to continuously improve processes. Many companies including Nike, Toyota, the Mayo Clinic, and many others have seen dramatic growth after employing one or more of these iterative strategies. The concept changes the culture of a business so that all stakeholders have input and can act as problem solvers and critical thinkers. The result is more ideas for change.

PubMed.gov. " Application of Kaizen Principles to a Large Cochlear Implant Practice: A Continuous Quality Improvement Initiative at Mayo Clinic. " Accessed June 3, 2021.

FXSSI. " TOP 10 Most Profitable Companies in the World in 2021. " Accessed June 3, 2021.

Macrotrends. " NIKE Market Cap 2006-2021 | NKE ." Accessed June 3, 2021.

Smartsheet. " A Quality Principle: Everything You Need to Know about Total Quality Management ." Accessed June 3, 2021.

• Terms of Service
• Editorial Policy
• Privacy Policy
• Your Privacy Choices

PDCA Diagram for Problem Solving

PDCA is a common way to implement a project or any other work. That is, before you can do anything, you must have a thorough plan ( plan ) under which to perform, check that the task has been completed as planned ( check ), and take corrective or improvement action if necessary ( action ). Then move on to the next cycle of PDCA, continuous improvement iteratively and incrementally.

The PDCA model can be briefly described as follows:

P lan (Planning): According to customer requirements and organizational policy, establish the necessary goals and processes for providing results.

D o (implementation): implementation process.

C heck (Inspection): Monitor and measure the process and products according to the policies, objectives and product requirements, and report the results.

A ct (Disposal): Take measures to continuously improve process performance.

Guideline of the Deming Cycle (or known as Deming Wheel)

Deming's theory reflects the comprehensiveness of quality management, showing that quality management and improvement are not the matter of individual departments, but need the leadership and promotion of top managers to be effective.

The core of Deming's theory can be summarized as 7 guidelines as follows:

The determination and participation of senior management;

Team spirit of teamwork;

Improve quality awareness through education;

Technical training for quality improvement;

Develop standards for measuring quality;

Understanding of the analysis table of quality cost; continuous improvement campaign;

The participation of employees at all levels.

Explore more PDCA Model templates

Create beautiful designs on-the-fly

No credit card required. No contracts to cancel. No downloads. No hidden costs.

©2024 by Visual Paradigm. All rights reserved.

• Terms of Service
• Privacy Policy
• Security Overview