The year-end maintenance review went well. Cost came in under budget. Downtime stayed within target. PM compliance looked strong. Planned-work percentage ticked up a few points. On paper, a good year, and the room felt good about it.

Out in the hallway afterward, the conversation sounded different.

Supervisors traded stories about how many non-critical PMs they'd pushed to make room for production. Planners mentioned the scopes they'd thinned to fit the hours. Engineers quietly named the systems being held together with temporary fixes. And everyone hoped next year's turnaround would have enough slack to finally catch up.

The space between those two conversations is where culture and incentives live.

Maintenance debt doesn't only come from bad processes or weak tools. A lot of it comes from good people responding rationally to what their culture rewards and their KPIs measure. Pay attention to the wrong things and you'll grow debt no matter how good your planning gets.

Culture isn't the poster in the breakroom. It's the pattern of what gets rewarded, what gets tolerated, and what gets quietly punished.

In a lot of operations, the unwritten rules read something like this. The heroes are the people who get the plant back up fast, whatever it takes. Asking for downtime to do preventive work is a reputational risk. Hitting this quarter's cost and production numbers matters more than preventing next year's problems. Maintenance is a cost center, and success means doing more with less.

Notice that none of those messages says a word about maintenance debt. They don't have to. They build an environment where deferrals are easier to justify than stoppages, short-term savings look more real than long-term risk, and cosmetic compliance beats honest, messy data. In that environment, debt grows almost on its own. Nobody decides to create it. The culture decides for them.

Metrics are loud. They tell everyone what leadership is actually watching. And a few common patterns quietly reward the exact behaviors that build debt:

The KPI guidance on this is consistent: balance the cost and availability numbers with proactive ones like planned-work percentage, MTBF, and schedule compliance. Get that balance wrong and your scorecard stops measuring reliability and starts quietly manufacturing debt.

Annual budgets and mid-year cuts are another place debt gets baked in.

When the targets tighten, the responses are predictable. Defer the non-mandatory work into a future period. Trim the turnaround scope. Push the capital project out a year. "Optimize" the PMs in a way that quietly strips content rather than real waste. On the spreadsheet, all of it reads as cost discipline. In the plant, it reads as assets running closer to the edge.

The deferred-maintenance research keeps landing on the same warning. Push work out often enough and you get higher operating cost, more unplanned downtime, and rising odds of a safety or environmental event down the line. The budget cycle, left unexamined, becomes a machine for taking on maintenance debt to hit a near-term number, with the bill arriving in a different fiscal year, or on someone else's watch.

There's a real difference between a hero culture and a reliability culture, and you can feel it the moment you walk in.

In a hero culture, the people who fix big problems under pressure are the stars. Nights and weekends spent saving production are badges of honor. The chronic issues that keep generating those emergencies get far less attention than the emergencies themselves. In a reliability culture, the quiet prevention of problems is what gets valued. Teams get recognized for cutting reactive work and killing repeat failures. It counts as a win when nothing happens, because the systems were maintained well enough that nothing had to.

In the hero culture, maintenance debt is a byproduct. The organization keeps borrowing against asset health to hit immediate targets, then leans on its heroes to limit the damage when the debt comes due. It feels exciting. It's also exhausting, expensive, and impossible to sustain.

If debt is going to shrink instead of grow, the incentives and the metrics have to move.

A few shifts do most of the work. Put debt-focused indicators on the leadership scorecard, the aged critical backlog, the planned-versus-reactive share, and the repeat failures on key systems, because those reflect directly whether debt is being created or retired. Reward teams for cutting reactive work and repeat failures, even when their maintenance cost ticks up a little in the short term, because that's usually what paying down debt looks like on the way in. Clarify who actually has the right to accept maintenance debt on the organization's behalf and under what conditions, so those calls get made in the open instead of by default at the frontline. And tell prevention stories the same way you tell hero stories, holding up the planned outage or the well-timed major repair that quietly prevented a much bigger loss.

Daily leadership behavior carries as much weight as the metrics. Ask "what debt did we create or retire this quarter?" right alongside the cost and downtime questions. Protect the critical maintenance work when budgets tighten instead of cutting it first. Back the site leader who makes the hard call to take downtime on a high-risk asset. Show real interest in data quality and root-cause learning, not just closure rates. Those signals tell the whole organization that maintenance isn't overhead to be minimized. It's a risk and reliability function to be managed on purpose. Helping leaders make that shift, and tie it to indicators that hold up in front of both operations and finance, is a lot of what we do.

Maintenance debt doesn't pile up in a vacuum. It piles up in cultures and scorecards that reward short-term wins, celebrate firefighting, and define success in ways that quietly ignore long-term risk.

Leave those drivers in place and every technical improvement you make, better planning, better systems, better processes, will be fighting uphill. The default behaviors will keep creating debt faster than the improvements can retire it. Fix the incentives and the same people who used to stretch assets too far start advocating for the right work at the right time. That's the whole game.

Next in the series, we stay on the human side of complexity and the one layer no software and no scorecard can manage for you: people. Skills, turnover, informal habits, and the shadow processes that grow up to fill the gaps.