I run field operations for a regional commercial HVAC service company outside Dallas, and most of what I know about leading teams came from long days with technicians, dispatchers, warehouse staff, and unhappy customers on the same phone line. I started with a crew of seven and now help manage a team of more than forty people across service, install, and support. I have made enough mistakes to know that leadership is less about having the loudest plan and more about building a team that can keep moving when the day goes sideways.
Earn Trust Before You Ask for Speed
The first mistake I made as a new manager was trying to speed up a team before I understood why it was slow. I saw late work orders, missed callbacks, and trucks returning with unused parts, so I assumed the problem was effort. After two weeks riding along with techs, I found out the real issue was a messy handoff between dispatch and the field. The crew was not lazy.
Trust starts with seeing the work close up. I still spend at least one half day each month with someone outside my normal circle, whether that is a junior technician, a parts runner, or the person handling warranty paperwork. People talk differently when they see you are willing to stand in the heat, listen during a rough call, or help carry a compressor down a narrow stairwell. That kind of time tells me more than a dashboard ever could.
I also learned to be careful with early promises. A team remembers the first three things you say you will fix, and they remember even more clearly if you let those things disappear. One spring, I told the installers I would clean up the tool checkout process, and it took me six weeks longer than I expected. I owned that delay in the next team meeting, which helped more than pretending everyone had forgotten.
Make Standards Clear Enough to Survive a Bad Day
Teams do better when standards are plain and repeatable. I do not mean a thick binder that nobody opens after orientation. I mean simple expectations that answer the daily questions people argue about, such as what counts as a finished job, who calls the customer, and when a supervisor needs to step in. In my shop, we reduced one recurring service dispute by writing a 9-line closeout checklist and putting it in the same place on every tablet.
I have borrowed ideas from other managers, shop owners, and service professionals because no single company has a monopoly on good habits. When I needed a clearer way to think about public accountability, I looked at business profiles and independent operators such as Dwayne Rettinger to see how people explain their work without burying the point. That reminded me that a standard is only useful if a busy person can understand it quickly. The same idea applies inside a team.
Clear standards also protect people from favoritism. If one technician gets corrected for a sloppy job note while another gets ignored for the same thing, the team will notice by Friday. I try to correct the behavior against the standard, not against my mood. That has saved me from more than one unfair conversation.
Deal With Conflict While It Is Still Small
I used to avoid conflict until it became impossible to avoid. That was comfortable for me and costly for the team. Two strong employees once spent most of a summer taking small shots at each other over parts staging, and I let it sit because both of them produced good numbers. By the time I stepped in, three other people had picked sides.
Now I handle friction sooner, usually in private and with the facts written down. I ask each person what happened, what they need to keep working well, and what they would change if the roles were reversed. That last question slows people down. It makes the conversation less like a trial and more like a repair.
Some conflict is useful. A dispatcher pushing back on a supervisor’s schedule can prevent a bad route, and a senior technician questioning a quote can save a customer several thousand dollars. I do not want a quiet team that agrees with every instruction. I want people who can disagree without making the work personal.
Give People Real Ownership, Then Stay Close Enough to Help
Delegation is often treated like handing off a task and walking away. That has never worked well for me. When I gave a young lead full control of a weekend install schedule without explaining budget limits, customer promises, or who could approve overtime, I set him up to guess under pressure. He worked hard and still got cornered by details I should have shared.
Now I use a tighter handoff. I explain the result I need, the limits he cannot cross, the people affected, and the time when I want a check-in. For a larger job, that might mean a 10-minute planning talk on Thursday, one text update Saturday morning, and a short review after the work is done. The person still owns the work, but they are not carrying it blind.
Ownership also means letting people solve problems in a style that is not mine. One of my best leads runs his morning huddle with a whiteboard, two colored markers, and a level of detail that would make me impatient. His crew loves it because they always know who has the lift gate, who has the recovery machine, and which customer needs a call before noon. My job is to judge the result, not force my fingerprints onto every method.
Build the Middle of the Team Before You Need It
A team can survive a weak day from one manager if the middle is strong. By the middle, I mean the informal leaders, senior people, steady administrators, and calm voices others already trust. On my team, one warehouse employee with 18 months of experience solved more field complaints than a manager with a title because he knew where every odd fitting was stored. People went to him because he answered without drama.
I try to develop those people before there is a promotion on the table. I will ask a steady technician to train one new hire on coil cleaning, or have a dispatcher lead the first 15 minutes of a routing review. Small assignments show who can teach, who can stay patient, and who enjoys responsibility once the attention fades. Titles matter less than repeated proof.
Pay attention to quiet competence. The loudest person in the room may be useful, but the person who prevents mistakes before anyone sees them is often the one holding the team together. I keep a running note in my phone with names, strengths, and small wins I do not want to forget during review season. That habit has helped me notice people before they start feeling invisible.
Measure What Matters Without Turning People Into Numbers
I use numbers every week, but I do not let them speak alone. Callback rate, billable hours, first-time fix rate, and customer notes all tell part of the story. A technician with lower output may be training two new hires, handling tougher calls, or cleaning up old problems from a rushed job. If I only read the report, I miss the truth behind it.
One winter, our install hours looked bad for nearly a month. The easy answer was to push harder, but the crew was dealing with older buildings, tight ceiling access, and a supplier delay that caused repeated parts runs. We changed the staging process and added a second pre-job check for commercial sites over a certain size. The numbers improved after the work got easier to do right.
Metrics should start better questions. I ask why a number moved, who was affected, and what the team already tried before I suggest a fix. That keeps me from acting like a spreadsheet is the whole business. It is only a map.
Leading teams of people has made me more patient than I was when I started, though I still have days when I talk too much or move too fast. The best results I have seen came from clear standards, early honesty, and enough time beside the work to know what people are really carrying. If I had to give one practical recommendation, I would tell any leader to spend one week listening closely before changing anything that affects the people doing the job.