Gestão que Destrava · #56 · August 5, 2026

What technical KPIs DON'T show about your team

Your KPIs look good. And yet something inside you says something isn't right.

There's a paradox that quietly torments many maintenance managers:

👉 The numbers look good.

👉 But the team's mood feels off.

MTBF went up.

MTTR went down.

Availability is high.

Backlog is under control.

Preventive work is up to date.

And still, if you look closely, you'll notice signs that aren't on any dashboard:

  • That shadow in a veteran technician's eyes
  • The silence at coffee break where there used to be conversation
  • The subtle coldness between two coworkers who were always close
  • The mysterious drop in creativity in meetings
  • The quiet rise in vacation requests
  • The small frictions that show up "for no reason"

And then you catch yourself thinking:

👉 "If everything looks good in the numbers, why do I feel something is out of line?"

That question deserves an honest answer.

And that's what we'll talk about today.

What technical KPIs were built to show

Before understanding what KPIs DON'T show, it's important to recognize what they do very well:

  • They show the operational health of the assets
  • They reveal failure and recovery patterns
  • They translate efficiency into comparable numbers
  • They flag objective technical deviations
  • They compare performance across plants, lines, and equipment families
  • They justify decisions and investments with evidence

That's a lot.

And it's essential.

An operation without technical KPIs is an operation flying blind.

But — and here's the turning point —

Technical KPIs were built to measure MACHINES. Not to measure PEOPLE.

And if one thing has become clear over the previous 55 editions of this series, it's this:

Maintenance isn't just about machines. It never was.

What NLP teaches about what numbers don't capture

Neuro-Linguistic Programming is generous on a point that rarely gets discussed:

The part of the human experience that most affects results is exactly the part that shows up least in objective data.

In other words: while KPIs show what happened, whoever leads needs to learn to see what's happening on the inside.

Things like:

  • The level of emotional safety to admit a doubt
  • The quiet trust between peers
  • The sense of belonging to the team's mission
  • The perception of fairness in how tasks are assigned
  • The invisible pride in work well done
  • The inner permission to propose a different idea
  • The collective energy at the start of a shift

None of these factors shows up in MTBF.

None shows up in MTTR.

None shows up in availability.

And yet they determine all of those KPIs.

Because the people doing the preventive work are human.

The people reading the alarm are human.

The people making decisions in critical seconds are human.

The people who pass knowledge on (or don't) are human.

And people don't fit in a spreadsheet.

The invisible signs that come before KPIs drop

Before any KPI starts to fall, there's a silent window — weeks or months — in which the team is already signaling the problem. It's just that nobody translates those signals into numbers.

Some of the most common:

  • A sudden drop in informal communication. Less talk at coffee, fewer jokes, more silence.
  • More "little absences." Not an epidemic. Just a frequency slightly above the historical average.
  • Fewer spontaneous suggestions. Nobody proposes an improvement "on their own." The routine becomes pure execution.
  • Distance between veterans and new hires. Knowledge stops flowing naturally.
  • Talk of "being tired" becoming more frequent. It's not complaining. It's a silent request for help.
  • More "silly frictions." Arguments over technical details that used to be resolved naturally.

If you spot 2 or 3 of these signs at the same time on your team TODAY, know this:

👉 In 3 to 6 months, your KPIs will start to drop.

It's not guesswork.

It's a behavioral pattern repeated in thousands of operations.

And when those KPIs drop, the manager has already lost months of possible response.

Because he only started looking when the number flashed red.

Where Manusis4 comes in — and where it STOPS

I want to share something important with you, openly:

Manusis4 is an increasingly powerful platform. It evolves with every release. It already delivers real-time KPIs, AI-driven predictive analytics, Digital Twin, IoT integration.

But not even Manusis4 replaces the human eye.

What Manusis4 does very well:

  • Automates tracking of dozens of technical KPIs
  • Correlates events the human mind couldn't
  • Predicts failures based on historical patterns
  • Builds dashboards that translate operations for leadership
  • Drastically shortens the time between data and decision
  • Frees the manager from the grunt work of gathering information

And precisely because it does all that so well, it gives the manager something precious back:

👉 Time and presence to notice what the data doesn't capture.

A manager who spends 80% of his time gathering technical data has no energy left to look at people.

A manager whose technology hands him the data ready to use can invest that time in conversations, in listening, in presence.

And that's where — in that presence — the invisible signs start to be read.

Technology applied well doesn't replace the human. It gives back room for the human to do what only humans can do.

Three human indicators you should start tracking

There's no official dashboard for this. But you can build your own "invisible panel" — in your head or in quick notes — by tracking three dimensions that technical KPIs ignore:

  1. Weekly emotional thermometer.

Every Friday, quietly, give your team's "mood" a score from 1 to 10. No rational analysis. Just feeling.

After 8 weeks, you'll have an emotional curve that reveals patterns no dashboard delivers.

  1. Map of informal interactions.

Notice who talks to whom at coffee, in the hallway, in the break room. Any subtle change in those patterns says a lot.

A pair who always had lunch together and stopped. Someone who became a silent island. These signs announce problems before any KPI does.

  1. Count of "spontaneous initiatives."

How many times, in the last week, did someone on your team propose something without being asked?

If the answer is "almost never," you already have a yellow flag — even if the technical KPIs are green.

Three human dimensions.

No sensor detects them.

All of them affect the KPIs.

This week's reprogramming

"My KPIs show me what happened to my assets. Only my presence shows me what's happening with my people. One without the other is half of leadership."

Repeat this sentence before your next results meeting.

Before your next dashboard review.

Before your next decision based only on numbers.

And allow yourself to also look at what doesn't fit in the chart.

To wrap up

Over the last 30 years, maintenance has evolved enormously in the quantity and quality of technical KPIs.

It was a necessary revolution.

But it created a quiet side effect:

👉 Many managers came to believe that if the numbers look good, everything is fine.

And it isn't.

Because the people who sustain those numbers carry experiences, pain, fears, dreams, frustrations, and potential that no sensor can read.

And that's where — in that invisible territory — the best managers make the difference.

Not because they ignore the data.

But because they use the data as a foundation, and their presence as the differentiator.

Because, deep down:

The best indicator of a team's health isn't on any dashboard.

It's in the eyes of whoever leads — if those eyes are trained to look.

Next week, we continue Phase 2 with a strong challenge for anyone in the asset management game:

👉 Asset management is people management in disguise.

We'll dive into how every asset management project is, deep down, a human project — and what that changes in the way you lead your next big initiative.

Until then.

Want to bring this to your maintenance?

Take the free 12-question diagnostic or see how the maintenance with AI mentoring works.

Take the diagnostic →See the mentoring