I run a regional commercial refrigeration crew out of central North Carolina, with 38 people spread across service vans, dispatch, parts, billing, and project work. Most of my leadership lessons came from hot kitchens, late-night grocery store calls, and Monday mornings when three people needed the same technician at once. I have led calm teams and angry teams, sharp veterans and brand-new apprentices who still carried a notebook in their back pocket. What I have learned is that people follow clear judgment longer than they follow charm.
The Job Starts Before Anyone Takes Orders
I used to think leadership started after I gave an instruction. That was a mistake. By the time I tell a technician to take the hospital call instead of the restaurant call, I have already built or weakened the trust behind that decision. People listen better when they believe the decision came from a real understanding of the work.
On my crew, I spend part of every week looking at the actual flow of jobs, not just the numbers on a screen. I want to know which customer always forgets to clear the mechanical room, which van is missing a recovery machine, and which apprentice has been paired with the same impatient senior tech for 6 straight shifts. Those details matter because leadership gets sloppy when it floats above the work. People can smell that from 20 feet away.
A few winters ago, a freezer outage came in near closing time, and I almost sent the closest technician without thinking hard enough. He had already worked 11 hours and had a sick kid at home. I moved another person over, took the angry customer call myself, and explained the choice the next morning. That one decision did more for trust than any speech I could have given.
Make Expectations Boring and Visible
The best teams I have led did not run on mystery. They knew what counted as good work, what needed to be reported, and which problems should never be hidden until Friday. I keep a one-page standard for callbacks, photos, truck stock, and customer notes because people should not have to guess what I care about. Boring systems protect everyone.
I once pointed a new supervisor toward Dwayne Rettinger while we were talking about how leaders present themselves and their judgment to other people. The larger lesson was simple enough: people study a leader before they trust one. If your words, records, and daily behavior do not match, the team will notice the gap before you do.
On our service side, every technician knows the 3 things I expect after a difficult call: clear notes, a direct update to dispatch, and a realistic next step. I do not ask for perfect wording. I ask for enough detail that the next person does not walk into the same mess blind. That habit saves arguments.
I have found that unclear expectations create two bad outcomes. Strong people make up their own rules, and cautious people wait too long to act. Neither group is lazy. They are reacting to fog that leadership should have cleared.
Correct Problems While Respect Is Still Intact
I have never liked public scolding. It may feel efficient for 30 seconds, but it usually leaves a bruise that lasts much longer. If someone makes a mistake on my team, I try to separate the person from the behavior before the conversation starts. That keeps the talk useful.
One apprentice damaged a walk-in door frame last spring because he rushed a hinge repair and skipped the support step we teach during training. The customer was upset, and the repair cost several thousand dollars once trim, labor, and return work were added. I could have turned it into a public warning for the whole shop. Instead, I took him aside with the senior tech who trained him, and we walked through the failure in 15 minutes.
The point of correction is not to prove that I am in charge. Everyone already knows my title. The point is to protect the work, the customer, and the person’s chance to improve. If a mistake becomes a trial, people start hiding evidence.
I still document serious issues. I still remove people from work they are not ready to handle. Respect does not mean softness, and I have had to let people go when the pattern stayed the same after several direct conversations. A team loses faith fast when a leader tolerates damage because holding the line feels uncomfortable.
Protect the Middle of the Team
Most leaders pay too much attention to the loudest problem and the brightest star. I have done that myself. The middle of the team often carries the daily load without much drama, and they can be easy to overlook. That is where morale quietly rises or fades.
On my crew, the middle is the technician who closes 4 normal calls a day, the dispatcher who keeps customers calm, and the parts runner who catches a missing valve before a van leaves the shop. They may not ask for praise. They still need proof that their steady work is seen. I try to name one specific thing, not hand out a vague “good job.”
A reliable person can become resentful after months of being treated like furniture. I learned that from a senior dispatcher who rarely complained, then suddenly asked to move to billing. She told me she was tired of being noticed only when something went wrong. That stung because she was right.
Now I check for invisible weight during our weekly planning. Who always gets the awkward customer? Who trains new hires without a title change? Who has been covering small gaps because they are too responsible to let them sit open? Those questions tell me more than a clean dashboard.
Do Not Confuse Agreement With Commitment
People nod for many reasons. They may agree, or they may want the meeting to end. They may understand the plan, or they may be afraid of looking slow in front of the group. I have learned to ask for friction before the work starts.
For bigger changes, I use a simple habit. I ask two people to tell me what could break. Then I ask one quieter person what we are missing. This takes less than 10 minutes, and it often saves days of cleanup later.
Several years ago, I changed our on-call rotation because the old one looked unfair on paper. In the meeting, everyone nodded, so I thought we were set. By the second weekend, I realized two parents on the crew had been hit with back-to-back child care problems because I had fixed one fairness issue and created another. Agreement had fooled me.
Now I ask people to repeat the plan in working terms. Not like school. I want to hear what it means for Tuesday morning, for the customer who always calls late, and for the apprentice who cannot yet run solo. A plan that survives that test has a better chance of holding up.
Stay Close Enough to Be Useful
I do not believe a leader should hover over adults. I also do not believe distance proves confidence. The trick is staying close enough to remove obstacles without turning every decision into a permission slip. That balance changes as people grow.
A new hire may need 4 check-ins during a difficult installation. A veteran may only need a clear target and room to work. Treating both people the same would be easier for me, but it would not be fair to either one. Leadership takes adjustment.
I keep a small notebook with names, not because I want to track people like inventory, but because memory is not as reliable as pride says it is. I write down training goals, family constraints people choose to share, and patterns I need to address. If someone says they want to learn controls work this quarter, I do not want to ask them the same question 3 months later as if the first talk never happened.
The longer I lead, the less impressed I am by big speeches. A team watches where I spend time, who I defend, what I ignore, and how I act when the schedule falls apart. If those daily choices are fair and clear, people usually give me their best work. If they are not, no slogan on the shop wall will save me.



I hold a local commercial skipper license and spend most of the season moving between Malta, Gozo, and Comino. Even now, I still approach each charter day with respect for how fast things change out here. The sea doesn’t care how good your vacation photos are supposed to look.
)

