Most of us understand that a car needs maintenance. Change the oil. Check the tires. Pay attention when a warning light comes on. We might not always do it on time, but we understand the deal: ignore those things long enough and eventually the car will stop cooperating.
Buildings are less demanding. Or at least they seem that way.
A building can keep functioning while a lot of things aren’t working particularly well. The heat still comes on, even if the system is working harder than it should. A small leak doesn’t necessarily stop anyone from using the room. A door that doesn’t quite close becomes something everyone learns to pull a little harder.
We get used to these things. Until we can’t.
A strange way to protect an investment
I wrote a short note about this in 2010. The question was simple: why do we accept preventive maintenance for a car, which generally loses value, but so often wait for something to break in a building, which we hope will hold or gain value?
That comparison isn’t entirely fair. Plenty of people neglect their cars, and plenty of buildings have good maintenance programs. Buildings don’t always appreciate, either.
But I still think there’s something worth looking at in the difference.
When a car breaks down, the consequence is immediate. You’re on the side of the road. Whatever you were planning to do next isn’t happening.
A building gives you more room to postpone the problem. You can put a bucket under the leak. Use another room. Turn up the thermostat. The cost of waiting may be real, but it doesn’t always arrive as an obvious bill.
Sometimes it arrives as a little more energy used every month. Sometimes as a repair that gets bigger. Sometimes as years of putting up with something that could have worked better.
Knowing what to do is part of the problem
Cars come with a fairly understandable maintenance routine. There are reminders, mileage intervals, and places you can go to have the routine work done.
A building is a collection of different systems, installed at different times, with different service needs. Knowing what needs attention, who should handle it, and whether a recommendation is reasonable can become a project of its own.
Even at home, where the owner and the person paying the bills are often the same person, that can be enough to put things off.
When responsibility is shared, it gets harder. The person who notices the problem may not control the budget. The person approving the work may not experience the inconvenience. Everyone can be doing their particular job while the underlying problem sits there.
What gets our attention?
I don’t think the answer is to maintain everything constantly. Maintenance costs money, and replacing something early isn’t automatically a good decision. Some things can reasonably be left alone until they fail.
The question is whether we’re making that choice deliberately, or just responding to whichever problem becomes impossible to ignore.
A broken system makes a strong case for itself. A functioning system that needs a little attention has a harder time. If we only make room for the first kind, we shouldn’t be surprised when emergencies keep winning.
That feels connected to the idea behind this publication. Systems depend on the signals they receive and what happens in response. A warning light is useful because it makes a problem visible while there’s still a choice about what to do.
Buildings have signals too. They just don’t always come with a light on the dashboard.
The original question still seems reasonable to me: if we consider a building one of our most important investments, why do we so often wait until it breaks to give it our attention?