Maintenance maturity: from firefighting to control

They have SAP. They have dashboards. They have planning meetings, KPI reviews, reliability programmes, predictive maintenance pilots.

And still, when you ask a simple question — are we actually executing the work we planned? — the answer is often unclear.

Not why work was missed. Whether it was truly executed in the first place.

That sounds like a basic question. In reality, many sites cannot answer it reliably.

Schedules live outside the maintenance system. Workorders get technically closed months later. KPI calculations depend on polluted backlog data. Different departments work from different versions of reality. Over time, the organisation quietly stops trusting its own numbers.

This is where most classical maintenance maturity models fail.

They measure whether capabilities exist:

• Do you have a CMMS?
• Do you track KPIs?
• Do you run reliability initiatives?
• Have you implemented predictive maintenance?

But they rarely measure something more important:

Does the organisation actually have operational control?

Because those are not the same thing.

A site can adopt advanced maintenance practices and still operate reactively every single day.

That gap — between capability adoption and operational control — is what real maturity in maintenance actually looks like.

And it explains why so many organisations invest heavily in "advanced" maintenance while still living in firefighting culture.

What classical maturity models actually measure

Most maturity models reward capability adoption.

Do you have a planner role? Do you measure plan attainment? Do you have reliability engineers? Have you implemented ISO 55000? Do you use predictive maintenance technologies? Have you completed backlog cleanup initiatives?

These are useful questions.

They are just not the right ones.

Because none of them tells you whether the operation is actually under control.

A site can answer "yes" to every one of those questions and still spend every day reacting to urgency.

The capabilities exist. The operational behaviour never changed.

The schedule exists, but the team executes outside it. The PM strategy was reviewed, but the same ineffective inspections continue for years. The predictive sensor flags a problem, the engineer creates a recommendation, and eight months later the bearing still fails because the execution loop never closed.

This is the difference between looking mature and being mature.

Most organisations are far better at adopting maintenance concepts than they are at operationally sustaining them.

A different definition of maturity

Real maintenance maturity is not the number of tools deployed.

It is the degree to which a site has verifiable operational control.

That means:

• work is identified from real signals instead of noise
• work is planned using trustworthy information
• schedules are realistic and connected to execution
• execution is captured honestly
• feedback loops actually improve future decisions

Where that operational loop holds, maturity is real.

Where it does not, maturity becomes theatre: dashboards without trust, KPIs without credibility, strategies without execution, and initiatives that slowly drift back into firefighting.

Most heavy asset sites are somewhere in the middle of that struggle.

Maintenance maturity as a series of broken loops

The path from firefighting to control is not really a checklist of capabilities.

It is a sequence of operational gaps being closed.

Most organisations break at multiple points in the loop simultaneously.

Stage 1 — KPI visibility

Can the organisation actually understand its own maintenance performance?

Not just see numbers on a dashboard — understand where they come from, challenge them, and trace them back to the records underneath.

At many sites, KPI definitions come from corporate systems nobody locally controls. Teams cannot easily re-filter the data, validate the assumptions, or explain why the numbers changed.

Eventually, trust disappears.

Deeper read: Why your KPI dashboard isn't making things better.

Stage 2 — Data trust

Even if KPIs exist, can the team trust the data feeding them?

Backlog pollution alone silently corrupts:

• overdue reporting
• MTTR
• plan attainment
• maintenance cost visibility
• PM compliance
• resource loading

Many sites already know their data is polluted. The dangerous part is that they continue using the numbers anyway.

Deeper read: Why are maintenance backlogs always polluted?

Stage 3 — Cause visibility

When planned work is not executed, does the organisation actually understand why?

Or does every review meeting produce the same explanations:

• production did not release
• materials were missing
• priorities changed
• too much urgent work

Surface-level explanations repeated every month are usually a sign that the real operational causes are still invisible.

Deeper read: Why execution is often the weakest link in the maintenance process.

Stage 4 — Process adherence

Can process improvements actually survive operational reality?

Many maintenance initiatives start with good intentions and disappear six months later.

Not because the team disagreed with the process. Because the underlying friction never changed.

If planners still spend hours chasing information, if engineers still work around disconnected systems, if supervisors still rely on side lists and phone calls, then the organisation quietly falls back into old behaviours.

Deeper read: Why isn't the maintenance process followed?

Stage 5 — Organisational alignment

Does management believe the process is being followed? And does the execution team agree?

At many sites, leadership and execution operate from completely different versions of reality.

Managers believe work is structured and controlled. The field experiences constant reprioritisation and operational instability.

The gap between those two perceptions becomes one of the biggest hidden barriers to improvement.

Deeper read: Why your maintenance schedule isn't driving execution.

Stage 6 — Daily operational control

At the final stage, the organisation becomes genuinely proactive.

Urgency still exists — but it is no longer the default operating mode.

The plan drives execution. Schedules are connected to reality. Teams can see emerging problems before they become crises. Engineers have enough feedback to improve the strategy continuously.

This is where maintenance starts becoming controlled instead of reactive.

Deeper read: What is firefighting culture in maintenance — and how do you stop it?

Why the stages compound

This is the part most maturity models completely miss.

Maintenance capabilities are not additive. They are dependent.

An advanced layer only works if the layers beneath it are stable.

Predictive maintenance only creates value if the organisation can respond to signals quickly and effectively. Reliability initiatives only work if the process actually holds operationally. PM optimisation only works if the underlying execution data is trustworthy. KPI dashboards only work if the records feeding them are credible.

You cannot build advanced maintenance on top of broken operational foundations.

And yet many organisations try.

That is why so many expensive initiatives quietly disappoint.

The technology itself often works perfectly. The operational system underneath it does not.

What real progression actually looks like

Real maintenance maturity is the gradual closing of operational gaps.

It is not about appearing more advanced. It is about becoming more controllable.

That progression usually looks something like this:

• Stage 1 closed: The organisation can trust and interrogate its own KPIs.
• Stage 2 closed: The underlying maintenance data becomes reliable enough to support real decisions.
• Stage 3 closed: Review meetings stop repeating the same vague explanations and start exposing actionable causes.
• Stage 4 closed: Process improvements hold because operational friction was removed instead of ignored.
• Stage 5 closed: Management and execution teams operate from the same operational picture.
• Stage 6 closed: The organisation becomes structurally proactive instead of structurally reactive.

Each closed stage enables the next.

Each unresolved stage quietly breaks the layers above it.

This is why maturity is not a checklist.

It is a sequence.

And the sequence cannot be skipped.