PDCA Cycle Explained with Real Workplace Examples

The PDCA cycle (Plan-Do-Check-Act) is a four-step method for improving a process: plan a change based on evidence, try it on a small scale, check the results against what you expected, then act by adopting, adjusting or abandoning the change. You repeat the cycle until the problem is solved, then start again on the next one.

PDCA sits behind most quality standards used in labs, food businesses and pharma. If you can run a disciplined PDCA cycle, you can lead improvement projects, close audit findings properly and show auditors that your system really improves.

Where PDCA comes from

Walter Shewhart described a cycle of specification, production and inspection in the 1930s. W. Edwards Deming built on it and taught it widely in Japan from 1950, where it became known as the Deming cycle. Deming later preferred the name Plan-Do-Study-Act (PDSA), to stress studying and learning from results rather than simply checking.

PDCA is now built into many ISO management system standards:

• ISO 9001:2015 maps clauses 6 to 10 onto PDCA, with leadership at the centre.
• ISO 22000:2018 uses two linked PDCA cycles: one for the management system and one for operational planning and control, including the hazard control plan.
• ISO 14001 and ISO 45001 share the same harmonised structure and PDCA logic.

The four steps in practice

Plan

Define the problem with data, not opinion. Set a measurable aim, map the current process, analyse causes (for example with a fishbone diagram or 5 Whys) and choose a change you predict will help. Decide in advance what you will measure and what result would count as success.

Do

Implement the change on a small scale first: one shift, one line, one ward or one week. Train the people involved, run the change as planned and record what happens, including problems and surprises.

Check

Compare the results with the baseline and your prediction. Did the measure improve? Were there side effects? Use simple tools such as run charts rather than relying on one good day.

Act

If the change worked, standardise it: update the SOP, train everyone and monitor to hold the gain. If it partly worked, adjust and run another cycle. If it failed, record what you learned and try a different change.

Why the small-scale test matters

Testing small limits the cost of a wrong idea and gives you real data quickly. A change that looks obvious in a meeting often fails at 3 a.m. on a night shift, or causes a problem in another department. Small tests reveal this before you rewrite procedures for the whole organisation.

Three short workplace examples

For the lab example, see also Turnaround time (TAT) in clinical labs.

Worked example: reducing emergency TAT in a Kochi hospital lab

A 400-bed hospital in Kochi received repeated complaints from the emergency department about slow potassium and troponin results. The laboratory's quality manager led a PDCA project with the section supervisor, a phlebotomy lead and an emergency department nurse.

Plan. The team pulled four weeks of laboratory information system data and measured TAT from sample receipt to result authorisation. The median was within the lab's internal target, but a long tail of samples took far longer, mostly on the evening shift. A process walk showed emergency samples waiting in the general reception queue and then for a full centrifuge batch. The team set an aim to bring a defined percentage of emergency samples within target, and predicted that a separate emergency pathway would help.

Do. For two weeks on the evening shift only, emergency samples went into a red tray at reception, and one centrifuge was kept free for them. Staff logged any sample that missed target and the reason.

Check. A run chart showed fewer delayed samples on the evening shift, while the other shifts stayed unchanged. The log revealed a new issue: some samples were not labelled as emergency by the ward, so they still went into the general queue.

Act. The lab adopted the red-tray process on all shifts, updated its SOP and trained reception staff. A second PDCA cycle tackled labelling, working with the emergency department to use a priority flag on the electronic request. TAT became a standing item at the monthly quality meeting and in management review, supporting the laboratory's ISO 15189:2022 requirements for monitoring and improvement.

PDCA vs DMAIC vs 8D

The methods overlap rather than compete. Many organisations use PDCA as the everyday habit, DMAIC for larger projects and 8D for customer complaints. Read more in Lean Six Sigma basics and 8D problem solving.

Common mistakes

• Skipping Plan. Jumping to solutions without baseline data means you cannot show improvement.
• No prediction. Without saying what you expect, Check becomes a matter of opinion.
• Testing everywhere at once. Full roll-out on day one hides what worked and multiplies the damage of a bad idea.
• Stopping after Do. Many projects implement a change and never check whether it worked.
• Not standardising. If Act does not update the SOP and training, the gain fades.
• One cycle only. PDCA is a loop; most real problems need several turns.

Key takeaway: PDCA works when each step is done honestly: plan with data, test small, check against a prediction and act by standardising what works. Repeat the cycle until the gain is secure.

Frequently Asked Questions

What is the PDCA cycle with an example?

PDCA stands for Plan, Do, Check, Act. For example, a hotel kitchen measures buffet waste (Plan), tries smaller batch cooking for three dishes for two weeks (Do), compares waste weights with the baseline (Check), then extends the method to all hot dishes and updates par levels (Act). The cycle repeats to find further improvements.

What is the difference between PDCA and PDSA?

PDSA replaces Check with Study. W. Edwards Deming preferred PDSA because he felt check suggested simply inspecting results, while study emphasises learning from them and comparing them with predictions. In practice, many organisations use the terms interchangeably, and ISO standards use PDCA. What matters is that the third step involves real analysis.

How does ISO 9001 use the PDCA cycle?

ISO 9001:2015 describes PDCA in its introduction and maps it onto the clauses: Plan is clause 6, supported by context and leadership, Do is clauses 7 and 8, Check is clause 9 and Act is clause 10. Leadership in clause 5 sits at the centre. The cycle applies to individual processes and to the QMS as a whole.

Is PDCA the same as continual improvement?

PDCA is a method for achieving continual improvement, not the same thing. Continual improvement is the ongoing activity of enhancing performance, required by standards such as ISO 9001 in clause 10.3. PDCA provides a repeatable structure for each improvement, alongside other tools such as corrective action, DMAIC and Kaizen events.

Next steps

To build your problem-solving toolkit, Root Cause Analysis and CAPA covers the analysis and corrective action skills behind every good Plan and Act. For a system-wide view, ISO 9001 Essentials: Quality Management Systems and Practical Implementation shows how PDCA runs through a QMS. Both are offered online to learners in India and the GCC.

Read next: 8D problem solving: steps, template and example, Quality KPIs that actually drive improvement and Root cause analysis: 5 Whys vs fishbone. Want guidance on a learning path? Speak to a counsellor.