The Symptom Is Not the System

The Symptom Is Not the System

Why Fixing the Visible Problem Does Not Always Fix the Factory

A machine stops. An operator makes a mistake. A near miss occurs. A maintenance task takes longer than expected.

The immediate response may be to repair the machine, retrain the employee, revise the procedure or add another control. Sometimes that is exactly what is required. But the visible event is not always the complete problem. A recurring error may involve more than training; a maintenance delay may begin before the repair; a near miss may expose weaknesses in identification, information or process design.

The important distinction is between what happened and what made it possible.

The Occupational Safety and Health Administration (OSHA) recommends investigating underlying causes rather than stopping at fault or blame. The UK Health and Safety Executive (HSE) also emphasises human and organisational factors in adverse events.

The event tells us what happened. The system helps explain why it was possible.

1. Why Factories Fix What They Can See

Visible events create pressure for visible solutions. Production needs equipment restored. Supervisors need operations moving. Maintenance needs the job closed. Safety teams need controls reinforced.

The difficulty begins when the response addresses only the point where the failure became visible.

A component is replaced. Retraining is completed. A checklist is added. A warning sign is installed. The issue is closed.

If a similar event later occurs, the recurrence may indicate that the intervention corrected the immediate condition without changing the wider environment.

This does not make every repair or training action insufficient. It means the action should be judged against the condition it was meant to address. An investigation should establish what happened, the sequence leading to it, the conditions present and the controls expected to prevent it. It should also ask why those controls did not work as intended.

The visible issue is often where attention starts, not where the investigation should end.

2. “Operator Error” Is a Description, Not a Diagnosis

“Operator error” describes an action. It does not automatically explain the circumstances surrounding it.

When a procedure has not been followed, consider whether it was available, understandable and applicable to the actual task. Machine configuration, workload, communication, tools, time pressure and information can all influence execution.

These considerations do not remove individual accountability. They help determine whether the working system supported the expected behaviour. If a worker selects the wrong setting, ask whether the controls were clearly identified, the instruction matched the machine configuration and the information needed to check was available.

OSHA cautions against treating carelessness or failure to follow a procedure as a complete explanation because underlying causes may remain unidentified. HSE guidance similarly recognises the influence of design, workload, communication and working conditions on human performance.

The practical shift is from assigning a label to understanding the conditions surrounding the action.

3. Maintenance Problems Often Begin Before the Repair

A maintenance task may run beyond its planned duration. The repair itself may be technically difficult, but time can also be lost before the technical work begins.

Before repair begins, the equipment may need identification, maintenance history or drawings may need to be located, isolation may need clarification and another department may need to release the asset.

The repair and the process around it are not the same. Measuring hands-on repair time can hide time spent searching, waiting and coordinating. NIST research on maintenance technology implementation highlights the need to understand the human and organisational problem before choosing maintenance technology.

Establish where time is being spent before introducing another system.

4. Near Misses Are Signals

A near miss can reveal a weakness before it produces harm.

Consider an illustrative situation: two similar machines are difficult to distinguish, and a technician approaches the wrong equipment before recognising the error.

A reminder to verify the asset may be appropriate. The event can also raise questions about asset numbering, workplace layout, work-order information and consistency between procedures and digital systems. Establish what allowed the confusion and whether the same condition exists elsewhere.

OSHA encourages employers to investigate close calls because they can expose hazards and shortcomings before a more serious event occurs.

The absence of harm does not mean the absence of useful information.

5. When Corrective Action Stops Too Soon

A corrective action is only effective when it changes the condition that needs to change.

Retraining, another inspection, a replacement component or a warning sign may all be valid responses. The question is whether the conditions associated with the failure have changed.

Review what was believed to be the cause, what changed and what remains. Check whether the new control is available, understood and practical. Completion status is not effectiveness; an action can be marked complete while the underlying condition remains.

A corrective action should be judged by its effectiveness, not only its completion status.

6. Look for Patterns That Travel

Weaknesses can cross equipment, departments and shifts.

