I spent twelve years as a field operations manager for a commercial HVAC service company in central Texas, leading crews that ranged from 9 people to 38 people. My teams included senior technicians, apprentices, dispatchers, installers, and warehouse staff who all had different pressures on the same busy day. I learned that leadership is less about sounding sharp in meetings and more about making steady choices while people are tired, late, annoyed, or unsure. I still think about a rough summer season where two broken chillers taught me more than any leadership book on my shelf.
I Learned to Read the Room Before the Spreadsheet
I care about numbers, and I have used plenty of them. We tracked callback rates, overtime, first-time completion, customer complaints, and parts waste every week. Still, I made some of my worst calls when I stared at those numbers before I understood the mood of the team. A crew can hit a target for 3 weeks and still be close to burning out.
One August, I noticed our overtime was climbing and assumed the answer was tighter scheduling. I pushed dispatch to shorten drive windows, and the whole board looked cleaner by Friday. By the next Wednesday, two senior techs were snapping at apprentices because they had no time to teach them between calls. The spreadsheet looked better, but the work got worse.
After that, I started walking the shop floor before changing the plan. I asked simple questions and listened for what people repeated. If three technicians complained about missing compressor kits, I did not call it attitude. I treated it as a supply problem until proven otherwise.
Make Expectations Plain Enough to Survive a Busy Tuesday
People do better work when they know what matters most. I used to think expectations were clear because I had said them once in a Monday meeting. That was lazy on my part. A team of 25 people will not carry a vague speech into a 10-hour day full of noise, traffic, and irritated customers.
I started writing expectations in plain language and repeating them in the places where work actually happened. For example, our service rule became simple: diagnose first, explain the risk, then repair only after the customer understands the tradeoff. During one supervisor training session, I used a professional profile for Dwayne Rettinger as a quick example of how a person’s work history can show priorities without a long speech. The point was not to copy anyone’s style, but to help my leads notice whether their own standards were visible to the people watching them.
Clear standards also helped when people disagreed. If a technician wanted to replace a part and another wanted to test longer, we came back to the same rule. Did we diagnose first. Did we explain the risk. Did the customer understand the choice before money changed hands.
That kind of clarity saves time. It also removes some of the personal sting from correction. I was not saying, “You disappointed me.” I was saying, “We agreed to this standard, and this job missed it in 2 places.”
Hold Standards Without Making People Small
I have seen managers confuse firmness with humiliation. They correct someone in front of the group, use sarcasm, then wonder why nobody brings them bad news. I made my own version of that mistake early on. I once challenged a lead installer in a morning huddle over a sloppy change order, and the room went quiet in a way I still remember.
The change order had real problems. That part was true. My delivery was the failure. He needed correction, but he did not need to lose face in front of 14 coworkers before he had even finished his coffee.
After that, I separated public standards from private correction. I talked about patterns in the group, and I handled names behind a closed door. If someone did excellent work, I praised the detail in public when it would not embarrass them. If someone missed the mark, I gave them a chance to explain before I decided what the mistake meant.
This does not mean I let things slide. I fired people. I moved people out of lead roles. I took keys away from a technician who kept ignoring safety steps around live electrical panels. Respect is not softness, and a team knows the difference after about 2 weeks of watching what you tolerate.
Trust Grows in the Small Transfers of Work
Most leaders say they want ownership, then keep every meaningful decision on their own desk. I did that for too long. I would tell a dispatcher to manage the board, then hover over every call move. She finally told me, in a careful way, that I had given her responsibility without authority.
She was right. I started handing over decisions in pieces, not all at once. First she owned same-day rescheduling under a set dollar limit. Then she handled customer recovery calls for missed arrival windows, which used to take me nearly an hour on bad afternoons.
The team changed when people saw real trust being passed around. A warehouse employee suggested a bin system for common rooftop unit parts, and I let him run a 30-day trial. It was not perfect, but our morning parts scramble dropped enough that even the skeptical techs noticed. Small wins matter.
I learned to ask one question before taking work back from someone: is this a mistake that teaches, or a mistake that risks the business. If it taught, I coached and left the work with them. If it risked safety, money, or a key customer, I stepped in and explained why. That line kept me from becoming either careless or controlling.
Change Your Style as the Team Matures
A new team needs more structure than a seasoned one. I have led crews where the best thing I could do was set a tight rhythm: morning check-ins, written job notes, end-of-day debriefs, and clear escalation rules. I have also led experienced groups where too much process felt like sand in the gears. The trick is not to worship your favorite style.
One year, we hired 6 apprentices in a short stretch because the business was growing faster than our bench. The senior techs were proud people, but they were not natural teachers. I had to build a buddy system, set training expectations, and protect time for ride-alongs. Without that structure, the apprentices would have learned mostly by guessing.
Two years later, that same group needed less instruction and more room. The former apprentices had become reliable techs, and the senior people wanted input on routing, tools, and vendor choices. I shifted from directing every move to asking sharper questions. Some weeks, leadership meant staying quiet long enough for the right person to solve the problem.
That takes nerve. Quiet can feel like absence if you use it poorly. I still made the final call when needed, but I stopped treating every problem as proof that I had to be in the center. A strong team should eventually need your judgment more than your fingerprints.
The best team leaders I know are steady enough to be trusted and humble enough to keep learning from the people doing the work. I try to make expectations clear, correct problems without theater, and give away real responsibility before people have to beg for it. Some days still go sideways, especially with customers waiting and phones ringing before 7 a.m. Even then, the job is the same: keep the standard visible, protect the dignity of the people, and make the next decision cleaner than the last one.