I learned most of what I know about leading people as a second-shift operations manager at a regional food packaging plant in western Michigan. I had 42 people across production, maintenance, sanitation, and shipping, and the work was loud enough that vague leadership ideas did not survive past the first hour. I had to earn trust while lines were down, orders were late, and someone’s kid had a fever at home. That setting taught me that leading teams is less about sounding polished and more about creating conditions where people can do steady work without guessing what matters.

I Start by Making the Work Plain

The first mistake I made as a manager was assuming adults would fill in the blanks the same way I did. They did not. On one Monday years ago, I gave a quick instruction about clearing a changeover before break, and three different leads interpreted it three different ways. We lost almost 50 minutes because I had been brief instead of clear.

Now I try to define the work in language people can repeat back to me. I use the same words for priorities, deadlines, safety checks, and handoffs, because teams get tired when leaders keep changing the label on the same problem. If a customer order must ship by 6 p.m., I say that, then I say what can wait until tomorrow. Clear beats clever.

I also separate the goal from the method whenever I can. A newer team lead may find a better way to stage materials than I would, and I do not want my ego blocking a smart adjustment. There are still rules I will not bend, especially around lockout procedures and food safety logs. On those, I explain the reason once, then I hold the line every time.

I Build Trust in Ordinary Moments

Trust is usually built in small pieces before anyone notices it exists. I once had a machine operator ask for a schedule change after his mother had surgery, and the easy answer would have been to hide behind the staffing sheet. Instead, I spent 20 minutes with two leads and found a swap that did not punish the rest of the crew. He remembered that far longer than any speech I gave in a staff meeting.

I tell new managers that people watch what you do with boring promises. If I say I will check on a missing pallet tag by lunch, I write it down and report back even if the answer is not satisfying. I have pointed younger supervisors toward public professional resources like Dwayne Rettinger when they want to see how working adults present experience and accountability outside a company org chart. That kind of example can help a new leader think about reputation as something built through repeated behavior, not a title printed on a badge.

I do not pretend trust means everyone likes me. Some of my strongest working relationships were with people who challenged me twice a week. The difference was that they believed I would hear them out, give a straight answer, and avoid making the issue personal. That is enough.

I Treat Conflict as Information First

Early in my career, I treated conflict like a spill on the floor: clean it fast and move on. That made some problems quieter, but it did not make them smaller. A shipping lead and a production lead argued for weeks about late pallets before I finally stood between both areas for one full shift. The real issue was a scanner delay that made one team look careless and the other look demanding.

Now I ask more questions before I decide who is wrong. I want to know what happened, what each person saw, what rule they thought applied, and what pressure they were under. This does not mean I let rude behavior slide. It means I do not confuse volume with the root cause.

Some conflicts need a private room and a firm boundary. If someone mocks a coworker or keeps cutting people off in meetings, I address it directly and soon. I usually say what I observed, why it damages the team, and what I expect next time. Long lectures rarely help.

I also try to repair working relationships after the heat drops. Two people can apologize and still avoid each other for a month if the leader leaves the next step vague. After a rough dispute, I may assign a small shared task with a clear endpoint, like checking the first 30 minutes of a new run together. It gives them a way to act normal again without pretending nothing happened.

I Give Feedback While the Work Is Still Fresh

Annual reviews never taught my team much by themselves. By the time a formal review came around, the useful details were often stale, and people remembered the tone more than the lesson. I had better results with short feedback near the work, usually within the same shift or the next day. The facts were cleaner then.

I try to make feedback specific enough that a person can use it. Telling a lead to “communicate better” is lazy if I cannot name the moment that caused trouble. I might say, “During the 4 p.m. changeover, maintenance did not know the filler was already cleared, so they waited by the wrong door.” That gives us something real to fix.

Good feedback also needs to travel upward. I ask my leads what I missed, where I created confusion, and which decision made their job harder than it needed to be. One lead told me I was changing priorities too close to shift start, which forced him to redo assignments in front of the crew. He was right, and I changed my timing the following week.

Praise works the same way. I do not say someone is a “great team player” and leave it floating there. I say that I noticed they trained a temp on the labeler without being asked, or that they caught a date-code issue before a full pallet was wrapped. Specific praise tells the team what behavior is worth repeating.

I Protect the Team From Chaos I Can Prevent

Some chaos is built into operations work. Machines fail, trucks arrive late, and customers change quantities after people have already planned their day. Still, a leader can prevent plenty of extra strain by making decisions earlier and removing needless noise. I learned this after a spring rush when we ran six Saturdays in eight weeks and morale started to crack.

During that stretch, I began posting the next day’s plan before the end of each shift. It was not perfect, but it gave people a better chance to plan rides, meals, and child care. I also stopped calling every small issue an emergency. If everything is urgent, people stop believing the leader.

I try to absorb some uncertainty before it reaches the floor. That does not mean hiding bad news. It means I sort out what is real, what is rumor, and what decision has already been made before I interrupt 42 people trying to do their jobs. Teams can handle hard news better than scattered half-news.

One practical habit helped more than any workshop I attended. Before I leave, I write three lines for the next shift: what changed, what still needs watching, and who already knows. It takes less than five minutes, and it has saved hours of confusion. Small systems protect tired people.

I Measure Leadership by What Happens When I Step Away

The real test of my leadership is not how busy I look during a crisis. It is what happens on a normal Thursday when I am at a vendor meeting and the crew has to make decisions without me. If every question has to climb back to my desk, I have trained people to wait instead of think. That is a fragile way to run a team.

I give people room before they feel fully ready. A lead might own the morning huddle for two weeks while I stand nearby and speak only if safety or quality is at risk. Another person might handle the first call to maintenance or talk through a staffing gap with a peer. The point is to build judgment in small, recoverable moments.

I also tell people which decisions are theirs. If a line lead can move two people between packing tables without asking me, I say that clearly. If overtime approval has to stay with management because it affects payroll and fairness, I say that too. Authority should not be a guessing game.

Successful leadership has never felt flashy to me. It feels like fewer surprises, better handoffs, cleaner arguments, and people willing to tell me the truth before a problem becomes expensive. I still make mistakes, especially when pressure piles up and I move too fast. But I have seen teams grow stronger when I slow down, speak plainly, keep promises, and give people enough room to become dependable without having to become someone else.