An equipment-identification issue found during maintenance may also affect machine safety. An information gap between Engineering and Maintenance may appear between Production and Quality. A procedure problem on one asset may exist on similar equipment. Dependence on experienced employees may repeat across shifts.

A single event may have a local explanation; repeated events may point to a shared condition. Similar symptoms do not prove a common cause, so compare the circumstances and evidence.

Look across incident reports, near misses, maintenance delays, audit findings and repeated requests for clarification. OSHA recommends identifying trends rather than treating every event as isolated.

BRIGS examines these relationships through People, Machines and Processes, including the interfaces where information and responsibility move. Ask whether the same condition exists elsewhere.

7. Human Factors Belong Inside the Investigation

People interpret information, make decisions, respond to changing conditions and adapt when the intended process does not match reality. Human factors in manufacturing therefore matter to safety, quality, maintenance and operational performance.

This does not mean every error is caused by the system. Training can be inadequate, equipment can fail and individuals can make mistakes. The investigation asks whether the environment made the desired action clear and achievable.

Are labels readable? Can the correct asset be identified? Is the instruction available at the point of work? Are warnings and controls visible under actual conditions? This is where Factory UX becomes relevant: the way people see, understand and navigate the workplace is part of the operating environment.

8. Diagnose Before You Design

The quality of an intervention depends on diagnosis. A solution should follow evidence, not the first visible explanation.

SEE — Understand what happened. Examine the task, workplace, equipment, information and surrounding conditions.

CONNECT — Understand the relationships between People, Machines, Processes, information, responsibilities and controls.

DIAGNOSE — Identify the underlying condition. Separate the immediate event from technical, procedural, informational, organisational, environmental or human factors.

DESIGN — Address what needs to change. The intervention may involve Factory UX, process redesign, workplace changes, training, machine-safety controls, Factory OS or a combination.

IMPLEMENT — Make the change work under actual operating conditions and ensure it is understood by the people expected to use it.

IMPROVE — Check whether the condition has changed. Review recurrence, similar situations elsewhere and evidence that the new approach is working.

The method is not a universal formula. The evidence should determine the intervention.

9. Where BRIGS Creates Value

BRIGS connects diagnosis to the right intervention.

Factory UX addresses the human interface: equipment, instructions, visual information and the physical workplace.

Factory OS addresses operational continuity: information, workflows, permissions, maintenance activities and controls.

Machine Safety and Process Safety address equipment interaction, hazardous energy and process controls.

Workplace improvement ensures that a solution works where people perform the task.

These are intervention layers, not predetermined answers. The diagnosis determines which are needed.

10. A Practical Investigation Checklist

Use these questions to examine the conditions around an event:

People — What were people expected to do? Were responsibilities, competence and information clear?

Machines — Were assets, energy sources and isolation points identified? Did the equipment match the available documentation?

Process — Did the procedure reflect actual conditions? Were approvals, escalation and information access clear?

Interfaces — Where did responsibility or information move? Where did work slow down or require manual recovery?

Control and Learning — Was the issue tracked through closure? Were similar conditions visible elsewhere? Was the intervention verified?

This is not an audit or a substitute for a formal investigation. It is a practical lens for looking beyond the immediate event.

Conclusion: From Event Closure to System Improvement

Factories will experience failures, deviations, delays and near misses. What matters is what the organisation learns.

A correction may restore production, training may address a competence gap and a new control may address a hazard. The response should also establish whether the conditions that allowed the event have changed.

At BRIGS, this means examining People, Machines, Processes, information and controls before choosing a combination of Factory UX, Factory OS, machine safety, process safety or workplace improvement.

The event is the starting point. Understanding the conditions around it is what makes improvement possible.

A Practical Next Step

Use the BRIGS Factory Systems Self-Assessment to examine recurring conditions across People, Machines, Processes, Information, Interfaces and Control. It can help identify friction, information gaps, process inconsistencies and areas for deeper investigation.

Start with one recurring issue. Examine what surrounds it. Then determine what the system needs—not simply what the event seems to require.