Operational risk prevention works only when the response is built into the work. This article separates prevention, troubleshooting and problem solving, then shows how visible triggers, decision authority and learning make risk-based thinking practical.
A procedure is written in an office by somebody who is not hands-on. It is then approved in a meeting and placed in a shared folder. The real test arrives later, at 10:17, when a machine sounds weird and different, some relevant information is missing, or material does not look right. The person closest to the problem has to decide whether to continue, improvise, wait or stop. That decision is the prevention system.
If that person cannot see what normal looks like, recognise the trigger, take a safe first step or reach somebody with the authority to decide, the organisation is not preventing the problem. It is simply hoping that experience will somehow cover the gap.
A document is not yet a control
Some companies respond to a failure by writing a longer procedure. It is sent to that same shared folder and mentioned in the next training session where not everybody is even present. The operator still does not have the instruction at the workstation, and the supervisor still does not know what to check. Three weeks later, the same failure returns with a new report number.
A control changes what happens when a relevant condition appears. It must be visible where the decision is made, understandable to the person making it and connected to a response that somebody can actually authorise. Length of the procedure is not evidence of control. Sometimes a useful instruction is one page and sometimes it is simply a clear signal and a stop rule.
Keep three different jobs separate
Prevention keeps a known problem from occurring. Troubleshooting restores today’s work when the problem appears. Problem solving removes the cause so that the same problem is less likely to return.
These jobs support each other, but they are not interchangeable. Five orders delayed by a material shortage may need an immediate workaround first, a visible availability check of materials at hand and a call to the supplier to see what’s going on there. That restores the orders and may prevent the next shortage. It does not explain why the planning rule, reorder point or customer promise allowed the shortage to become likely. Calling that first response permanent problem solving is exactly how the sixth order becomes late as well.
Put the control at the point of choice
The person doing the work needs four things without having to search for them: the normal condition, the signal that something has changed from normal, the first safe response in such a case, and the point at which work must stop or move to somebody else.
“Tell your supervisor if concerned” is not a useful rule when the supervisor is in another building and the truck leaves in twenty minutes. Name the trigger, the response and the authority. If the response needs a decision from Purchasing, Quality or Management, the route must be prepared before the pressure situation arrives.
The person who sees the problem first may be a junior employee, a contractor or a cleaner. That does not weaken the evidence. It may be the reason the evidence has appeared early enough to matter. A system that listens only to people with the official title of expert will discover some risks and especially problems too late.
Do not confuse prevention with avoiding bad news
Prevention is not a synonym for stopping every change. The same observation can reveal a threat or an opportunity. A recurring hand injury may expose an unsafe grip. The same work may also reveal a safer and faster way to handle the material. Neither conclusion becomes useful because somebody entered it in a register somewhere. Both need evidence, an owner, a proportionate response and a check that the result of correction holds.
This is why risk-based thinking belongs in ordinary work. Conditions are uncertain. The outcome may be worse than expected, better than expected or simply different. The organisation needs to be ready to respond without waiting for a monthly meeting to tell it that the situation has changed.
Make escalation travel with the process
Keep action at the lowest level that has the skill and authority to handle it. Move it upward or across when the local team cannot change the system around the work. A supplier decision, a planning rule, a staffing constraint or a customer promise may sit outside the operator’s control. That does not make it somebody else’s problem, but it makes defined escalation route mandatory and part of the process.
This is the ground floor of a working Management Operating System. The standard and goals move down. Evidence of results moves up. Decisions, help and learning move across. PDCA is not a poster on the wall; it is the route by which a local signal becomes a decision, a changed standard and a checked result.
What ISO 9001 looks like at the workstation
ISO 9001’s risk-based thinking becomes useful at this point. The organisation identifies conditions that could affect the intended result, decides how to respond, who has the authority to decide on corrections, provides the competence and resources needed, and checks whether the response works. Let’s not forget sharing the learnings so that everybody else know what happened and how it was resolved. That logic does not live in a risk register alone. It lives in the choices people can make during real work.
If the management system contains a polished manual but the person doing the work cannot see the standard, recognise the trigger or stop the job safely, the system is watching the wrong end of the business.
Prevention starts beside the work. Put the knowledge, trigger, authority and learning route where the condition appears. Then the organisation has a chance to deal with the problem before it becomes a customer complaint, a repeated failure or a monthly surprise.
Best way to contact me and learn more about how I work is either here in LinkedIn or at www.baleteworks.com, and book the initial discussion. No strings attached.