Why do complex systems and retrofit tradeoffs still trip up our team?
You can walk most buildings now and read them clearly. The trouble starts when systems interact — mechanical, electrical, envelope — and the retrofit means picking a loser. Someone wants lower cost. Someone wants less disruption to the tenant. Someone wants the number that looks good on paper. You call this a technical problem. It usually isn't. Look honestly at your last stuck audit. Was it the system that confused you, or was it that your team disagreed about what to protect and never said so out loud? Complexity in the building is real. But most of the delay comes from unspoken priorities colliding in a meeting, dressed up as an engineering debate. You do not control how tangled a building's systems are. You do control whether your team names its tradeoff rules before it needs them. Decide what 'good enough' means, together, in plain words, before the next hard case arrives. Do this and the technical work gets easier — not because the building changed, but because you did.
The gap isn't more facts about controls or heat pumps. It's that your team has never agreed, before the argument starts, what counts as good enough. Set the tradeoff rule together first — cost, disruption, performance — write it down. Then the complex system is just hard detail, not confusion.
What changes unlock by starting
- Your team argues about the actual tradeoff, not around it
- Retrofit decisions take less time because the rule already exists
- Fewer audits stall waiting on unresolved disagreement
- A shared, written standard for 'good enough' you can reuse project to project