What You're Protecting

Guys don't follow a title. They follow what they see somebody do, day after day, especially on the days nobody's checking.

Protect the trust, not the schedule

Most managers believe that managing a schedule is their primary duty, but not me. Yes, managing the schedule is extremely important, but there are other things that if you don’t put first, your schedule management would be even more difficult. My role as a manager is first to protect three things: trust, morale, and the quality of the work. And those three aren't separate. They feed each other.

Every time I keep my word, back a technician up, or handle a bad moment the right way, I'm laying a plank in the bridge between me and the team. It takes months if not years to build and unfortunately one bad day to burn. But once that bridge is strong, something starts to shift. The guys start protecting the schedule themselves. They push to finish a job because they don't want to let the team down or to let themselves down, not because I'm standing over them. They flag a problem early because they trust I'll back them instead of blaming them. I stop being the only one who cares if the unit goes out on time.

Most supervisors chase the schedule and lose the trust doing it. I try to protect the trust, and the schedule follows.

Quality works the same way. It doesn't come from a checklist, and it doesn't happen at the end when the last guy checks the job and passes or fails it. It starts with the first technician who touches the unit and decides to do his part right, and it carries from one set of hands to the next until the job rolls out the door. That only happens with a crew that's steady, trusts each other, and trusts me. Quality becomes reputation, and reputation is pretty much free marketing. It's why a customer calls us again and again instead of shopping around, and why he tells someone else to call us too. Crack the trust and the quality goes right along with it.

Show it before I say it

I can try to talk a team into caring about the work but it’s always best that I just show them. If I want accountability, I should be the first one accountable. If I want craftsmanship, they have to watch me demand it of myself first. Guys don't follow a title. They follow what they see somebody do, day after day, especially on the days nobody's checking. Every standard I want on the floor has to already live in how I work.

I always do my best to plan ahead of time and to keep things organized. Ten minutes before the end of the shift, everybody stops work and cleans up the area he worked in. Tools put away and trash out of the bay. Tomorrow starts fresh on a clean slate even though the job is not even half done. We set tomorrow up for success. This also allows the job to be handed off to anyone at any time if it needs to be. Physical organization is mental organization.

As for myself, ten minutes before I leave, I always come up with a game plan for tomorrow. I review tomorrow's schedule again and take notes on who, what, why, where, how, and any anticipated challenges or things that could be a problem. I try to think of what parts will be needed or who may need to work with whom and what we need to do to achieve the common goals.

The frustration shows up at the finish line

The real test in my opinion is when the guys are frustrated, and this is where most supervisors lose sight of the picture. A technician having a bad day isn't a discipline problem. It is a human one.

For me, the worst of it shows up at the end of the job. A unit fails final QC and the work has to be redone. The test reports didn't get filled out, and the completed work order comes back to him with a list of what he needs to correct or redo. Nobody likes going backward on a job he thought was finished.

Get him off the floor first

When a guy gets mad, my first move isn't to talk, even though it's always tempting to assert my authority. It's to get him away from the audience. If the crew is watching, he's not arguing with me anymore at that point. He's putting on a show for everyone, and nobody backs down in front of a crowd. So I pull him aside: "Hey, c'mon, let's go outside and have a one-on-one." And nine times out of ten, when we're away from the floor and the other guys, the temperature drops on its own. At that point, the environment is more conducive for an adult conversation.

Then listen

Once we're one-on-one, I do my best to listen. The initial instinct is to seek first to be understood, but I try to understand the "why" behind the frustration. Most of the time he doesn't need me to fix anything. He just needs to be heard.

If I overreact, a bad moment turns into a bigger one, and the whole crew learns that venting gets punished instead of understood. Staying steady isn't passive. It's the discipline.

I had a tech get mad at me for making him wipe his anti-seize handprints off the shocks and brake chambers. It's a trailer, he said. It's already dirty. Nobody's going to look under there. I was being too strict, and some things don't need to be that serious.

I didn't argue with him. I listened until he was done. Then I gave him one line: "We've done such a good job all the way to the finish line. We're not going to let the last five percent be the reason somebody says: you guys did great, but…" Today may be anti-seize on the brake chambers but if the standard is not protected, tomorrow there may be anti-seize on the steering wheel or the door handle of the cab.

Hold the line without making it personal

Listening to him didn't mean lowering the standard. Staying calm doesn't mean there's no line. If it turns disrespectful, I respond firm, not reactive. But I'm far from perfect and I'd be lying if I said there weren't times when I let my ego go to my head, which always came with a price of bruised trust.

The skill is separating the business from the personal, out loud. I tell him straight: this is nothing personal, but I understand it's not just nothing to you. I know it's affecting you right now. That holds the standard and tells him I see him in the same breath. It's harder than laying down the law, and it's the difference between a crew that respects me and one that only complies.

When the bad day becomes a pattern

One bad day is human. The same guy having a bad day every week is something else, and it calls for a different response. That's when I have to make it formal. I take him out of his environment and into the boardroom, or whatever formal setting we have, for a sit-down. The room sets the tone before anyone says a word. He understands his actions brought him there, and that clears the way for a direct conversation and clear expectations. For some guys, that's enough. For others, the pattern comes back, and that's where a performance improvement plan or a formal reprimand comes in. It's not punishment for its own sake. It's protecting the same standard the crew's trust is built on.

What it adds up to

None of this happens in big speeches. It happens in small moments: a tense exchange taken off the floor, a bad day absorbed instead of escalated, a pattern addressed before it spreads, a standard held by example instead of a lecture.

That's the whole job, every day: quietly protecting the thing that makes the shop worth working at and the team worth joining.