Short answer
The difference comes from looking through the lens of a job title instead of the person and their skills. The fix isn't just empathy — it's consistent practice: competency maps, cross-training and real action behind the declarations, applied the same way to an operator as to a manager.
"Such a shame — he learned so much"
An experienced operator is leaving. He knows the machine, knows the process, hears when something starts to "sound different," catches a problem before it ever shows up in a report. The reaction on the shop floor is almost always the same: "Such a shame. He learned so much over the years. We're losing that experience." It's hard to disagree.
This is exactly the moment to pause and ask the key question: why? What is it about our organization that fails to offer what this person will get somewhere else? An organization's growth should always rest on the people who build it — and if a company isn't a workplace someone stays in until retirement, that's worth stopping to address, and worth acting on. That's what always delivers the greatest value and the most stable, long-term path to operational excellence.
And when a manager leaves
When a position loses an experienced manager, we hear different sentences: "They want to grow." "They need new challenges." "They want different experience." "After a few years, it's a natural step." And usually, we understand it completely — without a hint of resentment.
And here — even though it's easier for us to accept — the exact same question that came up with the operator should come up again: why? Did we do enough for the manager to find, with us, what they're now looking for somewhere else? Finding it easier to accept doesn't make the question any less valid — sometimes it just means it's more comfortable not to ask it.
The same needs, different labels
Why don't we look at the operator the same way? They might also want to learn something new, work with different technology, test themselves in a different environment, earn more, get promoted, or simply see what's out there. The need for growth, change and finding your own path isn't tied to a job title — and yet we call a manager's growth ambition, and a good production employee's departure a lack of loyalty.
The person and their skills, not the job title
What matters is looking not through the lens of a job title — manager or operator — but through the person. It isn't the function itself but the person and their skills that create real value for the organization. A job title or role name shouldn't limit anyone from supporting others wherever they can — whether that's an operator training new hires or a manager stepping back closer to the process.
Competency maps and cross-training: declarations vs. action
More and more organizations talk about competency maps and cross-training employees — about multi-skilling and growth becoming the norm, not the exception. That's a good direction. But it's worth asking whether real action follows those declarations: is an operator's growth path as visible and real as a manager's, or only written into a slide deck. A competency map only makes sense when it's a living tool for managing people's growth on the shop floor — not a document created once and left to gather dust.
A mature response from a manager
An organization should of course try to retain good people — talk to them, ask about their needs, offer real growth opportunities, build a workplace people don't want to leave. But sometimes the most mature response from a manager is simply to say: "It's a shame you're leaving. You mattered to us. I understand your decision — go, grow. And if you ever want to come back, the door is open." Regardless of whether that person sat at a desk or stood at a machine.
Author
Andrzej Smoleński — production and operations transformation manager, Lean Six Sigma Master Black Belt. More than 20 years of experience developing processes, teams and management systems.