Abstract background

The 5 biggest pitfalls of the PDCA cycle

PDCA is a powerful method for continuous improvement, but it demands precision. The five biggest pitfalls: Plan-Do-Plan-Do, no room to experiment, no intention to improve, a plan imposed from above and PDCA without KPIs and data analysis.

Key takeaways

  • Complete the learning cycle, as quickly and as often as possible. Applying PDCA once a year ignores its power.
  • Trying things out is the essence of the Do and Check steps and determines ownership of solutions.
  • PDCA only comes into its own with a specific intention to improve the process, not as an aid in running it.
  • A detailed plan from above based on wrong assumptions forces the shop floor to use tricks.
  • Without real KPIs and data analysis, continuous improvement rests on quicksand.

A misstep is quickly made

Many organizations pay more and more attention to continuous improvement and PDCA cycles. That is not surprising, because with this very powerful improvement method you achieve much better performance. PDCA is also present at the heart of every intelligent company.

If you want to succeed with PDCA you have to be alert, because precision matters. Without inspiring, mobilizing, appreciating and reflecting, for example, it does not work at all. If you do not pay attention, your organization or team eventually ends up in a vicious circle. So beware of the five biggest PDCA pitfalls.

The five PDCA pitfalls at a glance

What goes wrong and what the remedy is.

What goes wrong

Remedy

1. Plan-Do-Plan-Do

Check and Act are skipped

Complete the cycle, often

2. No experiments

PDCA as a control tool

Allow trying things out

3. No intention

Only repairing the process

Aim explicitly at improvement

4. Plan from above

Wrong assumptions, tricks

Analyze first, involve the shop floor

5. No KPIs

Check meeting without facts

Real KPIs and data analysis

Pitfall 1: Plan-Do-Plan-Do keeps repeating itself

The pattern of Plan-Do-Plan-Do keeps repeating itself. You never get round to Check and Act, and there is always a new plan you can pull out of the cupboard. The mistake is that you do not apply PDCA consistently. If you want to achieve the desired improvement, you have to complete the learning cycle, as quickly and as often as possible. You ignore the power of PDCA if you apply it only once a year.

Pitfall 2: PDCA without being allowed to experiment

This pitfall is familiar territory for managers with an excessive urge to control. They see PDCA mainly as a tool to plan and check the work. You are then saddled with an approach that hinders instead of solving real problems. These managers do not allow experiments, because they are seen as risky. But trying things out is precisely the essence of the Do and Check steps. Moreover, experimenting determines the ownership of solutions for daily bottlenecks, and that ownership is crucial to move forward together.

Pitfall 3: PDCA without a specific intention to improve

Organizations still often apply PDCA purely as an aid in carrying out the ordinary process. They look, for example, for what is “missing” in a process and then add it correctively, so that the process again does what it was designed for. All very useful, but it does not contribute to the continuous improvement of processes. PDCA only comes into its own with a specific intention to improve your process. Note, however, that continuous improvement is a standard part of your job.

Pitfall 4: applying PDCA to a plan from above

This pitfall starts with a plan from above without much analysis or “wisdom”, but worked out down to the last detail. Senior management will then do everything to carry out this plan, even if it gradually becomes clear that it rests on wrong assumptions. This too misses the essence of PDCA. The shop floor is caught in a split: people have to use all kinds of tricks to realize the plan (optically), while in practice they try to keep doing what is useful. That is tiring and annoying, and of course bad for your results.

Pitfall 5: PDCA without KPIs and data analysis

Perhaps the most important pitfall: trying to get PDCA going without real KPIs. You will notice that your continuous improvement process rests on quicksand. Without KPIs you cannot plan well and cannot set norms and targets, and you lack the data to monitor and analyze execution. The check meeting is ultimately about nothing, because you do not know whether you are right or wrong. You get stuck in generalities.

If you want PDCA to work as a precision instrument, you have to think carefully about your KPIs and analyze the underlying data. They string the steps together, and only then do you have a strong story.

How Diamond Decisions makes PDCA data-driven

PDCA is a cycle of decisions: what do we plan, what do we conclude at Check, what do we change at Act? In business modeling we link each of those decisions to a KPI, data analytics supplies the facts for the check meeting, and the decision makers learn to complete the cycle weekly instead of yearly.

Talk to the author

Leo KerklaanLeo Kerklaan
Diamond Decisions

Discuss your question with Leo

Tell us where decisions in your teams get stuck today. In a no-obligation conversation we explore how everyone can make better decisions with data every day.

Schedule an introduction →

Step 4 of our approach

Decision Makers

From data to better decisions every day, in every team.

Explore Decision Makers →

Frequently asked questions

01

What are the biggest pitfalls of PDCA?

Five stand out: never getting to Check and Act, not being allowed to experiment, using PDCA without a specific intention to improve, applying it to a detailed plan imposed from above, and working without real KPIs and data analysis.

02

How often should you go through the PDCA cycle?

As quickly and as often as possible. A cycle that is completed weekly or even daily yields far more learning moments than an annual planning and control cycle. Once a year ignores the power of PDCA.

03

What is the difference between PDCA as a control tool and PDCA as an improvement method?

As a control tool PDCA is used to plan and check the work and to repair deviations. As an improvement method it starts from an explicit intention to make the process better and leaves room for experiments, so that employees own the solutions.

04

How does a small team start with PDCA?

Choose one process and one KPI, agree on a small experiment, look at the figures together after a week and decide what you keep. A small team needs no programme for this, only a fixed moment in the week.

Further reading

About the author

Leo Kerklaan

Leo Kerklaan

Leo is a strategy professional who advises, teaches and writes about strategic performance management, in business and government, in the Netherlands and abroad. He is the author of several management books, including the bestseller De cockpit van de organisatie.

About Diamond Decisions

Diamond Decisions helps organizations become better by enabling better decisions. We don’t start with data, dashboards or AI, but with the decision that needs to improve, and work back from there to KPIs, data and technology. We do that in four steps: inspiration and alignment, business modeling, analytics and data platform and data-driven decision makers. That way BI and AI don’t remain an IT project, but deliver value every day.

Schrijf je in voor de Masterclass