You call it "resistant to technology." He calls it "I learned the hard way that pretty promises rarely deliver."
Every mature maintenance team has a character who's almost always misunderstood.
He's been with the company 15, 20, 30 years.
He's seen ERP rollouts fail.
He's seen expensive consultants leave without delivering.
He's seen promised software turn into spreadsheets in practice.
He's seen leadership get excited about a project that died in 6 months.
He's seen two or three of the company's "digital revolutions" in which nothing changed.
And then, when you walk into the meeting excited, presenting the next new platform, he gives you that look that's hard to read.
It's not hostile.
It's not aggressive.
It's not rude.
It's just... cautious.
And you leave the meeting thinking:
👉 "This guy is the team's bottleneck. How do we win him over?"
Here's a challenge:
👉 You don't need to beat him. You need to understand him.
Because the experienced skeptic isn't an enemy of transformation.
He's the professional who could speed it up the most — if you knew how to win him over.
Where veteran technicians' genuine skepticism comes from
Skepticism about technology is rarely about technology.
It's about track record.
And the track record of many veteran technicians includes things like:
- Inflated sales promises. "This will cut MTTR by 40% in 90 days." It didn't.
- Hit-and-run consultants. They show up excited, charge a lot, deliver a PowerPoint, and disappear when problems show up.
- Software imposed without listening. The tool came ready-made, without involving the people who would use it.
- Investment without upkeep. The technology was bought but nobody took care of it — and it died of neglect.
- Vendor switches with no transition. A new system was adopted and two years of data got thrown away.
- "It's going to revolutionize everything" talk that turned into "it's going to stay the way it always was."
Each of these episodes leaves an emotional scar.
And emotional scars shape the team's collective unconscious.
In other words: when the veteran skeptic looks at you presenting a new platform, he's not looking just at you. He's looking at everyone before you who made similar promises.
And that changes everything.
Because as long as you think you need to "overcome technical resistance," you're fighting the wrong person.
Your project's real adversary isn't in the room.
It's in the room's past.
What NLP teaches about reprogramming negative expectations
Neuro-Linguistic Programming is generous on a principle rarely discussed in management handbooks:
The human brain doesn't distinguish between a learned expectation and an absolute truth.
In other words: if the veteran lived through 3 or 4 projects that failed, his brain learned that transformation projects fail.
And it will protect its owner by projecting the same outcome onto your project — even if your project is excellent.
And here's the good news:
Learned negative expectations can be reprogrammed — but only through accumulated evidence, not speeches.
That means:
- A pretty presentation won't change his expectation.
- A comparison with a competitor won't change it.
- A technical argument won't change it.
- A promise of results won't change it.
What changes it is a consistent build-up of small, verifiable deliveries over time.
And then — only then — his brain starts to consider the possibility that this time could be different.
That doesn't happen in a week.
It doesn't happen in a month.
It happens in cycles of 3 to 6 months of consistency between what's said and what's done.
The mistakes that deepen skepticism (even with good intentions)
Many managers, trying to "break the resistance" of a skeptical team, make the problem worse — without realizing it. Three traps are very common:
- Promising too much at the start.
"In 3 months we'll be at the next level." If it doesn't happen, you've just added another negative memory to the team's emotional archive.
- Ignoring or publicly dismissing the skeptic.
Comments like "don't be obsolete" or "whoever doesn't want to evolve gets left behind" may silence the skeptic — but they contaminate the whole team with quiet discomfort.
- Pushing to change everything at once.
The more the manager tries to speed things up, the more the skeptic shuts down. Because he's seen that rush before — and knows where it usually ends.
The pattern is always the same: the more pressure the manager applies, the more the skeptic reinforces his own unconscious protective pattern.
And he doesn't do it out of ill will.
He does it out of accumulated experience of corporate survival.
How does Manusis4 approach adoption in traditional, skeptical industries?
Over the years, we've learned something important:
The longest-lasting rollouts aren't the ones that start with enthusiasm. They're the ones that start with humility.
And that's why Manusis4 developed an adoption approach that respects the collective emotional maturity of traditional industries.
In practice, that means:
- We don't promise a "revolution." We make small promises you can verify at 30, 60, and 90 days.
- We listen to the skeptic before any rollout. His questions usually reveal where previous projects failed.
- We start with a single tangible win. One specific pain, solved quickly, builds credibility. We don't announce "digital transformation" — we announce "solve X, first."
- We document every concrete delivery. Proof. No rhetoric. No fancy PowerPoint.
- We don't replace the history. We preserve it. No "throwing away everything that was there." We migrate with respect for what came before.
- Our team stays close for the first 6 months. It's not onboarding — it's long-term presence, to rebuild the trust other platforms broke.
In other words: Manusis4 doesn't sell technology as an argument.
It sells trust rebuilt over time.
And that's why, very often, the system's biggest champion inside the customer is precisely the veteran skeptic from day one.
Because once he's been won over by accumulated evidence, he becomes the most loyal guardian of adoption.
And by the way: if you have a veteran skeptic on your team today, know that he may be exactly the best gauge of the quality of the vendor you're evaluating. If the skeptic comes around, the platform passes the real test.
How to lead a technology-skeptical team — 5 moves that work
If you're facing skepticism on your team today, try these five moves:
- Publicly acknowledge the painful history — without blaming anyone.
Say: "I know we've had projects that didn't deliver. I'm not here to promise this one will be different. I'm here to prove it, week by week, by delivering small, verifiable things."
- Bring the skeptic into the process from the start.
Not as an adversary. As an advisor. His questions are the best list of requirements your vendor could ever receive.
- Radically shrink the scope of the first 90 days.
Pick ONE small, verifiable win, and deliver it with surgical precision. That's worth more than 100 corporate presentations.
- Don't confront the skepticism — let accumulated evidence dissolve it.
You won't convince him with words. You'll convince him with months of consistency between what was promised and what was delivered.
- Name and celebrate the first signs of change — with the skeptic himself as the protagonist.
When he acknowledges, even shyly, that something is working, make it a public milestone (with respect, without embarrassing him). That unlocks other silent skeptics.
Five moves.
No additional cost.
Time — a lot of time — as the investment.
But it's the only real path in traditionally skeptical industries.
This week's reprogramming
"The skeptic on my team isn't an obstacle. He's the guardian of a collective memory nobody had the courage to acknowledge. My role as a leader isn't to defeat him — it's to win him over, with accumulated evidence, over time. And when I win him over, he'll be my greatest ally."
Repeat this sentence before your next kickoff meeting.
Before your next corporate presentation to a traditional industry.
Before your next frustration with "that guy who doesn't want to change anything."
And watch your leadership in digital transformation gain a maturity almost no competitor has.
To wrap up
Traditional industries aren't behind.
Traditional industries got burned — by decades of poorly delivered promises.
And understanding that changes everything you can build with them.
Companies that learn to deal with skeptical teams with maturity:
- Win lasting adoption (not just signed contracts)
- Gain internal champions among the most respected professionals
- Build case stories that attract other traditional customers
- Stand out in markets where everyone sells similar promises
- Turn skepticism into commitment — the strongest kind of commitment there is
Because, deep down:
A converted skeptic is the most loyal customer there is.
And he only converts with evidence, presence, and time.
Next week, we continue Block 9 by opening a front that's still rarely discussed: the new professional profile Maintenance 4.0 demands — and what changes emotionally in the mind of someone who has to reinvent himself in the middle of a mature career.
It's going to be one of the most delicate editions of the series.
Until then.