I run a 38-person facilities maintenance team that covers medical offices, warehouses, and two older retail centers in the Phoenix area. I started as a night-shift technician with a tool bag, a radio, and a habit of fixing things before anyone asked. Leading people has taught me that a team rarely fails because nobody knows the slogan on the wall. It fails because daily expectations are foggy, tension sits too long, and the person in charge talks more than they listen.
I Set the Standard Before I Ask for Speed
The first mistake I made as a supervisor was pushing for faster work before I had clearly defined good work. I had 11 technicians at the time, and I kept saying we needed cleaner tickets, quicker response times, and better handoffs. The problem was that each person had a different picture in their head. One person thought a closed ticket meant the equipment was running, while another thought it meant photos, notes, parts used, and a customer update were all finished.
Now I show the standard in plain detail. For a basic air handler call, I expect photos of the data plate, the failed part, the repair, and the final reading. I also expect a short note that another technician could understand three months later. That sounds small, but it removes a surprising amount of argument.
I learned this after a customer last spring questioned a repair that had been done correctly but documented poorly. The technician had solved the issue in under 40 minutes, yet the notes made it look like guesswork. We spent half a morning rebuilding the story from texts and memory. That was on me.
People move faster once they know what finished looks like. I do not expect anyone to read my mind, and I try not to punish someone for missing a rule I never made clear. Clear beats clever. If I want a standard followed, I write it down, repeat it in the field, and show it during real jobs instead of waiting for a mistake.
I Protect Trust in Small Moments
Trust on my team is built in moments that look ordinary from the outside. A technician calls at 6:20 in the morning because his truck will not start, and I either treat him like a problem or like a person trying to solve one. A dispatcher admits she double-booked a roof access appointment, and I either make the correction safe or make everyone hide the next mistake. People remember both versions.
I keep a short list of outside voices I respect, because leadership can get narrow when all my feedback comes from inside the same building. I once heard Dwayne Rettinger describe leadership as a daily record of how people experience your decisions. That stuck with me because it matched what I had seen in crews that trusted each other. One fair decision does not fix years of mixed signals, but one careless decision can make a good team quiet by lunch.
I do not confuse trust with softness. If a senior tech skips a lockout step, I address it the same day, even if he has saved us several thousand dollars in callbacks over the year. The difference is that I handle the issue directly instead of turning it into a public performance. Public shame is fast. It is also expensive.
A few years ago, I had a strong employee who rolled his eyes whenever a newer person asked a basic question. He was productive, and for too long I let that productivity cover the damage he was doing. After two apprentices asked to be moved off his jobs, I sat him down and gave him a plain choice. He could teach with patience, or he could stop being assigned helpers.
I Use Meetings Only When They Beat Silence
I have worked under managers who held meetings because Tuesday arrived. That taught me what not to do. My standing operations meeting is 25 minutes, and if I cannot name the decision or risk we need to discuss, I cancel it. The crew appreciates that more than any speech I could give.
Good meetings have friction in them. If everyone nods through the whole thing, I assume I either missed the real issue or trained people to keep quiet. Last winter, we had repeated delays on filter change routes across 14 buildings, and the easy answer was to blame the techs. In the meeting, a newer dispatcher finally said our route sheet had two buildings listed in the wrong order for afternoon access.
That one comment saved us hours every month. It also reminded me that the quietest person in the room may be closest to the bottleneck. I now ask specific questions instead of broad ones. “What will slow this down by Friday?” gets better answers than “Any concerns?”
I also watch who talks too much. Sometimes it is me. When I catch myself explaining a decision for the third time, I stop and ask one person who has not spoken what I am missing. The room changes when people see that silence is not the safest option.
I Coach the Person, Not Just the Role
Two people can hold the same job title and need completely different leadership. One technician may need more freedom because too much checking makes him second-guess work he already knows how to do. Another may need a written plan for the first 30 days because spoken instructions disappear under pressure. I try to match the support to the person in front of me.
I learned this with a dispatcher who was sharp with details but froze during angry customer calls. My first instinct was to give her scripts, which helped for about a week. Then I sat beside her for four calls and noticed she was trying to solve every problem before asking two basic questions. We practiced slowing the first minute of the call, and her confidence changed within a month.
Coaching also means knowing when a person is in the wrong seat. I once had a technician who struggled with solo troubleshooting but was excellent at inventory control. He could spot a missing motor starter in a crowded cage from 20 feet away. Moving him into parts coordination kept him employed, helped the field team, and stopped the daily cycle of frustration.
I do not pretend every story ends that well. Some people resist feedback no matter how clear or respectful I make it. When that happens, I document the pattern and make the next step clear. Kindness without follow-through turns into confusion.
I Make Accountability Boring and Predictable
The best accountability system I have used is not dramatic. Every Friday, I review open tickets, callbacks, safety notes, and customer complaints with the same format. Nobody wonders which numbers matter because they see the same four categories every week. Repetition lowers the temperature.
People handle correction better when the rules do not move around. If a callback happens because a part failed, we treat it differently from a callback caused by a skipped test. If a customer complaint is vague, I do not assume the employee is wrong. I ask for photos, notes, timestamps, and the customer’s exact concern before I decide what happened.
This protects the team from lazy blame. It also protects the business from wishful thinking. One summer, our repeat calls on ice machines jumped for 3 weeks, and the first theory was that the equipment was old. The ticket history showed that we had stopped cleaning one sensor during routine service because the step was missing from the checklist.
Once we fixed the checklist, the problem faded. Nobody needed a lecture about ownership. They needed a system that made the missed step visible. I still believe personal responsibility matters, but I have seen too many leaders use that phrase to avoid fixing broken processes.
I Let People See How Decisions Get Made
One reason teams lose faith in leadership is that decisions seem to appear from a locked room. I cannot share every detail about payroll, contracts, or private employee matters, but I can explain the thinking behind most choices. If we delay a truck replacement, I tell the lead techs what other costs came first. If we change the on-call rotation, I explain which complaints or gaps made the old version unfair.
I started doing this after a rough month when I reassigned weekend coverage without enough warning. The plan made sense on paper, but I had not explained the customer demand behind it or asked who had family commitments already set. Two people were angry, and they had reason to be. I fixed the schedule, then apologized in the next huddle.
That apology mattered more than I expected. A younger technician told me later that he had never heard a manager admit a planning mistake in front of 12 people. I did not enjoy doing it, but I liked the result. The team argued less about future changes because they knew I would explain the reason and own my part if I handled it badly.
Leading teams of people is not about having the loudest voice or the cleanest spreadsheet. I still carry a small notebook in my back pocket, and I still write down names next to promises I make during a shift. If I tell someone I will check on a tool order, ask about a schedule issue, or review a promotion path, I need to follow through. People do not need perfect leaders, but they do need leaders whose words survive the week.