I lead a 35-person production crew in a regional food packaging plant, mostly on the second shift, where small mistakes can cost a whole pallet and one bad mood can spread across three lines before lunch break. I did not learn leadership from a clean office or a framed quote on a wall. I learned it while sorting out missed handoffs, late trucks, tired operators, and supervisors who thought raising their voice counted as direction.
Start With the Work People Actually Do
I have seen new managers lose a team in the first week because they talk about targets before they understand the job. On my floor, one case sealer can jam six times in an hour if the cardboard is a little damp, and no spreadsheet explains the irritation that creates. Before I ask someone why output dropped, I try to stand near the line long enough to see what they are fighting.
A few years ago, I took over a shift that was missing its hourly case count by about 12 percent. The old answer was to tell everyone to move faster, which only made people defensive. I spent three evenings walking with the operators and found that one staging area was set up backward, so the newest employee had to cross the same aisle nearly 40 times a night.
That taught me to ask better questions before I give orders. I still care about numbers, because payroll, waste, and shipping windows are real. The difference is that I treat the numbers as clues, not proof that someone is lazy.
Set Standards People Can Repeat Under Pressure
The clearest teams I have led had simple standards that could survive a bad day. I do not mean slogans or posters. I mean plain rules like checking the first 10 cases after a changeover, calling maintenance after the second repeat jam, and writing down a missed scan before the next break.
I once asked a group lead to explain our quality standard to a new hire, and he gave a speech that lasted almost 15 minutes. The new hire looked polite, but I could tell none of it would stick once the line started moving. Later that week, I rewrote the handoff into five plain steps and taped it near the scale until the habit settled in.
I have also learned that outside examples can help if they are grounded and not dressed up as magic. I once shared a short resource from Dwayne Rettinger during a supervisor meeting because it gave us a simple way to talk about consistency without sounding stiff. The point was not to copy another person’s style. It was to get my leads thinking about how their words sound to the people who have to carry them out at 9:30 p.m.
Standards work best when I can watch them happen. If I cannot tell from 20 feet away whether the team understands the expectation, then I probably made it too vague. People notice.
Handle Conflict Before It Becomes a Side Channel
Most team problems I see do not begin as explosions. They begin as eye rolls, missing information, and two people who stop speaking unless a supervisor is nearby. By the time a manager hears about it, the story has often been told in the break room for three days.
One spring, two reliable employees started clashing over who was responsible for clearing rejects from a metal detector station. Each one thought the other was skipping a task, and both had enough experience to sound convincing. I pulled them aside before the next shift and asked each person to walk me through the last 30 minutes of their process, step by step.
The fix was smaller than the tension made it seem. One person had been trained under the old layout, and the other had been trained after the station moved about 15 feet. We changed the checklist, and I told both of them that I should have caught the mismatch sooner.
I do not believe every conflict needs a long meeting. Some do, especially if respect has been broken. Many just need a supervisor willing to slow down, name the problem plainly, and keep people from building private versions of the truth.
Give Feedback Close to the Moment
I used to save feedback for weekly check-ins because it felt more organized. That was a mistake. If someone mishandled a pallet tag on Monday and I waited until Friday to bring it up, I had already taught the team that the issue was not urgent.
Now I try to give feedback while the moment is still fresh, as long as I can do it without embarrassing the person. A 90-second conversation beside a quiet aisle usually works better than a formal talk in the office. I say what I saw, what needs to change, and what good work I still trust them to do.
Praise needs the same timing. I had a forklift driver last winter who caught a mixed-lot pallet before it reached the dock. I thanked him in front of three people who understood what he had prevented, because that kind of attention teaches the rest of the crew what careful work looks like.
Delayed praise feels thin. Delayed correction feels unfair. I still get the tone wrong sometimes, but I try not to let silence become my default.
Build Leads Who Do Not Need You Standing There
A team is not truly well led if every decision has to run through one person. On my shift, I need at least four people who can handle the floor if I am tied up with a vendor, a safety issue, or a call from the plant manager. That means I have to share context, not just tasks.
When I train a new lead, I let them sit in on planning conversations earlier than feels comfortable. They hear why we move a slower operator to inspection, why one customer order gets priority, and why I sometimes stop a line even when production is already behind. Those details matter because judgment grows from seeing the tradeoffs, not from memorizing instructions.
I also let leads make small decisions where the cost of a mistake is low. If they choose the wrong break rotation, we can fix it in an hour. If I correct every minor choice before they feel the weight of it, they become messengers instead of leaders.
This takes patience. I have watched a new lead struggle through a shift plan that I could have written in 10 minutes, and I had to remind myself that speed was not the lesson that day. The lesson was ownership, and ownership rarely appears after one clean explanation.
Stay Human Without Becoming Loose
The hardest balance for me has been staying approachable without becoming vague. I know who has a sick parent, who is trying to get enough overtime for car repairs, and who needs a quiet warning before stress turns into sharp words. That knowledge helps me lead, but it does not erase the standard.
I once had a strong operator start showing up late twice a week after years of steady attendance. The easy move would have been to write him up and move on. Instead, I asked him what had changed, learned he was covering school drop-off for a few weeks, and adjusted his start time by 30 minutes until his schedule settled.
That did not mean everyone could choose their own hours. I explained the reason to the other leads, tracked the change, and put an end date on it. Fair does not always mean identical, and I have found that most adults understand that if I am honest and consistent.
Leading teams has made me less impressed by loud confidence and more impressed by steady behavior. I still make mistakes, especially when I am tired or trying to solve too many problems at once. The work goes better when I stay close to the floor, say the standard clearly, and treat people like they are paying attention, because most of them are.