10/09/2026
The project engineer tossed his marker onto the conference table, grabbed his laptop, and walked out.
Ten seconds later, the shop superintendent looked over at me and shook his head.
โThat guy lives in a fantasy world. If we stop production to change that drawing, it has to go back through the customer for approval.
That could take two weeks, and weโll miss our ship date. Weโve built these before. If we find a crack, we repair it. Why shut down the entire floor for something we know how to fix?โ
Five minutes later, the project engineer was standing in my doorway.
โHe doesnโt get it. The bevel prep is the problem. That edge is hardened, and after we weld it, weโre getting hairline cracks. I mean really, J, we know whatโs causing it, so why would we keep building it that way and risk the integrity of the joint?โ
They were looking at the exact same problem, and neither one was wrong.
The superintendent had crews on the clock, and a ship date he was responsible for hitting.
Changing the drawing could stop work for two weeks while it went back through customer approval.
The engineer had a known defect creating hairline cracks in a welded joint he was responsible for signing off on.
From his perspective, repairing cracks after they happened made no sense when we already knew what was causing them.
They were both protecting what they were accountable for.
And both were completely convinced the other guy was being stubborn.
Iโve seen this happen more times than I can count.
We assume someone is pushing back because they donโt understand our position.
But most of the time, they understand your position perfectly.
Theyโre just carrying a risk you arenโt.
If you want to influence someone, stop trying to prove why youโre right long enough to understand why they believe theyโre right.