When the operator and the manager disagree on why a line stops

This article is for plant managers, production managers, continuous improvement leads and maintenance managers who have sat through a review where the explanation for a stopped line did not match what the operators said on the floor. It shows how to put the stop reasons logged at the machine next to the meeting-room explanation, so the discussion moves from competing memories to one shared record.

Two explanations for the same stopped line

Every plant knows the scene. On Monday morning the line review shows a poor Friday. The explanation from the meeting room is ready: a material shortage, a late changeover, a new product still settling in. Then someone talks to the operator who ran the line. Her version is different: the infeed jammed every few minutes, she cleared it each time, and nobody called it a stop because it never lasted long enough to be written down.

Neither person is wrong on purpose. They saw different parts of the same shift from different positions. The manager sees the shift through reports, schedules and the last escalation. The operator sees the machine, cycle after cycle. When the two accounts collide, the meeting often settles on the version told by the most senior person in the room, and the action plan follows that version.

Why management and the frontline see different solutions

Mark Galley of ThinkReliability, a US training and consulting firm specialising in root cause analysis with the Cause Mapping method, makes this point in Management and the Frontline See Different Solutions. Starting from a hotel room where the lights above a projection screen could not be switched off separately, he describes a manager who saw an expensive rewiring job and a maintenance technician who saw two bulbs to unscrew. His summary of people with different expertise is short: “They literally see problems differently.”

The article goes beyond the anecdote. Galley explains that an incident usually has several causes, that each cause is a place where a change can be made, and that fixing attention on a single root cause narrows the options an organization can see. Asking frontline staff, technical leads and management for input widens the set of possible solutions.

On a production line the same logic applies one step earlier, to the question that comes before any solution: why did the line stop? The operator and the manager do not only see different fixes. They often hold different accounts of the cause. A structured method organizes the analysis. What the analysis still needs is a factual record of the stops that both sides accept.

What each side sees, and what each side misses

The disagreement is rarely random. It follows the way each role collects information during a shift.

The table shows why both accounts can be partly right. The operator tends to describe the frequent short stops that never reach a report. The manager tends to describe the long stops and the conditions around them. The meeting picks one story because there is no shared view that holds both, and the OEE figure on the slide does not say which story it supports.

Putting machine stop reasons next to the meeting-room explanation

The goal is not to prove who was right. It is to replace two memories with one record that both sides helped to build. A simple routine works in most plants.

1. Capture the stop at the machine, when it happens. The start and end of each stop should be detected automatically, and the operator should qualify the reason from a short list at the station while the event is fresh. A reason typed in at the end of the shift is already an opinion.
2. Keep the reason list short and shared. Build it with operators, maintenance and production together. If operators do not recognize the labels, they pick whatever is closest, and the data drifts back toward the meeting-room version.
3. Write down the meeting-room explanation before opening the data. At the start of the review, the manager states the expected main cause of the loss. This keeps the comparison honest.
4. Put the two side by side. Show the stop sequence for the shift, the minutes lost per reason and the number of stops per reason. Ask where the record confirms the explanation and where it does not.
5. Bring the operator into the discussion of the gaps. Where the record and the explanation differ, the operator is usually the person who can say what happened. This is where frontline know-how becomes practical rather than a slogan.
6. Turn each confirmed cause into an action with an owner. A cause found on the record can be checked again on the record a week later, which closes the loop.

What changes when the record is shared

For example, a line where the review blamed a late changeover might show, on the stop record, that the changeover ran close to plan and that most of the lost minutes came from dozens of short infeed stops spread across the shift. The example is illustrative, but the pattern is familiar: the long event is visible in the meeting, the frequent short ones are visible only at the machine.

Once both views sit on the same screen, three things tend to happen. The discussion moves from who is right to which cause to tackle first. Operators see that what they enter is used, so the quality of the reasons improves. Managers hear solutions they would not have proposed themselves, because the people closest to the problem are now part of the analysis. In Galley’s terms, the causes stay the same; the organization simply sees more of them, and more places to act.

The record also strengthens the root cause analysis itself. A structured method needs facts for each cause it lists. Stop times, durations and reasons logged at the machine give the team those facts, and let it check afterwards whether the chosen solution actually reduced the stops it was meant to remove.

TEEPTRAK measures machine stops and OEE automatically, without connecting to the PLC: a module wired into the electrical cabinet and a sensor at the line, with about one hour of installation per machine and OEE available within 48 hours. Operators qualify stop reasons at the station, so the line and the meeting room work from the same record. TEEPTRAK is used in more than 700 plants in more than 30 countries, where customers see on average a gain of 10 to 15 OEE points and 30% fewer unplanned stops.

Further reading

• Management and the Frontline See Different Solutions (Mark Galley, ThinkReliability)
• Daily production meeting: 15 minutes with yesterday’s downtime data
• Micro-stops and catch-up gestures: what machine stops reveal about work at the station

FAQ

Why do operators and managers give different reasons for the same line stop? They collect information differently. Operators live through every interruption, including short ones that are never reported, while managers see reports, totals and escalations. Both accounts can be partly right, which is why a shared stop record helps more than a debate.

Should the system or the operator choose the stop reason? Both have a role. The start and end of a stop are best detected automatically at the machine, so no stop is missed. The reason is best qualified by the operator at the station, from a short list built with the team, while the event is still fresh.

How does machine stop data support a root cause analysis? It gives each listed cause a fact base: when the stops happened, how long they lasted, how often they repeated and which reason was chosen. The same record then shows whether the action taken actually reduced those stops.