A working PDCA system has goals, evidence and support moving through the organisation in different directions.
If PDCA is a circle on your slide, where does the decision happen when the number turns red at 09:00?
That question exposes the weakness in many management systems. Plan, Do, Check and Act are shown as a loop, but the work does not happen in a circle. It happens through levels, functions and shifts. The loop only works when the right information reaches the person who can decide what happens next.
A dashboard is not a management system
Senior management sets a target. A dashboard collects measures. The night shift receives a sentence about supporting a corporate objective. When performance slips, everyone waits for the next meeting.
That is not PDCA. It is information travelling without a decision. The people doing the work may have reported the problem for weeks. Management may honestly say it has not seen the evidence. The message stopped between them.
One objective, three decisions
Take 95% on-time delivery. The objective can be shared. The decisions cannot.
At 09:00, the shift supervisor needs to know which orders are at risk today, why, and what can be changed before the truck leaves. On Friday, the operations manager may need to change a planning rule that created four late orders. At month-end, senior management may need to decide whether a customer promise, supplier arrangement or capacity choice is damaging the whole business.
Each level needs evidence that supports its decision. A smaller version of the senior dashboard is not automatically useful at the point of work. If the same red number appears at all three levels with no different action attached, the dashboard is just decorating the problem.
Three directions, not one
A working PDCA system has three movements.
Goals, limits and priorities move down. People need to know what result matters, what boundary cannot be crossed and which decisions they are expected to make.
Evidence, exceptions and requests move up. The signal must reach someone with the authority and resources to remove a barrier or change the rule. Then there is learning loop which tends to be forgotten entirely.
Help and learning should move across. A useful fix found in Planning must reach Operations. A better check found on one site must not remain local by accident and the reason for one department success must be shared. Training must match the method supervisors actually use.
The organisation chart does not create these routes. Someone has to design them.
The handoff is where the loop dies
A delivery problem rarely belongs to one department. Sales makes the promise, Planning sequences the work, Purchasing waits for supply, Operations executes it and Finance sees the margin. Passing the issue upward without connecting those people turns a senior manager into a courier between tables.
Set a practical rule: when a problem or opportunity affects another function, the owner sends the evidence to a named counterpart, agrees the next decision and records it. Copying a senior manager is not the same as connecting the work.
The route also needs psychological safety. If a temporary worker sees a gap, the contract type does not make the gap imaginary. If a manager dismisses the message because of who delivered it, the loop has been broken by choice.
Keep action close; escalate deliberately
Action should stay at the lowest competent level. Escalate when the decision crosses a function, exceeds a local limit or needs authority and resources that are not available there. Escalation is not failure. Unclear escalation is.
This is where risk-based thinking joins PDCA. Risk-based thinking asks what conditions could move the result and what management should prepare. PDCA asks what the evidence now says and what should change. One looks ahead; the other learns from the last move. A capable management system does both.
The ISO connection is practical
ISO 9001 is often reduced to procedures and audits. Its process approach, responsibilities, objectives, monitoring and risk-based thinking point to a more demanding question: can the organisation see a deviation, decide what it means and act before the consequence becomes normal?
Changing a procedure title will not repair a broken route. Draw the three flows for one objective: what moves down, what moves up and what must move across. Then test them against a real warning from the shift. If the warning cannot reach every level and function that needs it, the diagram has found real work to do.