Things My Engineer Knows That I Don't
Property managers are expected to make real decisions about buildings they weren't formally trained to operate - alongside people who have spent entire careers learning those types of systems.
That's not a failure of the profession. It's the nature of the job.
You are not the engineer. You are the leader of a building that requires engineers, technicians, and specialists across multiple trades. Your job is not to out know them. Your job is to understand enough about how your building works to ask the right questions, recognize when something doesn't add up, and champion the right decisions with ownership and vendors.
When your maintenance tech tells you a piece of equipment has been running harder than normal and they want to get eyes on it before the busy season - do you understand enough about that system to know why that matters? Can you translate that concern into a capital conversation with ownership? Can you get ahead of it before it becomes an emergency?
That's the level of fluency the role requires. Not a technical certification. Operational awareness.
What It Costs When the Gap Stays Hidden
The knowledge gap isn't abstract. It shows up in specific, expensive ways.
The vendor call you can't push back on. A contractor tells you a repair requires a full component replacement. You don't have enough context to ask whether that's the only option, whether deferring it is realistic, or whether the failure mode they're describing is consistent with what your tech reported. You approve it. Maybe it was right. You'll never know because you didn't have enough to interrogate it.
The budget conversation that falls apart. You're asking ownership to approve a significant repair. They push back. You can relay what your engineer told you but you can't connect the technical problem to the financial consequence in language ownership needs to hear. The request fails - not because it was wrong, but because the translation wasn't there.
The maintenance team that stops bringing you problems early. This is the most expensive one and the least visible. When your team concludes that their PM doesn't track what they're describing, they start filtering. They bring you what needs your signature and manage the rest themselves. Your situational awareness of the building's real condition quietly degrades and you don't know what you're missing.
How to Build It, Without Going Back to School
The best technical education available to a property manager isn't a course or a certification. It's already in the building you're managing and the team you're leading.
Walk the building with your maintenance team. Not an inspection - a conversation. Ask them to explain one system while you're standing in front of it. How does it work when it's running normally? What does something wrong look like? What do they watch for? Most good technicians enjoy this conversation. They've been waiting for someone to ask.
Attend vendor meetings. Stop sending your engineer alone. Sit in. Bring a notebook. Ask the questions you genuinely don't know the answers to - why this approach and not another, what failure looks like if you defer, what they'd do if it were their building. Vendor meetings are free education from people who spend their careers on one system.
Do the debrief after every incident. When something fails or a situation escalates, ask your team to walk you through it afterward. What happened, why, what the early signs were, and what catching it earlier would have looked like. Real events stick. You start recognizing patterns before they become problems.
Ask why before you approve. Every time your maintenance team or engineer recommends something, ask why before you sign off. Not to challenge them - to understand it well enough to defend it to ownership and to know it's the right call. A good technician respects that question. It tells them you're engaged and that you'll back them when it matters.
The Question That Changes the Relationship
When I started asking, something shifted that I didn't expect.
My team started bringing me problems earlier.
Not because I suddenly knew more than them. But because they realized I could handle the information - that I'd listen, that I'd take it seriously, that I'd go to bat for the repair or the capital request or the vendor change they were recommending. They trusted me with the early stage concerns because I had shown up for the ones that came before.
That's the return on investment that never gets quantified. How many emergencies didn't happen because a maintenance tech felt comfortable enough to say "something's off with this equipment" three weeks before it became a crisis?
Three questions worth asking your team:
"What do you wish I understood better about this building?"
"What's something you've been wanting to flag but weren't sure how to bring up?"
"If you could change one thing about how we plan and prioritize - what would it be?"
These questions are uncomfortable to ask. That discomfort is the point.
What I'd Tell Every Property Manager
There are still systems in buildings I've managed for years that my engineer understands better than I do. That hasn't changed.
What changed is that I know enough to ask the right questions. To understand the options I'm given. To translate a maintenance concern into a capital conversation. To know when something doesn't add up.
Your maintenance team has the answers. Your job is to be curious enough to ask the right questions and consistent enough to act on what they tell you.
Know your building. Know your team. Stay ahead of the problems.
The building will keep teaching you as long as you're willing to show up and listen.
If you found this newsletter interesting, consider checking out these past editions:
