The Maintenance Manager's Real Job
Most maintenance managers describe their job as keeping the plant running.
That description is accurate as a statement of purpose but misleading as a description of how the best maintenance managers actually spend their time.
Keeping the plant running reactively — responding to failures as they occur, coordinating emergency repairs, managing the crisis of the moment — is what most maintenance managers do most of the time.
Keeping the plant running proactively — preventing the failures before they occur, building the systems that make the team effective, managing performance against leading indicators — is what the best maintenance managers do most of the time.
The difference between these two modes is not capability.
It is capacity.
A maintenance manager spending 70% of their shift on reactive coordination has 30% of their capacity available for the proactive management activities that would reduce the reactive burden over time.
A maintenance manager spending 30% of their shift on reactive coordination has 70% of their capacity available for the proactive activities that compound into sustained performance improvement.
Building the systems that move the team from reactive to proactive mode is the highest-value investment a maintenance manager can make — and it is the investment that consistently distinguishes high-performing maintenance organizations from those that remain trapped in the reactive cycle regardless of how hard the team works.
The Five Management Disciplines of High-Performing Maintenance Teams
Discipline 1: Work prioritization that reflects consequence, not urgency
The most common maintenance team management failure is allowing urgency to override consequence in work prioritization.
The fault that is loudest, most visible, or most recently reported receives the fastest response — regardless of whether it represents the highest-value maintenance activity available to the team at that moment.
A systematic work prioritization framework replaces urgency-driven prioritization with consequence-driven prioritization — ensuring that the team's available capacity is directed toward the work that prevents the most costly failures and maintains the most critical assets.
The framework has four priority levels.
Priority 1 covers safety and environmental events requiring immediate response regardless of other work in the queue.
Priority 2 covers Tier 1 asset failures that are stopping production or imminently will stop production — dispatched as soon as a qualified technician is available.
Priority 3 covers Tier 1 and Tier 2 asset condition-based alerts and PM windows that require response within a defined time window to stay within the P-F interval.
Priority 4 covers all other planned and deferred work that should be completed during available capacity.
Every work order entering the queue is assigned a priority level at creation — not at dispatch — so that the maintenance manager and technicians always have a clear picture of what should be worked next regardless of which supervisor is on shift.
Discipline 2: Planning before dispatch
The single most impactful management practice for improving maintenance team productivity is ensuring that work orders are planned before technicians are dispatched.
A planned work order contains everything the technician needs to execute a first-time fix — the fault description, machine history, most likely causes, correct SOP version, parts list with confirmed storeroom availability, required tools, and estimated completion time.
An unplanned work order contains a fault description and a name.
The difference in execution outcomes between a planned and unplanned work order is significant — planned work orders produce higher first-time fix rates, shorter MTTR, better data quality, and less technician frustration.
In smaller maintenance teams where a dedicated planner is not practical, planning is the maintenance manager's most important pre-dispatch activity.
In larger teams where a dedicated planner or reliability engineer exists, the maintenance manager's role is ensuring the planning function is resourced and respected — not bypassed under production pressure with underprepared technicians dispatched before planning is complete.
Discipline 3: Daily team communication that drives the day rather than reacts to it
The shift handover and daily team meeting are the most consistently underutilized management tools available to a maintenance manager.
A shift handover that consists of "Line 3 had issues, check it out" passes no useful operational intelligence and starts the incoming team reactive.
A structured shift handover that covers current asset conditions, open work orders and their status, upcoming PM windows, parts staged for planned work, and any developing conditions that the incoming team should monitor starts the team informed and positioned to manage the shift proactively.
The daily team meeting — or shift start briefing — that reviews the day's planned work, confirms capacity against workload, and identifies the highest-priority open items before the shift begins is the management touchpoint that separates a planned maintenance operation from a reactive one.
These meetings should take 10 to 15 minutes and be structured enough to cover the essential information consistently regardless of which manager is running them.
Discipline 4: Performance management against leading indicators
Maintenance team performance management in most operations focuses entirely on lagging indicators — OEE achieved, unplanned downtime that occurred, PM compliance for the period just ended.
Lagging indicators confirm what has already happened.
They provide no mechanism for course correction during the period they measure.
A maintenance manager who learns at the end of the month that PM compliance was 71% on Tier 1 assets has learned something they cannot act on for the current month.
A maintenance manager who tracks PM compliance weekly and sees it dropping from 87% to 79% to 71% over three weeks has three weeks of early warning to identify the root cause and intervene before the compliance deficit produces the unplanned failures it predicts.
Leading indicator management requires four things.
Weekly rather than monthly reporting cadence for the most actionable metrics.
Asset-class-level rather than facility-level reporting — so that a compliance deficit on Tier 1 assets is not averaged away by high compliance on Tier 3 assets.
Defined response thresholds — specific metric values below which a specific management response is required within a specific timeframe.
Closed-loop tracking — confirming that the management response actually resolved the root cause rather than temporarily improved the metric.
Discipline 5: Technician development as a maintenance management priority
The maintenance manager who treats technician development as someone else's responsibility — HR, the training department, or self-directed learning — consistently loses the performance gains that skilled, developing teams produce.
Technician development in a maintenance context is not primarily formal classroom training.
It is the structured exposure to new failure modes, new equipment types, and more complex repair challenges that builds the diagnostic capability that reduces diagnosis time and improves first-time fix rates.
Pairing less experienced technicians with more experienced ones on complex repairs — not as observers but as active participants with defined responsibilities — accelerates capability development faster than any classroom program.
Structured post-repair reviews — five minutes after completing a complex or unusual repair where the technician walks through what they found, what they did, and what they would do differently — builds the reflective practice habit that accelerates capability development over time.
Ensuring that tribal knowledge from experienced technicians is captured in SOPs before those technicians retire or move on is the development activity that has the longest lasting impact on team performance — because it makes what the best technician knows available to every technician rather than disappearing when the individual leaves.
The Information Architecture That Makes Team Management Possible
Every management discipline above depends on reliable, timely, accurate information.
A maintenance manager cannot prioritize work by consequence without knowing what each asset's criticality classification is and what the current queue of open work orders contains.
A manager cannot plan before dispatch without knowing what parts are in stock, what the machine's fault history is, and what SOP version is current.
A manager cannot conduct a structured shift handover without a system that captures the current state of open work orders, developing conditions, and planned work for the incoming shift.
A manager cannot track leading indicators weekly without data systems that generate those indicators automatically rather than requiring manual compilation from multiple sources.
The maintenance manager who is managing through institutional memory, verbal communication, and end-of-shift paper reports is managing with one hand tied behind their back — not because they lack skill or commitment but because the information architecture they depend on is not providing the data their management disciplines require.
The transition from reactive to planned maintenance management is as much a data infrastructure change as it is a management behavior change.
The manager who receives a real-time dashboard showing current work order status, open PM windows, and asset condition alerts is positioned to make proactive management decisions.
The manager who learns about developing situations through verbal reports from supervisors who learned about them from operators is always one communication step behind the situation they are trying to manage.
Managing the Reactive-to-Planned Transition
The transition from a predominantly reactive maintenance operation to a predominantly planned one is the most significant management challenge in manufacturing maintenance — and it requires a specific management approach rather than simply deciding that the team will be more proactive.
Three specific management practices accelerate the reactive-to-planned transition.
Practice 1: Protect planned maintenance capacity from reactive cannibalization
The most common reason planned maintenance transitions fail is that reactive emergencies consistently consume the capacity that was allocated to planned work.
Protecting planned maintenance capacity requires explicitly scheduling PM windows into the production schedule — so that the machine time required for planned maintenance is committed before production orders are booked — and maintaining the discipline to defend that commitment when reactive pressure mounts.
A PM window that is consistently deferred when production needs the machine will never be executed.
A PM window that is built into the production schedule as a firm commitment — with the same status as a customer delivery commitment — is executed because the cost of deferral is explicit rather than invisible.
Practice 2: Make the reactive premium visible
The reactive maintenance cost premium — the difference between what reactive repairs cost and what the same repairs would have cost as planned maintenance — is the invisible financial driver of reactive culture.
When the maintenance manager can show the operations director that the emergency hydraulic press repair that stopped the line for four hours cost three times what a planned seal replacement would have cost two weeks earlier, the financial case for protecting planned maintenance capacity becomes concrete rather than theoretical.
Making the reactive premium visible requires the cost attribution data that a well-adopted CMMS provides — specifically, the ability to compare the labor and parts cost of reactive corrective work orders against the estimated cost of the planned PM that would have prevented them.
Practice 3: Celebrate prevention rather than only heroic response
Reactive maintenance culture is reinforced by the social recognition it generates.
The technician who repairs the production-stopping failure at 2:00 AM is recognized, thanked, and celebrated.
The technician who replaced a cam follower during a planned PM window two weeks earlier — preventing the failure that would have occurred at 2:00 AM — receives no recognition because the failure that did not happen is invisible.
Maintenance managers who deliberately recognize prevention — naming the specific failures that planned maintenance prevented, quantifying the downtime cost avoided — build the social reinforcement for planned maintenance that reactive culture does not provide naturally.
Frequently Asked Questions
What is the most important metric for a maintenance manager to track?
PM compliance rate on Tier 1 assets is the single most actionable leading indicator for most maintenance managers — because it predicts future unplanned downtime with meaningful lead time and because the root cause of compliance failure is almost always identifiable and addressable within the current planning period.
OEE is the ultimate outcome metric but it is a lagging indicator — it confirms what already happened rather than predicting what is about to happen.
The combination of PM compliance as the leading indicator and OEE as the lagging confirmation is the most complete performance picture for a maintenance manager's weekly review.
How does a maintenance manager build trust with the production team?
The most reliable trust-building mechanism is delivering on commitments.
A maintenance manager who says the filling machine will be back in production by 3:00 PM and delivers it by 2:45 PM builds more trust with the production manager than any relationship-building conversation can.
The commitments that a maintenance manager can make reliably are constrained by the quality of their maintenance data — specifically, the accuracy of MTTR estimates by fault type and the reliability of planned maintenance window scheduling.
Better data produces more reliable commitments. More reliable commitments produce more trust. More trust produces more cooperation from production in protecting planned maintenance windows. More protected PM windows produce fewer reactive emergencies. Fewer reactive emergencies produce better data.
The virtuous cycle begins with data quality.
What is the ideal maintenance team size for a mid-sized manufacturing facility?
There is no universal answer — the optimal team size depends on asset count, asset criticality profile, planned-to-reactive ratio, wrench time, and the complexity of the maintenance tasks the facility requires.
A more useful question is whether the current team size is appropriate given the current planned-to-reactive ratio and wrench time.
A team spending 60% of its time on reactive work with 30% wrench time has significantly more available capacity than the workload suggests — because improving the planned-to-reactive ratio and wrench time simultaneously can recover 20 to 30% of effective maintenance capacity without adding headcount.
Before adding maintenance headcount, assessing whether the reactive burden reduction and wrench time improvement that better management systems enable would provide the additional effective capacity required is almost always the more cost-effective first step.
The maintenance manager who is always fighting fires is not managing maintenance. They are managing the consequences of a maintenance program that has not yet been built. Building the program — the prioritization framework, the planning discipline, the performance feedback loops, and the data infrastructure that supports all three — is the management work that eventually makes the fires rare enough to manage.
Login
Blog
