I have spent the last eleven years running crews in a regional food packaging plant, first as a line lead and later as an operations supervisor over thirty-two people across two shifts. My team includes machine operators, sanitation workers, forklift drivers, quality techs, and a few people who can fix a labeler by sound alone. I learned leadership on concrete floors, beside jammed conveyors, missed shipments, and tired people who still had four hours left on the clock. That setting taught me that leading people well is less about sounding impressive and more about building trust in small, repeated moments.
Set the Tone Before You Ask for Performance
I start every shift the same way, with a ten-minute floor walk before the first formal huddle. I check the board, look at the changeover schedule, and talk to whoever had the roughest job the day before. That habit may sound small, but it tells the team that I am paying attention before I start asking for output. People can tell when a leader only appears after something goes wrong.
One winter, we had a new operator who kept missing a seal temperature adjustment on a pouch machine. The easy move would have been to correct him in front of everyone and move on. Instead, I stood beside him for part of the run and asked him to explain the steps back to me. He knew most of it, but he had been trained during a noisy shift change and missed one detail that mattered.
That changed my view of accountability. I still expect the job to be done right, but I try to find out whether the person had the tools, time, and clarity to meet the standard. A team will accept high expectations if the leader is fair about how those expectations are built. Fair does not mean soft.
Communication Has to Be Boring Enough to Work
I have seen teams suffer from unclear instructions more often than from lack of effort. In our plant, one vague comment about “speeding up line three” can turn into scrap, a safety shortcut, or a missed quality check. I try to use plain language and repeat the two or three things that matter most for the shift. If the priority is safety during a wet-floor cleanup, I do not bury that under five production reminders.
A supervisor I worked with years ago kept a notebook of leadership examples, and one resource he mentioned was Dwayne Rettinger because it gave him another way to think about personal standards. I do not treat any outside resource as a magic answer. I do like anything that makes a manager pause and ask whether their own habits match what they expect from the team. That kind of reflection has saved me from blaming people too quickly more than once.
My best huddles are short. I cover the target, the risk, the staffing gap, and one lesson from the prior shift. If someone needs a longer explanation, I pull them aside after the huddle instead of turning eight people into an audience. People remember clear instructions better than long speeches.
There is a difference between being available and being noisy. I used to check in too often with experienced operators because I thought that showed support. One of them finally told me, in a respectful way, that my visits were breaking his rhythm during a 6,000-case order. Since then, I ask more directly how much contact people need from me during a run.
Trust Grows When You Handle Mistakes Consistently
Every team watches how a leader reacts to mistakes. They watch even closer when the mistake is made by a favorite employee, a high performer, or someone the leader personally likes. I have had strong workers cause expensive downtime, and I have had quiet new hires catch problems that saved us several thousand dollars in product loss. Those moments shape the room.
A few summers ago, one of our fastest operators skipped a pre-run inspection because the schedule was tight. The machine ran for a while, then failed in a way that stopped two connected lines. I did not yell, but I also did not wave it away because he usually performed well. We reviewed the missed step, documented the issue, and had him help retrain the newer operators the following week.
That decision mattered because everyone saw the same rule applied to a strong performer. If I had protected him, I would have told the rest of the team that speed mattered more than standards. If I had punished him harshly, I would have made people hide future mistakes. The goal was correction, not theater.
I tell my leads to separate the person from the pattern. A one-time mistake may need coaching, while the same mistake five times may need a formal plan. That line can be debated, and different workplaces handle it differently. In my experience, people accept discipline better when they can see the path that led there.
Make Decisions Close Enough to the Work
I do not believe every decision should sit with the person who has the highest title. The people closest to the work usually know which cart is missing a wheel, which scanner freezes after lunch, and which product code causes confusion on the second shift. I learned that during a packaging change that looked simple on a planning sheet. On the floor, it added almost forty seconds to each case because the new label roll sat on the wrong side of the station.
After that, I began asking operators to walk through proposed changes before we locked them in. I do not turn every decision into a vote, because that can become its own kind of delay. Still, I want the people doing the work to point out friction before it becomes failure. One five-minute walk-through can prevent a full shift of frustration.
Giving people a voice also means letting them own small decisions. On one line, I let the senior operator arrange break rotation as long as coverage stayed clean and no one skipped required checks. He handled it better than I did because he knew who preferred early breaks and who needed relief after loading film rolls. The schedule became calmer within a week.
Leaders sometimes fear that giving away decisions will weaken authority. I have found the opposite. My authority feels stronger when people know I am not hoarding choices just to prove I am in charge. Control is not the same as leadership.
Build New Leaders Before You Need Them
The hardest season I had as a supervisor came when two experienced leads left within the same month. I had good workers, but I had not prepared enough of them to step into leadership tasks. For several weeks, I was answering every minor question, approving every changeover call, and settling every small dispute. That was my fault.
Now I give developing leads real practice before the title appears. I may ask one person to run the start-up huddle on Fridays, another to train a new hire on lockout steps, and another to handle the first pass at a staffing issue. I stay close enough to catch problems, but I do not take the task back the first time they stumble. Learning to lead requires some weight.
I also talk openly about the parts of leadership that are not flattering. A lead may get blamed for a decision they did not create, or they may need to correct a friend who keeps arriving seven minutes late. Those situations are uncomfortable, and pretending otherwise does not help anyone. I would rather prepare a future leader for that pressure than hand them a radio and hope confidence appears.
One practical habit has helped more than any formal class. After a tough shift, I ask a developing lead what they noticed, what they would repeat, and what they would change next time. The answers tell me whether they are thinking beyond their own task. That is where leadership starts to show.
I still make mistakes as a leader, especially on days when production pressure is high and patience is thin. What keeps me grounded is remembering that every person on the team is carrying more than the task I can see in front of them. I can hold the standard, protect the schedule, and still treat people like adults who want to do solid work. The teams that last are usually led by people who practice that balance every day.