Operators distrust OEE when it looks like a score on them, when the number includes losses they cannot control, or when they log stops and nothing changes. Earn trust by promising in writing how the data will and will not be used, showing whose losses they are, and fixing something they asked for within weeks.
They are often right to be wary
Put yourself on the line for a moment. Someone from the office arrives with a clipboard and a new number, and says it is "not about you".
If earlier programs in your plant ended with a target and a telling-off, that doubt is simply experience. Treat the doubt as useful information, and do not try to talk people out of it.
Bad trust also costs you data. Scared people log less, round up and code stops in the safest way, so your data gets worse just when you need it most.
What they say, and what they mean
| What you hear | What is behind it | What earns trust |
|---|---|---|
| "It's just to watch us." | Fear of blame | A written rule on how data is used |
| "That number is wrong." | Stops they cannot control count against them | Show the losses by owner, and check the figures together |
| "More paperwork." | Time taken from the job | A few seconds per stop, and drop one old form |
| "Nothing ever changes." | Past programs that went nowhere | Fix one of their requests quickly |
| "They'll just raise the target." | Gains used against them | Say what a gain will and will not mean |
Make the promise before the clipboard
Say it before the first stop is logged, and put it on the wall. A plant manager should say it in person, since a supervisor cannot promise it alone.
- OEE measures the line and the system around it, not a person.
- The data will not be used for individual discipline or pay.
- Crews see their own data first, before managers discuss it.
- We will tell you what we did with each top loss, even if the answer is "not yet".
Only promise what you will keep. One manager quoting a log at someone's review will undo months of work, and everyone on site will hear about it.
State the limits at the same time. Safety incidents and deliberately false records still follow your normal rules, so say that now and not after the first case.
Check with your works council or union and your privacy rules early, especially if you plan to use cameras. Tell people what the camera sees, who can view it, and how long it is kept.
Answer the hard question straight
Crews will ask whether better numbers mean higher rates, fewer people or fewer shifts. If management has not decided, say that, and say when you will know.
Do not promise "no job losses" unless the owner of the business has agreed and will stand by it. An awkward answer now costs less than a promise that breaks later, and some people may stay wary whatever you say.
Show them whose losses they are
This often changes the conversation. Break down one shift's losses by who can really do something about them.
Example: a shift plans 480 minutes, and OEE is 62.5%. So 300 minutes made good product, and 180 did not.
Show that chart to the crew and ask what they see. Here the biggest loss is a pallet that did not arrive, and the operator's log is what proves it.
Show it the same way when the crew's own losses come out on top. A chart you share only on the good days is a trick, and people will spot it.
See waiting for material and waiting for an operator for how to code these fairly.
Fix something they asked for, fast
Ask each crew what wastes the most time on their shift. You will likely hear about a sticky guide, a missing tool or a sensor that trips for no reason.
Pick one that is cheap and fix it inside two weeks, then put it on a board with the operator's name, if they agree. Of everything on this page, do this first.
With a reason, in a few seconds.
At the line, the next day.
With a date, on the board.
What was done, or why not yet.
A short daily production meeting holds this loop together. A gemba walk helps too, as long as managers go to ask and not to check on people.
Things that destroy trust
- League tables of shifts. Early gaps are often product mix or logging habits. Why OEE differs between shifts shows why they mislead.
- Bonuses on the OEE figure. Pay for the number, and you can expect arguments about what counts, not fewer stops.
- Moving the goalposts. Changing the ideal cycle or the rules without telling crews makes the number look rigged.
- Asking "who?" before "why?". One question about who was on shift, and the log gets shorter.
- Target before baseline. A number set before you know the losses reads as pressure. See how to set OEE targets.
- Hiding that the figure was wrong. If the data had an error, say so at the line. Admitting it builds more trust than the number ever could.
Watch for gaming, without a witch hunt
If planned time keeps growing, or a lot of stops move to "planned", or counts jump on some shifts, people may be defending themselves. Treat that as a sign the number is being used as a weapon, and look at how managers talk about it.
Fix the cause first. Then write down the rules on what counts, so the calculation leaves less room for argument.
How to tell it is working
You will not get this from a survey. Watch for changes on the floor.
- Stops with a useful reason rise, and unknown time falls, without reminders.
- Operators argue with the data, because arguing means they care.
- People bring up losses before you ask.
- Crews start asking to see yesterday's figures.
Keep logging quick, since a slow log wears trust down however good your intentions are. Operator downtime logging has the rules for that, and OEE training for operators has the first session.
A slow log wears trust down, and machine data can take most of that work away. Fabrico, a light MES for OEE, takes stops, speed and counts live from PLCs or IoT sensors, so the operator's part is tagging the cause at the line. See how Fabrico captures stops.
What people ask next
Why do operators resist OEE?
Often because it looks like a personal score, or because it follows a program that changed nothing. Remove the personal side in writing, then act quickly on what they log. How to explain OEE has words that help.
Should OEE be tied to operator bonuses?
We advise against tying it to a personal bonus, because it invites arguments over definitions and quiet changes to the data. If you reward anything, reward the team for finishing improvement actions.
Should you compare OEE between shifts?
Use it to find causes, not to rank crews. Differences often come from product mix, staffing or logging habits, so look there first, as why OEE differs between shifts shows.
How do you handle an operator who refuses to log stops?
Ask what makes it hard, since the reason is usually time, the code list or a past bad experience. Then fix that, and have them help rewrite the list. Taking stops from the machine also removes some of the work, as machine state detection explains.
Will operators accept cameras for OEE?
Some will not, so being clear from the start is the minimum. Say what is filmed, who can see it and how long it is kept, and involve your works council or union where you have one. Computer vision for OEE covers how it is used.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.
Related guides: Plant Manager OEE KPIs: What to See Each Week · How to Start an OEE Program: The First 30 Days · Shop Floor KPIs: What the Crew Should See · Manufacturing KPI Board: Layout That Gets Used