Have you ever stopped to think about why 70% of asset management projects fail?
If you've worked in asset management for a few years, you've probably seen this scene more than once:
A great project kicks off.
Consultants hired.
Platform chosen.
Methodology defined.
Schedule approved.
An upbeat kickoff.
Everyone leaves the first meeting with that feeling that "this time it's going to work."
Six months later, the project is running at half strength.
A year later, it's become "that project we keep trying."
Two years later, it's become "that expensive consulting job we paid for and got nothing."
And nobody can really explain what happened.
The software was good.
The methodology was solid.
Leadership sponsored it.
The processes were designed.
But the project died.
And then comes the question almost nobody has the courage to answer honestly:
👉 What was missing?
The technical illusion that sabotages asset management projects
The most comfortable — and most wrong — answer is always the same:
"We needed more robust technology."
"We needed a clearer process."
"We needed a more sophisticated methodology."
"We needed more complete data."
And the industry keeps going around this loop: buying more technology, more process, more methodology, more data.
And projects keep dying.
Not because the technology is bad.
Not because the process is flawed.
Not because the methodology is imperfect.
But because the most important layer was left out of scope:
👉 The people who have to carry all of it out, every day, consistently.
Every asset management project is, deep down, a human transformation project disguised as a technical project.
And like every human transformation, it requires:
- Reprogramming beliefs
- Reframing professional identity
- Retraining collective habits
- Rebuilding institutional trust
- Restoring a sense of belonging
- Emotional support in moments of doubt
None of these items come in the consulting package.
None of them is a software deliverable.
And that's why the industry keeps switching vendors, thinking the problem was the last one.
What NLP teaches about projects that ignore the human layer
Neuro-Linguistic Programming is tough on this illusion:
Every human system, when forced to change without emotional care, snaps back to the previous pattern with a force proportional to the change attempted.
In other words: the more ambitious the project technically, the greater the team's unconscious resistance — if that team isn't taken care of along the way.
And that resistance doesn't show up as open sabotage.
It shows up as:
- "I forgot to log it."
- "I didn't have time to update it."
- "The system was down."
- "Nobody told me."
- "I'll do it later."
- "We've always done it this way, and it worked."
- "There must be some error in the report."
Each of these phrases is actually a silent cry for emotional help.
And whoever leads has to learn to decode them.
Because as long as the manager thinks he's dealing with "unwillingness," he's treating the symptom.
When he understands he's dealing with collective emotional misalignment, he starts treating the cause.
5 signs your asset project has become a "people-in-crisis project in disguise"
If you recognize 3 or more of these signs in your current project, it's time to change your approach:
- The project leadership is exhausted. Pulling alone. Nobody really "embraces" it.
- Real adoption is far below declared adoption. On paper, everyone participates. In practice, few are consistent.
- The trainings are "really good," and the meetings that follow show nothing has changed. Content consumed, behavior untouched.
- The relationship with vendors has turned into mutual blame. "You don't deliver." "You don't use it." The honeymoon turned into a fight.
- Leadership starts asking "where are we with this project?" And nobody has a clear answer.
These 5 signs are universal.
They show up all over the world.
In giant companies and mid-sized ones.
In ISO 55000, RCM, CMMS rollout, and digital transformation projects.
The pattern is always the same:
👉 When the asset project starts to hurt, it's a sign the human layer needs urgent attention.
Not more technology.
Where does Manusis4 fit in this more mature understanding?
Here I want to share something important with you — and different from what most platforms say publicly.
Manusis4 is powerful technology. But we've never believed technology alone changes culture.
What Manusis4 does very well — and why it stands out — is create reliable infrastructure so human change can happen safely:
- It reduces day-to-day friction (fewer reasons to "forget" to log)
- It simplifies what used to be complicated (fewer excuses not to use it)
- It translates data into language the team understands (less anxiety about "I don't know how to use it")
- It evolves with the team's maturity (it doesn't force leaps the culture can't sustain yet)
- It gives the leader time back to take care of what only the leader can take care of: people
And it's precisely that combination — reliable technology + present leadership — that makes asset management projects really take off.
Because when the technology foundation is solid, the manager can invest his energy where it makes the biggest difference:
👉 In leading the human side of change.
And that's when projects stop being "just another expensive consulting job" and become real transformation.
The 4 moves that save asset management projects
If you're leading a project today that's "kind of stalled," try these four moves before changing anything technical:
- Publicly acknowledge the built-up frustration.
Name the pain. That frees the team from the burden of pretending everything's fine.
- Restart the project with the people — not the deliverables.
Spend a whole month just on conversations. Ask what hurts. Listen without getting defensive.
- Drastically cut the scope for 90 days.
Pick a single new practice. Nurture it until it becomes a habit. Only then move forward.
- Publicly celebrate the smallest visible progress.
Every gesture of change has to be reinforced. The old culture settles in silently; the new one has to be applauded out loud.
Four simple moves.
All free.
All available to any manager, today.
And all with the potential to turn around projects that looked lost.
This week's reprogramming
"My asset project isn't stuck for lack of technology. It's stuck because part of my team hasn't yet been convinced — in their hearts — that this change is worth it. And my job is to win that part over before I demand anything from it."
Repeat this sentence before your next project meeting.
Before the next push for adoption.
Before the next decision to "turn up the pressure."
And notice how your leadership becomes, at the same time, firmer and more effective.
To wrap up
The great quiet revolution in maintenance over the next 10 years won't come from technology.
It will come from the mature understanding that asset management, at the end of the day, is people management — just disguised as machine management.
Whoever understands this first:
- Will attract the best people
- Will retain the most experienced ones
- Will develop the next leaders
- Will build a lasting culture
- Will turn the maintenance department into a reference within the company
- Will reap results competitors will try to copy for years
Because, deep down:
Important assets, you buy.
An asset management culture, you build — person by person, conversation by conversation, year after year.
And that's what separates the projects that die from the ones that make history.
Next week, we close Block 8 and open the way to Block 9 — where we'll dive into digital transformation with soul: IoT, Digital Twin, AI applied to maintenance, and the emotional challenge of adopting all of it without losing what's human in the operation.
It's going to be a rich shift.
Until then.