There's a post on Reddit from a manufacturing supervisor that gets at something a lot of companies quietly ignore.
The person had been in the role for a few months. No formal supervisor experience coming in. Their shift's performance had improved. Their manager was starting to loop them into bigger conversations. And then the manager said something that stuck with them: focus on the leadership side. The technical stuff will come.
The supervisor wasn't sure about that. They wanted both. And they were asking strangers on the internet whether that instinct was reasonable.
It is. And the reason it even becomes a question says a lot about how companies set up their new supervisors to either succeed or quietly struggle for the first two years.
Why New Supervisors Ask This Question in the First Place
Most manufacturing supervisors get promoted because they were excellent at the job they were already doing. They knew the line. They knew the equipment. They could troubleshoot in their sleep. That technical credibility is exactly why their team respects them on day one.
Then the role changes. Suddenly they're managing people instead of running the process themselves. And now there are two directions they could develop, and nobody has given them a clear answer on which one actually matters more.
The reason this feels like a real dilemma is that both things genuinely matter. A supervisor who can't credibly talk shop with their team loses authority fast. A supervisor who can't manage a performance issue or run a real 1:1 will watch their best people leave or tune out. You need both. The question is sequencing.
Here's what actually happens when companies don't answer this clearly: the supervisor defaults to what they're most comfortable with, which is the technical work. They keep their hands in the machine because that's where they feel competent. The leadership stuff gets deferred. Weeks turn into months. The team learns that their manager is more likely to troubleshoot alongside them than to have a real conversation about their development. And the manager wonders why they feel stuck.
What the First 90 Days Actually Need
The first three months in a supervisor role are mostly about credibility and basics. Not strategy. Not org charts. Credibility and basics.
Credibility means the team believes you can do the job. For a manufacturing supervisor, some of that comes from technical knowledge, but most of it comes from how you show up. Do you follow through on what you say? Do you treat people the same on a bad production day as a good one? Do you know each person's name and what they're working on? Those aren't soft skills. They're the actual work of the first 90 days.
The basics are things like running a shift handoff that's actually useful, giving feedback in the moment instead of saving everything for a quarterly review, and knowing when to escalate versus when to handle something yourself. None of that requires deep leadership theory. It requires practice and someone giving you honest feedback on what you're doing.
Technical knowledge in this window serves one purpose: it keeps you credible enough that your team will let you lead them. You don't need to be the best technician on the shift anymore. You need to be good enough that nobody questions whether you understand the work.
The leadership habits are the thing that compound. A supervisor who builds real people skills in year one will be significantly more effective by year three than someone who stayed close to the technical work because nobody pointed them in a clear direction.
The Real Mistake Companies Make Here
Most organizations don't answer the leadership versus technical question at all. They promote someone, hand them a new title, and expect the person to figure out the rest. Maybe there's a one-day onboarding. Maybe a binder. Maybe a manager above them who means well but is also stretched across three other priorities.
What doesn't happen is a structured process that builds leadership habits over time, alongside the technical development that was already happening. The two get treated as separate tracks, or one gets ignored entirely.
That's where the gap shows up. Six months in, the supervisor is competent at the technical side and genuinely uncertain about the people side. They haven't had anyone model what a good 1:1 looks like. They haven't practiced giving feedback that actually changes behavior. They've been winging it, and it's starting to show in their team's numbers.
The manager from that Reddit post who told their supervisor to "focus on leadership" was right in instinct. But instinct without structure doesn't produce habits. It produces a supervisor who's been told to lead people without being taught how.
What Actually Helps
The supervisors who figure this out fastest have a few things in common.
They get repetition on the basics early. Not a workshop. Not a binder. Actual repetition, where they try something, get feedback, adjust, and try again. That's how habits form. A one-time training session on giving feedback doesn't produce someone who gives good feedback. It produces someone who sat through a session on giving feedback.
They have a peer group. Talking through a hard situation with someone who is also three months into a supervisor role is different from asking your manager for advice. The peer group normalizes the struggle and shortens the learning curve.
And they get clarity on what "focusing on leadership" actually means in practice, week by week. Not as a concept. As a set of specific behaviors they're working to build.
The technical skills don't go away. A good supervisor keeps developing there too. But the leadership habits are the thing that compound. A supervisor who builds real people skills in year one will be significantly more effective by year three than someone who stayed close to the technical work because nobody pointed them in a clear direction.
The Reddit supervisor asking whether their instinct was reasonable? They were right to want both. What they actually needed was someone to show them the order, and then stay with them long enough for the habits to stick.
If you're an HR director or people lead at a manufacturing company watching new supervisors navigate this exact question, that's the gap Groveland was built to fill. Learn how we work with manufacturing teams here.
Frequently Asked Questions
New supervisors should build a foundation in both, but leadership skills need deliberate, structured development early, while technical skills often develop more naturally through daily work. The instinct to stay close to the technical side is common and understandable, but supervisors who build people skills in their first year outperform those who defer that development.
Most were promoted because of technical performance, not leadership readiness. The skills that made them great individual contributors don't automatically transfer to managing people. Without a structured process to build leadership habits early, most supervisors default to what they already know, which is the technical work.
It means repeated practice on specific behaviors, not a one-time workshop. Things like running effective shift handoffs, giving in-the-moment feedback, and handling a difficult team situation before it escalates. The repetition, combined with honest feedback, is what builds habits that actually hold up under production pressure.
Most supervisors start to feel meaningfully more confident around months four to six, assuming they're getting real feedback and some form of structured development. Without that structure, the uncertainty often persists much longer, and the team feels it before the supervisor does.
It's usually a signal that the supervisor hasn't been given a clear framework for what leadership looks like in practice. The fix isn't a conversation telling them to lead more. It's giving them a structured, repeatable process for building leadership behaviors over time, with enough support that the habits actually form.