Key Takeaways
- Teams stay reactive long after they believe in preventive work, because a reactive operation drops the planned job first, rewards the rescue, and makes efficiency look like a threat to jobs.
- Effort spent against that design has to be spent again every shift. The way out changes what gets written down and what earns the credit.
- Capture comes before scheduling. A preventive task that slips has to stay visible on the same list as the breakdowns, or it slips for good.
Nobody reading this needs convincing that preventive maintenance beats reactive maintenance. Almost every maintenance team already believes it, and a great many are still reactive. The reactive vs preventive maintenance argument was settled years ago, and the teams stuck on the wrong side of it lost to a system rather than to a shortage of effort. The planned job is the only work nobody shouts for, so it gives way first, and every job that gives way makes the next breakdown more likely. You get out by changing what the operation records and what it rewards. Asking people to try harder asks them to beat that system by hand, every shift, for as long as they work there.
What is the difference between reactive and preventive maintenance?
Preventive maintenance is work done before a failure, at a time you choose, with the parts and the people ready. Reactive maintenance is the same work done after the failure, at a time the machine chose. The task is often identical. Everything around the task changes, and those conditions decide what the job costs everyone involved.
The comparison we come back to most is the car. Changing the oil on a Saturday morning takes a couple of hours, with the tools laid out and a coffee going on the step. The car breaking down on the way to a wedding, on the hard shoulder with nothing in the boot, is the identical problem met in the worst conditions available. Same task, completely different experience.
On a plant floor the gap is concrete. A planned bearing change happens between runs, with the part on the shelf and the right person on shift. The unplanned one happens mid-run, with production waiting, the part on an overnight courier, and whoever was nearest the phone doing the job.
That difference has a price in lost output and emergency labor, and a cost no invoice records, carried home by whoever took the call. Both are real. Neither explains why teams who know all this stay where they are.
Why do maintenance teams stay reactive when they already believe in preventive work?
A reactive operation is stable, and a stable system outlasts good intentions. It runs as a loop that feeds itself, kept turning by three mechanisms. Each is a sensible response to how the operation works, which is why the loop holds in teams full of capable people.
- The planned job gives way first. A breakdown arrives with a supervisor, a stopped line and a deadline. A preventive task arrives alone. When there are more jobs than hours, the one without a voice gets pushed, and the skipped inspection is often the one that would have caught next month's failure.
- The rescue is what gets noticed. The technician who brings a stopped line back at the end of a bad shift is the hero of the day, and being that person feels good. The technician whose machines never stop is invisible, because nothing happened. A reactive team learns quickly which kind of work earns the thanks.
- Efficiency reads as a threat. From the floor, a plan to get ahead of the work can sound like a plan to need fewer people doing it. A crew that suspects the savings will be taken in heads has every reason to keep the work looking as big as it is.
Why doesn't telling people to try harder work?
Effort is spent one shift at a time, and the system refills overnight. A push to protect the preventive schedule lasts as long as somebody is personally defending it, and the first bad week undoes it. Every choice between the loud job and the quiet one is made again the next morning, by tired people, against the same incentives.
The usual responses are familiar: a PM week, a calendar on the wall, a talk at the morning meeting, an extra Saturday to clear the overdue inspections. Each one asks the team to keep picking the unshouted job over the shouted one, and a firefighting team has already heard "get more organized" more often than any other advice. Every push that collapses costs you something too. The crew learns the planned week is the first thing cancelled, and you start to wonder whether the crew is the problem, which is the wrong conclusion drawn from accurate evidence.
We've watched this across a lot of teams. When doing and logging the planned work is left to discretion, it loses, even in teams that care. It survives where management treats recording the work as part of the job, on the worst day as much as the best.
Read the resistance honestly, too. A technician who drifts toward the breakdown is protecting something real: the standing that comes from getting the line back, and a job that looks safer in a busy department than a calm one. You can't train someone out of a choice that is working for them. You can change what the choice gets them.
How do you switch from reactive to preventive maintenance?
Change two things about how the operation runs. First, capture every job, planned and unplanned, in one record where a skipped preventive task stays visible. Second, take away the threat that makes the team prefer firefighting. Scheduling comes after both, because a schedule nobody records against is a wish list with dates on it.
In most reactive operations a missed PM leaves no trace. The breakdown gets a work order, or at least a phone call and a memory. The inspection that didn't happen gets nothing, so there's nothing to see, nothing to count, and no moment where anyone has to explain it. A preventive schedule disappears that way without anyone ever deciding to abandon it.
Put the planned job and the breakdown in the same record and the slip becomes an item with a date against it. A run of slips becomes a pattern a manager can raise. The work that used to vanish now competes in the open.
This is the part of the shift the software industry tends to skip. Preventive maintenance tools are sold on their calendars and triggers, and the calendar is the easy half. The record is the input and the schedule is the output, and the output is only ever as good as what goes in. A schedule generating tasks into a system the team doesn't use produces a tidy list of work that never happened. Escaping reactive maintenance is an adoption problem before it is a scheduling one.
When you look at preventive maintenance software, ask one question before the vendor shows you the calendar: what happens to a preventive work order that doesn't get done this week? Does it stay on the same list as the breakdowns, overdue and visible, or does the next one simply generate on schedule as if the last one had happened? The answer tells you whether the tool was built for teams that already run a clean schedule, or for the team you are actually running.
How do you take away the threat that keeps a team reactive?
Show, with evidence, that getting ahead of the work protects the team, and change what gets recognised so the quiet machine earns the credit the rescue used to. The fear is rational, so the answer has to be concrete. A reassurance fades the first time someone on the crew does the arithmetic.
Say plainly what the recovered hours are for. In a reactive department they go to the backlog nobody has reached, the jobs waiting since spring, and fewer calls after the shift has ended. That is the honest trade on offer, and it's a better one than the crew expects.
Then let them see the record doing it. A maintenance director with thirty years on the floor described to us how work order volume made the case upstairs. It showed one manager carrying far more than one person's load, and it won the budget for two more technicians. The numbers a crew fears will count them out can be the numbers that bring more people in.
The rescue identity needs somewhere better to go. The technician who is brilliant at diagnosing a stopped machine is the best person to decide what the preventive check on that machine should look for. Handing them that job moves their standing upstream of the failure, where the same skill prevents the stoppage it used to fix.
What does escaping reactive maintenance look like once it's working?
The share of work that was planned starts to climb and holds through a bad week. The call-outs thin out, the backlog stops growing, and the preventive job that slipped on Tuesday is on the list on Friday with somebody's name against it.
The long-run benchmark is high. World-class maintenance operations run planned maintenance percentages above 85%, the standard benchmark associated with the Society for Maintenance and Reliability Professionals. Treat that as a direction and never as a first-quarter target. The comparison that matters early is your own planned share this month against last month.
The first stretch is more modest and more encouraging. Broderick's Handmade, a food producer, had cut reactive maintenance by 60% four months after go-live, and the team got there by using the system rather than by adding features on top of it. The case study also records Broderick's getting more done with the same resources, which answers the headcount question in one line.
Two limits are worth naming. Some equipment should run to failure, because planning its care costs more than the breakdown, and choosing those machines is a discipline of its own. And a record can't defend the preventive window by itself. Somebody has to hold it in the week three things break at once, and that week always comes.
Every team that gets out of reactive maintenance believes what it believed at the start. What changes is the operation around the belief. The planned job stops disappearing when it slips, the technician who keeps a machine quiet gets the credit, and the crew's workload becomes something the record shows instead of something to fear.
You settled the reactive vs preventive maintenance question a long time ago. The open question is whether your operation is built so the planned job survives a bad week, and that is something you can change without asking anyone to care more than they already do.
