Being Right Isn't Enough

A lesson in job site politics nobody puts in a training manual.

Ninety VAV boxes. All programmed identically. All piped and wired the same way — or at least they were supposed to be.

I was deep into commissioning when I started noticing something wrong. A handful of hot water valves were behaving backwards. Calling for heat, valve closing. Not calling, valve opening. Classic signs of a normally open versus normally closed mix-up — except all my programming was identical, all my wiring checked out, and the rest of the boxes were fine.

I dug into it. Pulled the installation spec. Looked at the actuator orientation on the affected boxes. There it was: the heads were mounted wrong. Rotated the wrong direction at install. The fix was almost embarrassingly simple — remount the head, maybe five minutes a box.

I had the data. I had the diagrams. I had the installation spec with the diagram showing exactly which way the actuator needed to face. I walked into that meeting completely confident I knew what happened and what needed to happen next.

---

It didn't go the way I expected.

The mechanical contractor pushed back immediately. Alternative explanations that didn't hold up. Schedule pressure. The general friction of a room full of people who all have somewhere else to be. I made my case. I had the documentation. I was right.

My PM listened to the whole thing and then looked at me.

"Can't you just reverse the output in the program?"

I started to explain why that wasn't the right answer. Different configuration than the rest of the boxes, inconsistency in the system, the underlying install issue still not corrected—

He nodded like he'd heard this before.

"Do it anyway. Being right isn't always as important as it seems."

So I did. Reversed the outputs, documented which boxes were affected and why, and we moved on.

---

On the drive back I kept turning it over. The fix I wanted — remounting the heads — was genuinely simple. Faster than the meeting we just had. But on a union job, I'm not touching mechanical work. That's not my call to make, and making it unilaterally would have created a different kind of problem.

So the right fix wasn't actually available to me. And the fix that was available to me — the program change — was the one my PM had suggested from the start.

I'd walked in holding all the right answers. I walked out having done the thing I'd argued against, because it was the only move that didn't step on anyone's jurisdiction or blow up a relationship we'd need on the next job.

I'm still not sure I handled it well. I think I could have read the room faster and saved everyone forty minutes. But the deeper thing I took from it was this: technical correctness is the floor, not the ceiling. Knowing the heads were on wrong was the easy part. Knowing what to actually do about it — given the people, the contract, the politics, the schedule — that's the harder skill, and nobody teaches it.

Field-Ready will. But I'll be honest with you about how complicated it actually is.