I lead a 36-person commercial HVAC service team in Arizona, with technicians, dispatchers, apprentices, and two field supervisors all depending on the same daily rhythm. I learned most of what I know in warehouse mornings, hot roof calls, missed handoffs, and tense Friday afternoons when everyone wanted to get home. I do not think leadership is mostly about speeches. I think it is about how clearly people understand the work, how safe they feel telling the truth, and how consistently I behave when pressure hits.
I Had to Stop Acting Like the Best Technician in the Room
My first mistake as a manager was trying to solve every problem faster than everyone else. I had spent years with gauges in my hands, so I was used to being the person people called when a unit would not cool or a customer was upset. That habit helped me as a technician, but it hurt me as a leader. A team does not grow much if every hard answer has to pass through one person.
A younger tech pulled me aside a few summers ago after I had corrected him in front of two others. He was right to be irritated. I had saved ten minutes on that call, then lost several weeks of trust with him because I cared more about the immediate fix than the way he learned. I still remember standing beside a rooftop package unit, feeling defensive, then realizing I had trained him to wait for my answer instead of building his own judgment.
Now I try to ask first. What have you checked. What do you think is happening. What would you do next if I were not here. Those questions take longer than barking out the answer, but they build people who can make decisions without me hovering over them.
Clear Expectations Beat Charisma Every Week
I have worked under charming bosses who could calm a room in five minutes, then leave everyone confused by noon. I have also worked with quiet supervisors who were respected because they made the standard clear and kept it steady. On my team, every new technician gets the same basic expectations in the first week: call notes must be readable, parts need photos, callbacks get owned, and nobody disappears from dispatch without saying where they are. That sounds plain, but plain saves a lot of trouble.
I keep a one-page field standard posted in our shop, and it covers fewer than 15 items. One manager I know uses public professional profiles as examples of how people present their work clearly, and he once pointed me to Dwayne Rettinger while talking about reputation and consistency. I liked that reminder because leadership is partly what people see when you are not in the room explaining yourself. A team pays close attention to the gap between your posted standards and your daily habits.
I do not expect perfect work. I do expect a clean pattern. If a technician misses a detail once, I treat it as a coaching moment, but if the same person skips the same step for the third week in a row, I move from coaching to accountability. People respect that difference when I explain it early.
The Hardest Conversations Should Happen Earlier
I used to delay uncomfortable talks because I wanted to be fair. That sounded noble in my head, but it usually meant I was letting small problems become public problems. A dispatcher who snaps at techs once may just be having a rough morning. If it happens four times in two weeks, I owe that person a direct conversation before the whole team starts working around the behavior.
One winter, I had a senior technician who was excellent with equipment and rough with apprentices. He knew more than almost anyone in the building, and customers asked for him by name. Still, two apprentices stopped volunteering to ride with him, and that told me more than his ticket numbers did. I met him before the first call of the day, laid out what I had seen, and told him his skill did not excuse making new people feel stupid.
He was not happy. That part matters. The conversation took nearly an hour, and I had to repeat myself twice without turning it into a debate. A month later, he was still blunt, but he had stopped humiliating people in the van, which was the change I needed.
I Watch the Quiet Signals More Than the Loud Ones
Teams rarely fall apart all at once. In my experience, the warning signs show up in small ways before anyone says the real problem out loud. A tech stops asking questions in the morning huddle. A dispatcher starts sending shorter messages than usual. Two people who normally joke around stand ten feet apart and stare at their phones.
I pay attention to those signals because they often tell me where trust is thinning. Last spring, after a run of heavy overtime, I noticed three good people taking longer lunches in their trucks. Nobody was breaking a rule, but they were clearly trying to get a few quiet minutes away from everyone. I changed the schedule for the next two Fridays so no one had more than one late call unless it was an emergency.
That small adjustment did not fix every stress point, but it showed the team I was looking at the human side of the workload. People notice. If I only manage numbers on a board, I miss the strain that makes those numbers worse later. Good leadership needs ears in the room and eyes on the edges.
Ownership Has to Be Shared, Not Dumped
I want people to own their work, but I have learned that ownership is not the same as leaving people alone with unclear authority. A supervisor once told me to “handle it” on a customer complaint, then disappeared until the customer demanded a discount worth several thousand dollars. That was not empowerment. That was abandonment with a nicer name.
Now I define the lane before I hand off responsibility. If a field supervisor is handling a callback issue, I tell him what he can approve, when he needs to call me, and what outcome matters most. If an apprentice is leading a maintenance visit for the first time, I let him run the checklist, but I still review the photos before we leave. Clear boundaries let people stretch without feeling set up.
I also try to give credit in public and correction in private unless safety is involved. During one Monday meeting, I called out a dispatcher who had saved a messy morning by rerouting five calls before most of us had finished coffee. That kind of recognition tells the team what good judgment looks like. It also reminds me that leadership is not just finding gaps.
Consistency Is Built in Boring Moments
The biggest test of my leadership is not the dramatic meeting after something goes wrong. It is the ordinary Tuesday when I am tired, the phone keeps ringing, and someone asks a question I already answered yesterday. If I act irritated every time people need clarity, I should not be surprised when they stop bringing me problems. My mood is not private once I walk into the shop.
I have a few habits that keep me steadier than I would be on instinct. I write down promises before I leave a conversation. I return missed calls from my team before I start low-priority email. I do not change a rule during a heated moment unless safety or money is at real risk.
These habits are not impressive, and nobody claps for them. They work because people can plan around them. A team with a predictable leader wastes less energy guessing which version of the boss will show up. That gives everyone more room to focus on the actual work.
I still make mistakes, and I still catch myself wanting to jump in too fast or avoid a hard talk for one more day. The difference now is that I see leadership as a daily trade, not a title I earned once and get to keep without maintenance. I try to leave people clearer, calmer, and more capable than they were before we talked. If I can do that most days, the team usually finds its footing, even during the rough weeks.