When an employee fails to follow a written procedure, the initial response from leadership is often straightforward: remind the employee of the requirement, retrain them, or reprimand them.

Sometimes that response is appropriate. Employees are responsible for following reasonable requirements, especially when safety, quality, or regulatory compliance is involved.

But beginning with discipline assumes the employee is the source of the failure. Before reaching that conclusion, leaders should ask a more important question:

Did the employee fail the procedure, or did the procedure fail the employee?

In many organizations, employees do not deviate from procedures because they are careless or unwilling to comply. They deviate because the written procedure does not reflect how the work actually gets done, or how it needs to get done when conditions are not ideal.

A procedure may describe the expectation without creating a workable process

A procedure can have a perfectly reasonable intent and still fail in practice.

Written procedures are often developed around the normal sequence of events. They explain what should happen when the necessary information is available, the equipment works, the weather cooperates, and every previous step was completed correctly.

Front-line employees operate in a different environment. They also encounter unexpected questions, irregular conditions, mistakes, competing priorities, incomplete information, and situations the procedure’s author did not anticipate.

When the document does not account for those realities, employees are left to bridge the gap. They create workarounds, rely on experience, or ask the person who already knows how to handle the exception. The required outcome may still be achieved, but it is no longer being achieved through a consistent and controlled process.

That should not automatically be treated as an employee problem. It may be evidence that the organization has not provided employees with a process that works under actual operating conditions.

Sometimes the work is being done—but the system cannot prove it

I encountered this problem while reviewing an organization that required incoming inspections on every part it received.

The requirement was clearly stated in the organization’s manual. However, I could not find records showing that the inspections had been completed. Based on the documentation, it appeared that employees were not complying with the requirement.

Further review revealed a different problem.

Employees were performing the inspections. The manual told them that incoming inspections were required, but it did not establish how those inspections should be documented. There was no defined record, form, system entry, or other process for demonstrating that the requirement had been completed.

The employees were performing the work, but the organization had not created the system needed to make that work visible and verifiable.

This distinction matters. Retraining or reprimanding the employees would not have corrected the underlying issue. The real corrective action was to develop a practical documentation process that connected the manual requirement to the work being performed.

A requirement by itself is not always a complete process.

Begin by asking where the system failed

When leaders discover apparent procedural noncompliance, their first question should not be, “Why didn’t they follow the procedure?”

A better starting question is, “Where might our system have failed them?”

That review should consider several possibilities:

  • Was the employee trained on the procedure?
  • Is there evidence that the training occurred?
  • Did the training verify understanding and ability, or merely document attendance?
  • Was the current procedure readily available when the work was performed?
  • Does the procedure reflect the actual workflow?
  • Are responsibilities and decision authority clear?
  • Does the procedure explain what to do when normal conditions do not exist?
  • Are employees receiving conflicting expectations from supervisors, customers, production demands, or other policies?
  • Is there a practical way to document completion when documentation is required?

Training records are an important starting point, but a signed training record does not necessarily establish competency. Likewise, a procedure that appears reasonable to its author may still be difficult to use in the environment where the work occurs.

Leaders may need to observe the process, speak with employees, review recent examples, and evaluate the risks created by both the written procedure and the actual practice.

If the procedure is current, practical, accessible, clearly understood, properly supported, and consistently reinforced—and an employee still knowingly refuses to follow it—then individual accountability may be appropriate.

But that conclusion should follow the review, not precede it.

Front-line employees are often closest to the solution

Correcting the problem does not always require a new manual, a longer procedure, or another layer of approval.

The best solution is often the simplest one that reliably achieves the organization’s objective without undermining safety, quality, or regulatory requirements.

Front-line employees should be included in developing that solution. They understand where the process becomes difficult, which information is usually missing, what exceptions occur, and which proposed controls would create more work without improving the outcome.

Their preferred solution should not be accepted automatically. Leadership still has to confirm that it meets operational, safety, and compliance needs. But when an employee’s recommendation accomplishes the intended objective without introducing unacceptable risk, it deserves serious consideration.

Including employees in the solution has another benefit: it creates ownership.

Employees are more likely to support a process they helped improve, particularly when leadership demonstrates that their practical experience is valued. That participation can improve implementation, strengthen trust, and reinforce a culture in which employees identify problems instead of quietly working around them.

Fix the system before adding complexity

Not every procedural deviation requires another policy. Sometimes the solution is a clearer responsibility, a revised form, a better handoff, a short checklist, improved training, or an established way to handle exceptions.

The objective should not be to create documentation for its own sake. It should be to build a system that allows employees to perform the work correctly, consistently, and with enough evidence to demonstrate that important requirements have been met.

Employees are still accountable for following reasonable procedures. But organizations are equally responsible for making sure those procedures are practical, current, clear, and supported by the processes needed to carry them out.

Before deciding that an employee failed to follow the system, first determine whether the organization gave them a system they could follow.