You Can't Build a Preventive Maintenance Culture Without First Surviving the Pain of Change

One of the most challenging operational transformation projects I've led involved a maintenance department that was trapped in firefighting mode.

Every day looked the same.

A machine would fail.

Engineering would respond.

The issue would be fixed.

The team would move on to the next breakdown.

Repeat.

The engineering team spent the vast majority of its time performing reactive maintenance, with little or no preventive maintenance taking place.

This wasn't just my observation.

The issue had also been raised by the service teams of several major equipment suppliers, who highlighted that critical maintenance activities were consistently being missed.

The business challenge was clear:

Create structure within the maintenance function and transition from a reactive model to a preventive maintenance culture.

Where We Started

Together with the Engineering Manager, we began by creating visibility.

The first step was improving how reactive maintenance was captured.

We redesigned the process so every breakdown recorded meaningful information:

• What failed

• Where it failed

• Who responded

• How it was repaired

• Downtime incurred

• Duration of repair

• Repeating failure patterns

For the first time, we had reliable data instead of assumptions.

At the same time, we conducted a complete engineering stores stock-take.

This created visibility of:

✅ Spare parts availability

✅ Stock levels

✅ Consumable usage

✅ Inventory value

As a result, the CFO gained a clear understanding of the value of engineering assets and consumables across the business.

The Difficult Conversation

The most important part of the project wasn't technical.

It was organisational.

I had to explain to the Board that moving towards preventive maintenance would initially make things feel worse.

Many organisations want preventive maintenance but underestimate the transition period.

The reality was simple:

For a period of time, engineers would need to perform both reactive and preventive activities.

This would create:

• Longer lead times

• Reduced short-term engineering availability

• Higher workloads

• Temporary resource pressure

In other words, things would need to slow down before they improved.

Fortunately, the Board supported the approach.

Building the Framework

Before maintenance could become preventive, we needed a system.

I began by creating a complete asset register.

Every machine was identified and categorised according to operational criticality.

For the most critical assets, I then:

1. Reviewed manufacturer documentation

I extracted recommended maintenance activities and frequencies directly from machine manuals.

2. Engaged equipment manufacturers

I contacted suppliers directly to validate maintenance requirements and gather current best-practice recommendations.

This gave us a robust foundation for maintenance planning.

Making It Work

With the maintenance requirements defined, I developed a shared preventive maintenance schedule.

Initially, engineers were asked to complete preventive tasks immediately after attending reactive breakdowns on the same assets.

This allowed preventive maintenance activities to be embedded into existing workflows without requiring significant additional resources.

For several months, this became routine.

Over time something changed.

The engineering team stopped reacting.

They started planning.

Eventually, engineers were proactively visiting equipment specifically to perform preventive maintenance activities before failures occurred.

The Results

✔ Structured reactive maintenance reporting

✔ Full engineering asset visibility

✔ Engineering stores fully catalogued

✔ Preventive maintenance programme implemented

✔ Improved equipment reliability and OEE

✔ Increased engineering team engagement and morale

✔ Reduced dependence on firefighting activities

✔ Created the foundation for a future CMMS implementation

Perhaps the biggest success wasn't technical.

It was cultural.

The engineering team no longer felt like emergency responders rushing from crisis to crisis.

They became reliability specialists helping the business run more effectively.

The Lesson

Most organisations don't have a maintenance problem.

They have a systems problem.

Reactive maintenance is often the symptom, not the cause.

Until visibility, data, planning, asset criticality, and preventive scheduling are in place, teams will remain trapped in a cycle of breakdowns and firefighting.

The organisations that break that cycle don't start with software.

They start with structure.