The PDCA cycle is four steps. Most Malaysian manufacturing SMEs complete one and a half of them. Here is why — and what a full PDCA cycle actually looks like in practice.
Deming's PDCA cycle — Plan, Do, Check, Act — is the most widely taught problem-solving framework in Malaysian manufacturing. It appears in HRDC training programmes, ISO procedure manuals, and KPI reports across the country. It is also the most consistently incomplete improvement methodology in practice.
The observable reality in most Malaysian manufacturing SMEs: teams plan extensively, do incompletely, skip check entirely, and rarely act in the sense of standardising and propagating what worked. The cycle completes about 30% of its rotation and then stops.
Why Plan Phase Takes All the Time
Planning feels productive. Meetings are held. Root cause analyses are drawn. Fishbone diagrams are completed. Action plans are written. Presentations are made to management. All of this activity creates the impression of progress without requiring any change to the actual process.
The planning phase has no natural endpoint in many organisations — it can always be more thorough, more complete, more validated. This is compounded by organisational risk aversion: implementing a countermeasure requires committing to a course of action that might not work, and that failure is visible. Planning does not carry that exposure.
Why Do Phase Is Incomplete
Implementation is partial because the countermeasures designed in the Plan phase often turn out to be more difficult to implement than anticipated. Equipment constraints, budget limitations, or scheduling conflicts mean that only some of the planned actions get executed. The team moves to "check" before the implementation is complete — and then wonders why the results are not as expected.
The discipline of the Do phase requires completing the implementation as designed before measuring results. Measuring a partial implementation produces data that cannot be meaningfully interpreted — you do not know whether the incomplete actions are why the results are insufficient.
Why Check Never Happens
The Check phase requires collecting data and comparing it objectively against the target established in the Plan phase. This comparison will produce one of two findings: either the countermeasure worked, or it did not work as expected. Both are valuable findings. The second is unwelcome.
Organisations that have not normalised "this did not work as expected" as a legitimate outcome of the Check phase — where it is treated as learning rather than failure — will unconsciously avoid rigorous checking. The result is that countermeasures that are partially effective are declared successes, and the root cause remains partially unaddressed.
Why Act Never Standardises
When a countermeasure does work, the Act phase should result in the successful method being standardised and applied wherever the same root cause exists elsewhere in the factory. This is the compounding mechanism of PDCA — not just fixing one problem, but building organisational capability by capturing what works and replicating it.
In practice, standardisation is skipped because it requires updating procedures, retraining operators, and communicating across departments — all of which take more effort than the team has available after the immediate problem is resolved. The improvement is real but localised. The same problem recurs on a different line six months later, and the cycle starts again from scratch.