The install failed. The vendor blamed the GC. The GC blamed the drawings. And the PM got stuck in the middle.
In spec-driven projects, when things go wrong, the first instinct is often deflection. But for PMs trying to maintain momentum, blame games are worse than mistakes. They don’t solve problems—they slow everything down.
What blame sounds like:
“We only shipped what was requested.”
“Talk to the contractor—that’s not our scope.”
“The drawing didn’t specify the anchor pattern.”
What PMs remember:
Who helped vs. who finger-pointed
Who owned the next step vs. who delayed the fix
Who stepped into the problem—even if it wasn’t theirs
Distributors who gain long-term loyalty:
Focus on resolution, not fault
Communicate material-specific risks in field terms
Track every substitution, deviation, and cure variable—and help document field impact
You don’t earn the next job by being blameless. You earn it by being useful when everything’s going wrong.
