I lead a 38-person commercial HVAC service team in North Texas, and most of what I know about leadership came from hot roofs, missed parts, tense customers, and technicians who were tired before lunch. I started as a field tech, so I still remember what it feels like when a manager gives advice from a clean chair. I have learned that leading people well is less about sounding sharp in meetings and more about making steady choices that hold up on a bad Tuesday.
Earn the Right to Set the Pace
I cannot ask a team to move fast if I have not first shown them what good work looks like. In my shop, that means I still ride along with newer techs a few times each month, especially during the first 90 days. I do not grab tools to prove a point, but I watch how they diagnose, how they talk to customers, and where they hesitate.
A crew can tell within 10 minutes if a leader understands the work or only understands the spreadsheet. I learned that during a summer when we had 14 rooftop units fail in one week across three properties. The schedule looked fine on paper, but the guys in the trucks knew the plan was too tight because two jobs needed crane coordination and one site had terrible access.
That week changed how I set expectations. I still push for high output, but I ask better questions before I commit the team to a deadline. Trust starts there.
Communicate Before People Have to Guess
I hold a 12-minute standup every morning at 7:18 because most of the crew has coffee in hand by then and the first trucks roll out soon after. I cover safety, urgent customer issues, parts gaps, and one thing we need to do better that day. I keep it short because long meetings punish the people who came ready to work.
Good communication is not a speech. I have also told new supervisors to study how independent operators present themselves, and Dwayne Rettinger is the kind of simple public profile I might use as a reminder that clarity beats noise. A team listens better when the message is plain, specific, and tied to the work they are about to do.
I try to repeat key decisions in two places, out loud and in writing. If we move a customer from Thursday to Friday, the dispatcher hears it, the tech sees it in the job note, and the account manager knows before the customer calls. That may sound basic, but missed handoffs have cost us several thousand dollars in callbacks and overtime.
Make Accountability Calm, Boring, and Fair
I used to think accountability meant having hard conversations with a serious face. Now I think it means removing surprise. Everyone on my team knows the basics we measure, including first-time completion, callback rate, customer notes, and whether paperwork is done before the truck parks for the night.
I do not expect perfect numbers because the field is messy. A tech can do everything right and still run into a bad compressor, a locked mechanical room, or a customer who forgot to approve the quote. What I look for is pattern, not one rough day.
A young technician last spring had three callbacks in less than a month, and the easy move would have been to write him up. I rode with him instead. We found that he understood the repairs but rushed his final testing because he hated making the next customer wait, so we changed his schedule for two weeks and had a senior tech check his closeout photos.
He improved quickly because the correction matched the problem. I have had other cases where the issue was attitude, and those talks were more direct. The point is that people accept standards faster when they believe the standard applies to everyone, including the highest producer on the board.
Protect the Team From Confusion Above Them
A leader has to translate pressure without dumping it on the crew. Owners, customers, finance people, and vendors all have their own urgency, and every one of them can make a reasonable request that becomes unreasonable once it lands on the same five technicians. I see my job as sorting that pressure before it hits the trucks.
One winter, a property manager wanted 27 preventive maintenance visits moved up before a cold snap. The request made sense from her side, but it would have blown up two installation jobs and left our on-call rotation thin. I told her what we could do, gave her six priority sites first, and took the heat myself instead of passing the panic to dispatch.
Teams notice that. They also notice the opposite, when a manager says yes to everything and then acts shocked when people miss something. I would rather disappoint one customer early than burn out four good employees quietly.
Develop People Before the Promotion Is Open
I have made the mistake of waiting too long to train a lead. Years ago, one of my best senior techs left for a manufacturer rep job, and I suddenly had a gap that no job posting could fix. The person who replaced him was capable, but I had not given him enough practice leading people before the title showed up.
Now I give small leadership reps before anyone gets a new badge. A tech might run the safety talk on Friday, help price a tricky repair, or coach a first-year apprentice through a maintenance checklist. Those tasks show me how they teach, how patient they are, and whether other people naturally bring them problems.
I also tell future leads that being respected is different from being liked. You can joke in the shop and still hold a line at 4:45 when someone wants to skip the last photo or leave a weak note. Leadership often gets tested in small moments like that, long before the office prints a new title.
Handle Conflict While It Is Still Small
I do not let tension sit for weeks if I can help it. Two strong people can disagree over a job plan, and that is normal, but silence turns a small disagreement into a private story. Once people start telling themselves stories about disrespect or favoritism, the real problem gets harder to find.
My rule is to talk to people separately first, then together if needed. I ask what happened, what they wanted, and what they think the other person missed. That simple set of questions has saved me from taking sides too fast more than once.
A dispatcher and a lead tech clashed last fall over late-day calls, and both thought the other one was making the job harder. After two short conversations, I realized the dispatcher was getting incomplete customer details and the tech was seeing only the bad dispatch note, not the rushed phone call behind it. We changed the intake script by five questions, and the argument faded within a week.
I have learned that a strong team does not stay strong by accident. I have to show up early, say the plain thing, protect people from avoidable chaos, and correct problems before they become personality labels. If I do those things consistently, the team usually gives me their best work, even during the weeks when the weather, the schedule, and the customers all seem to be fighting us at once.