A technician makes a mistake that causes downtime, damage, rework, a quality event, or significant operational consequence.
Stabilize first
Protect people, equipment, product, and the process before beginning the accountability conversation. Do not conduct the investigation in the middle of uncontrolled consequences.
Once the condition is stable, preserve the facts while they are still fresh.
Understand what the person knew
Ask what information they had, what they believed was happening, what instruction they received, and what conditions influenced the decision. Listen before telling them what the organization thinks occurred.
The difference between a reasonable error and negligent disregard often lives in these details.
Examine the system too
Was the work order clear? Was the procedure current? Was training adequate? Did time pressure normalize a shortcut? Was the safeguard weak? Had the same risk been visible before?
An individual error and a system weakness can both be true.
Choose the response based on the failure type
Skill gaps need development. Knowledge gaps need clarity. System failures need correction. Ordinary errors need learning. Negligence and deliberate choices may require formal accountability.
Using the same response for all five is not strong leadership. It is poor diagnosis.
Useful language
What good looks like
The incident produces a more accurate understanding, the system becomes harder to fail in the same way, and individual accountability remains proportionate to the actual behavior.