How to Lead a Maintenance Team You Just Inherited

Key Takeaways

You inherited people as well as equipment, and the crew is the half that already holds a view about you.
Anything a new manager introduces gets read as a way of watching the team, so say what it is for while the crew is still deciding about you.
Consistency in public is what converts a sceptical crew. Persuasion in private moves one person at a time.

You inherited two things, and only one of them has an opinion about you. The equipment will accept whatever you decide. The crew has already watched somebody stand where you are standing, decide something, and leave. That is the real difficulty in leading a maintenance team you did not build. Your first instruction arrives in a room that has heard first instructions before, and the room is still running on what happened to those.

So the job is to become predictable in public, and to stay that way long past the point where it feels necessary.

Who actually decides whether your crew follows you?

One of your technicians decides it, and the odds are good that it is somebody without a title. Every crew has a person the others check with before they commit to anything. Find that person inside your first fortnight. A change that has their quiet agreement arrives in the department very differently from one that does not.

Three signals find them:

Who gets asked when a job is unfamiliar.
Whose word ends a disagreement on the floor.
Who the others wait for at the start of a job.

Take your first real change to that person privately, and ask what will break. You will get a straighter answer than the meeting would have given you. And the most credible person on the crew ends up inside the decision.

One thing to skip: sorting your crew by who looks comfortable with a phone. We have watched technicians who avoid computers use a demanding system daily, because the expectation was clear.

Why does anything new read as monitoring?

Because a record of the work is also a record of the worker, and nothing you have done yet tells the crew which half you intend to read. Technicians see a maintenance system as a big brother tool. They want to turn a wrench rather than type, and anything that logs what they did lands as a question about whether they are doing enough.

Two separate fears sit under that, and they take different answers. One is being watched. The other is being counted, because efficiency is a word technicians have heard shortly before somebody worked out that ten people could be eight.

Answer all three early, without waiting to be asked. A promise made in week one carries weight the same promise cannot carry after a technician has spent a fortnight wondering.

Get this wrong and the failure is quiet. The crew agrees in the room, works around it on the floor, and you spend your first year running a department on a picture of it that nobody has corrected.

What do you say before you ask them to change how they work?

Three things, in this order: what the change is for, what you will never use it for, and what it costs them. Then you do it yourself, first, in front of them. A manager who introduces a change and stays outside it has told the crew exactly how much it matters.

How a change lands depends more on the handling than on the change itself. Prosci puts projects with excellent change management at 94% for meeting or exceeding their objectives. Where it was handled poorly, the figure is 15%. Same work, different introduction.

Name the return honestly, and keep it small enough to be true. At Tricel, technicians ended up less reliant on second opinions and more confident in their own work. A head of engineering at a manufacturer running fifteen sites told us about a formal evaluation of tools their organization ran, where whether people would accept the thing was a named showstopper. If the crew will not take it up, the rest of the list stops mattering.

What does leading a maintenance team look like after the first month?

It looks like a routine rather than a personality. A maintenance director with thirty years on the floor described it to us as three plain things. The expectation is written into the job rather than announced once. A standing weekly meeting reviews open and closed work, in front of everybody. And the same line holds every week, until nobody in the room thinks of it as a policy any more.

The early weeks will not feel like progress, so it helps to know the far end. Holistic Industries put it plainly: every employee starts out calling the software the worst thing, and thirty days later the same people call it the best thing in the world. An opening position is a starting point rather than a verdict. Your job through that stretch is to be boring. Same answer, same question, every week.

What can leadership not fix here?

The clock. Trust arrives on the crew's schedule, and three months of steady behavior will never buy what two years of it buys. Some of what looks like resistance is a roster with no room left in it. A technician covering two people's work has no hours to give your change.

The equipment you inherited will still be there in a year, mostly unchanged. The crew will have made up its mind about you long before that. Leading a maintenance team you did not choose comes down to something smaller than most new managers expect. Pick one change. Tell them what it is for and what it will never be used for. Do it yourself first, then hold the same position on it every week, until it stops being your change and becomes the way the work runs.