It’s one of the hardest leadership jobs in the trades: introducing change to senior technicians who have already been through multiple changes.

Many of your senior people have already experienced software rollouts that made the day worse instead of better; process changes that added paperwork but didn’t solve anything; and management decisions that looked smart in a meeting, but fell apart in the field. 

And change fatigue is real. The Harvard Business Review notes that employees are experiencing far more organizational change than they did a few years ago, and their willingness to support it has declined.

So if your senior techs hesitate when you install a new tool or workflow—especially if it involves AI—their skepticism is likely born from experience. 

Before you pick a platform, pick their brains. 

Before you start searching for AI solutions, find out what your senior techs feel are the most urgent issues. They may even show you weaknesses you hadn’t seen before. 

Ask them what’s frustrating them most now and where the process seems to break down. Is scheduling unrealistic? Are job notes incomplete? What information do they need that they’re not getting? 

Experienced techs can quickly spot bad design. If you skip their knowledge and jump straight to rollout, the message they hear is that management already decided, and the techs’ job is to catch up. In that case, you’ll be lucky if they comply with the new system, let alone commit to it.

How to gain their support. 

Once you’ve determined which AI platform best fits your needs, go back to your senior people. Explain why you think it will improve your operations—especially the operations that they’re most involved in. Cite as many specific benefits as you can. 

Explain that you’re talking with them because you value their expertise. Acknowledge that they may have had bad experiences in the past. Be ready to answer as many questions as possible.

Most of all, let them know that you don’t intend to replace them; that in fact, you’re looking at an AI platform that you strongly believe will make their jobs easier. 

Get your senior people to buy in, and the rest of the business will move faster. If they disengage, even a good idea can sputter out. The biggest challenge is showing that their experience will truly improve the system.

Once you get it, let them test it. 

Try having a few senior people test a new workflow before a full rollout. Let them tell you where a new form is too long; where a mobile process breaks down on the jobsite, or where a dispatch update would actually help. It can also let them call out any gaps between what the office thinks is happening and what’s really happening in the field.

That kind of involvement does two things. It improves the system, and it tells the techs that their experience still matters. It also begins to acquaint them with the skills they’ll need to work with AI. 

McKinsey reports that when building digital and AI skills, adoption improves when learning is tied directly to the work itself, rather than treating training as a separate event.

That’s especially true with seasoned technicians. They’re not looking for lofty speeches about innovation. They want to see whether a change will actually help them do the job better.

Explain the problem in plain language

One of the fastest ways to lose credibility is to announce a new process without naming the problem it’s supposed to solve.

Make sure you state the change clearly, citing as many specific examples as you can. For example:

“We’re changing closeout because billing is waiting too long on missing notes.”

“We’re changing intake because technicians are walking into jobs without enough background information.”

“We’re adding this tool because customers are calling for updates we should already be sending.”

That kind of clarity ties a procedural change to an actual purpose rooted in your work. It also gives experienced techs something practical to evaluate. They may still disagree with the solution, but at least you’re addressing a real operational issue instead of selling some vague vision.

Training has to feel useful fast.

Seasoned people have a low tolerance for training that wastes time. They need learning that connects quickly with the job in front of them. Show them the practical benefits of the new system, such as:

• fewer callbacks

• tighter handoffs between departments

• less after-hours cleanup

• shorter back-and-forth with the office

• 
  

If the new tool requires ten extra taps but gives nothing back, they’ll spot that instantly.

The most effective version of training is usually short, practical, and reinforced by managers who can answer legitimate questions without getting defensive.

Managers set the tone more than the software does.

Seasoned techs may put up with an imperfect tool if they can fix it or work with it. They won’t, however, put up with a dismissive manager.

If a foreman, service manager, or owner automatically dismisses concerns as just “being negative,” resentment against the system will build. But if management listens to legitimate concerns, there’s a much better chance that it’ll be accepted.

Shout out the wins as soon as they happen. 

Once a process improves, point it out for the whole company to see. If a seasoned tech helped to improve said process, be sure they get credit for it. 

Company-wide announcements will reinforce the behavior you want to encourage—and demonstrate that the new system wasn’t just change for the sake of change. 

What are experienced techs really looking for?

Your long-time techs know the industry is changing. They’ve seen the growth of software, documentation, customer communication, and new operational systems. And to their credit, many of them have been adapting right along with it.

What they’re looking for most is to be asked their perspective, and for a reason to believe the next change will actually improve the workflow.

When leadership listens well, explains clearly, trains practically, and actually improves workflow, seasoned techs usually respond well.

The Graphite Lab builds AI products for trades businesses that want to make change easier to absorb by improving the work itself: cleaner handoffs, better information, tighter follow-through, and less avoidable friction between field and office.