There is no shortage of content about what frontline supervisors should do differently.
Walk any industrial leadership conference, scroll any manufacturing LinkedIn feed, search any podcast platform — the prescriptions are there. Delegate better. Coach more. Hold the standard. Develop your people. Be present.
What almost never makes it into the conversation is the perspective that would make all of it land harder: the person on the other side of that leadership. The operator who has spent a decade at the machine, experienced what it means to be led by the full spectrum of industrial supervisors, and navigated the informal path into leadership themselves without a development program waiting for them.
That’s the conversation this week was built around.
Jared Reining has been in manufacturing for a decade. Machinist at PharmaMed in Fargo. Former frontline supervisor. Minnesota National Guard infantryman. He found this show the way a lot of people find it — through a conversation in the manufacturing space that pointed him here. He wasn’t invited because he has a framework to sell or a consulting practice to validate. He was invited because he’s been on the floor — the one people are constantly talking about from a distance — and his account of what that experience actually looks like deserves to be on the record.
What follows are four things our conversation surfaced that every senior manufacturing leader should hear directly.
The Transition Nobody Actually Builds For
Jared’s entry into supervision didn’t begin with a promotion conversation or a training program. It began with a new hire who needed direction and a shop owner who trusted the most experienced person on the floor to provide it.
There was no formal authority. No defined scope. No title change. Just an implicit hand-off: before he comes to me with a question, have him come to you. And then, gradually, a small machine shop grew, one hire at a time, until Jared was the de facto lead for a team of several people, managing deadlines, developing skills in others, and compensating for the gaps in a growing operation by staying late and pushing harder.
He described those first several months honestly. The overwhelm was real. The stress lived primarily in the production and deadline side of the role, not the people side — Jared is, by his own account, someone who genuinely enjoys working with people. But the weight of being responsible for an outcome he couldn’t produce alone, without the infrastructure to support him, had a cost that showed up in his schedule and his personal life before it showed up anywhere on paper.
Here’s what’s worth naming about his experience: it was sequential. He was eased into increasing responsibility over time rather than dropped into a formal role with no preparation. That gradual exposure — one person, then three, then a few more — gave him a runway that most promotions simply don’t provide.
And he still found it hard. He still compensated with extra hours, self-directed study, and personal resilience that shouldn’t have been the load-bearing element of his development.
Most promotions don’t give anyone a runway. Most promotions are a tap on the shoulder, a new title, and a floor to run on Monday. The question worth asking is: what does that transition look like for the person who didn’t come into it with Jared’s natural orientation toward people — and without his instinct to prepare himself for a role the organization never prepared him for?
The Silent Signal Your Floor Is Sending
The most consistent observation Jared made about the supervisors above him over a decade in manufacturing was not about competence or temperament. It was about time and investment.
His supervisors, across organizations, showed up in one specific context: when something needed to be addressed. Performance issues, production misses, real problems that needed a response. In those moments, leadership arrived. When nothing required fixing, the check-in didn’t happen. The conversation didn’t happen. The investment of time beyond the transactional minimum didn’t happen.
He described it plainly: “If I don’t need to talk to you to fix something, that’s it. I have nothing else to say.”
He said it without resentment. He has good relationships with his supervisors. He’s not describing leaders who failed in some dramatic way — he’s describing a pattern that is simply the organizational default when a leader is operating at full capacity and every conversation that actually occurs is one that couldn’t be avoided.
But that pattern has a cost.
A team member who performs well, stays out of trouble, and never gives leadership a reason to intervene receives a clear and consistent signal from the absence of proactive investment: you matter when something is broken. When things are running, you don’t require attention.
That signal doesn’t produce disengagement overnight. It accumulates. It shows up in the recruiter call that gets answered because there was no real reason to stay rooted. It shows up in the quiet ceiling a good performer places on how much of themselves they bring to the work. It shows up in the gap between what someone is capable of producing and what they’re actually producing, a gap that no engagement survey will trace to its actual source.
The fix is not a formal program. It is not an additional meeting on the calendar. It is a consistent, brief, intentional conversation that exists outside the problem-solving context. What do you need that you’re not getting? What’s getting in your way that I haven’t heard about? What’s going well that nobody has acknowledged?
These conversations don’t take long, but they rarely happen. And their absence is one of the most expensive invisible costs inside industrial operations.
The Friction Underneath Everything
The next insight from Jared’s account that deserves more real estate than it usually gets came from a concept he’s absorbed from lean manufacturing thinking: the idea that small, recurring friction doesn’t become insignificant just because it isn’t dramatic.
His shorthand for it was vivid. He called it dooty on your diamonds.
The principle: you can add positive things to someone’s day indefinitely, and those additions won’t fully register if the recurring annoyances underneath them are still present. The tool that’s never where it belongs. The process that requires three steps when it could require one. The small thing that keeps happening that nobody has found ten minutes to address because it doesn’t rise to the level of a crisis.
These aren’t trivial. In aggregate, they are the daily physical and operational experience of being on that floor. And they communicate something to the person at the machine: either the organization notices and addresses what makes the work harder than it needs to be, or it doesn’t.
When leaders run at capacity — managing up and down simultaneously, attending meetings, chasing metrics — they are often the last to know what the small frictions actually are. The people who know are the ones doing the work. Which brings us back to the previous insight: the proactive check-in that almost never happens is also the mechanism most likely to surface these friction points before they’ve been sitting there for months.
Two minutes spent removing a recurring annoyance produces more visible return on floor engagement than pizza parties or culture initiatives. Not because the annoyance was large. Because the act of addressing it communicated something: this place actually pays attention to what the work is like for the people doing it.
That communication lands differently than a poster in the lobby. It lands at the machine, where people are actually deciding how they feel about where they work.
What the Floor Is Actually Asking For
Toward the end of the conversation, the question I asked Jared was direct: if the person responsible for developing frontline supervisors in your organization is listening right now, what do you want them to understand that they probably don’t?
His answer circled through everything he’d already described, but landed in a specific place.
The difference between the leaders who produced a meaningful experience for the people underneath them and the leaders who didn’t — in his view, across a decade of observation — wasn’t talent or personality. It was the investment of time and attention that existed outside the corrective or task-focused context. Leaders who asked questions without an agenda. Leaders who checked in before something went wrong. Leaders who treated the people on their teams as worth knowing, not just worth directing.
That behavior isn’t a personality type. It doesn’t emerge spontaneously from good intentions and a promotion. It is a practice — one that has to be taught, structured, and supported by the organization responsible for the leader who’s supposed to deliver it.
Jared was developing himself because the organization he worked in wasn’t going to do it for him. He read the books. He studied the frameworks. He put himself through the preparation the role demanded because he had a longer-term vision and understood what it would require. Not every person on the path to supervision is built that way — and more importantly, they shouldn’t have to be. The capability to develop people intentionally is not a natural talent that some candidates bring to the table and others don’t. It’s a skill. Skills are built with systems, not with hope.
The floor knows the difference between an organization that develops its leaders and one that promotes them and watches. It reads every check-in that happens and every one that doesn’t. It reads whether the small friction gets fixed or keeps sitting there. It reads the investment — or the absence of it — and makes daily decisions about how much of itself to bring to the work.
That’s not an engagement problem. That’s a leadership infrastructure problem.
Where to Start
If Jared’s account sounds familiar — the pattern of promotion without preparation, check-ins that only happen around problems, and small friction that’s been sitting on your floor for longer than it should have is something you recognize — The Leader’s Preflight Checklist is the starting point. Download it free at operationlead.com/checklist.
And if you’re a senior leader who’s starting to see the gap between the supervisors you have and the supervisors your operation needs, and you want to understand what it would look like to build development infrastructure rather than run another training event — request a call to learn about our system and process at operationlead.kit.com/requestcall.
The floor is talking. It always has been. The question is whether the organization has built anything that’s actually set up to hear it.
Let’s Lead,
Craig
