The unglamorous work of maintenance

Every organization I have been part of, including the ones we own, has an easier time celebrating the start of something than the upkeep of something. A new product line, a new client segment, a new hire for a new function — these get attention, discussion, and a kind of institutional energy that maintenance work almost never receives. Keeping an existing data process accurate, keeping an existing client relationship healthy, keeping an existing piece of infrastructure from quietly decaying: none of this produces a satisfying announcement, and so it tends to receive less attention than its actual importance would justify.

I think this imbalance is one of the most common and least discussed causes of decline in otherwise well-run companies. Nothing dramatic happens. There is no single bad decision to point to. Instead, a hundred small maintenance tasks each get deprioritized slightly, in favor of something newer and more interesting, and the aggregate effect, years later, is a business whose foundations are noticeably weaker than its newer initiatives would suggest, for reasons nobody can name precisely because no single decision caused it.

Why maintenance loses the argument

Maintenance loses the argument for attention because it is being compared, in the moment, against the wrong alternative. The question that gets asked is usually which of these two things is more exciting to work on, and maintenance will almost always lose that comparison. The question that should be asked is which of these two things, left undone, will cost us more in three years, and maintenance very often wins that comparison by a wide margin. The mismatch between these two questions, repeated often enough across a company, produces a business that looks busy and innovative on the surface while its underlying reliability slowly erodes underneath.

The question is not which task is more exciting. It is which one, left undone, will cost more in three years.

Making maintenance count as real work

Across ProspectScout, ExecLeads, and Franopolis we try to correct for this by treating maintenance as a category of real work rather than a residual claim on whatever time is left over. It gets named, it gets staffed, and the people who do it well get recognized for it with the same seriousness as the people who launch something new. This sounds like a small cultural adjustment, but it changes the incentives in a way that a general exhortation to care about quality never does. People respond to what gets rewarded, and if maintenance is never rewarded, no amount of saying it matters will make it happen consistently.

This is, in a sense, the operating discipline that makes the longer-term ownership thesis actually work rather than just sound appealing. A permanent owner can afford to invest in maintenance that a shorter-term owner would skip, because the permanent owner is the one who will still be dealing with the consequences of skipping it. But that affordability only matters if it is actually used. There is no credit for being structurally capable of patience if the daily habits of the business do not reflect it, and the unglamorous work of upkeep is where that reflection either shows up or quietly fails to.