Hired to Disagree
You bring in a contractor. You vetted them properly—checked the work, checked the references, paid for the engagement because they know something you don’t. Partway through the project, they tell you something you don’t like. Not incompetence, not evasion—a clear, confident recommendation that runs against your own instinct for how this should go.
You’re now standing in the exact situation you hired them to be in. And you don’t like it.
What do you do?
It turns out that question is incomplete. The better question isn’t whether you should trust the contractor. It’s what the disagreement itself is trying to tell you.
What disagreement tells you
If they were always going to agree with you, you didn’t hire expertise. You hired validation.
Disagreement with an expert doesn’t tell you who’s right. It tells you that one of you is operating from an incomplete picture. Your job isn’t to defend your conclusion. It’s to discover whose picture is missing a piece—and the trap is that your own certainty doesn’t announce itself as a hypothesis. It arrives feeling like a fact.
That’s the actual tension. Not “should I trust the expert.” Whether you currently have enough information to know if you’re the one who’s wrong.
Two ways to avoid finding out
The default resolution is bad, and it’s bad in one of two directions—both of which feel like a decision, and neither of which is.
The first is deference. They’re the expert, so their answer stands, full stop. This looks like respect. It’s actually abdication—you’ve stopped being accountable for the outcome and started being a pass-through for someone else’s judgment, which isn’t why you hired them.
The second is override. You’re the client, it’s your call, and their twenty years of experience doesn’t change what you already believe about your own environment. This looks like leadership. It’s actually the same failure from the other direction—you’ve decided the disagreement is resolved before you’ve done anything to resolve it.
Both skip the same step. Neither one asks what the other person sees.
What the actual work looks like
The alternative isn’t complicated. It just takes the discipline to slow down before making the decision.
Ask what failure they’re protecting against. An experienced contractor’s recommendation is rarely arbitrary—it usually comes from having watched a specific thing go wrong somewhere else, and that specific thing is worth naming out loud rather than assumed. Experience has a way of compressing years of failure into something that sounds like a preference. What feels obvious to the contractor may be the residue of a dozen projects that broke for reasons you’ve never had to encounter. The recommendation isn’t coming from confidence. It’s coming from memory.
That conversation rarely takes a formal shape. It happens in a follow-up call, a margin note on a project plan, a question asked twice because the first answer didn’t quite land. Ask what has to be true for their recommendation to be correct—what assumption is doing the load-bearing work underneath it. Then check whether that assumption actually holds here, in your environment, with your constraints, not in the environment where they learned the lesson the recommendation is built on.
None of this is an interrogation, and it isn’t a negotiation either. It’s an effort to make somebody’s reasoning visible enough that a real decision—yours—can get made on top of it instead of underneath it.
Sometimes the assumption holds, and you find out you were the one missing something. Sometimes it doesn’t, and their recommendation—sound in general, wrong for your specific case—needs to be overruled. Either outcome is fine. What matters is that you know which one happened, instead of guessing and calling the guess a decision.
What you’re paying for
You can still overrule the expert. That was never off the table.
There’s a real difference between overruling someone because you understood their reasoning and found where it didn’t fit your situation, and overruling them because their answer collided with what you already believed. The first is judgment. The second is just your original opinion wearing a different outfit.
The value of expertise isn’t that it’s always right. It’s that it gives you one last opportunity to discover that you might be wrong.
Discover more from At Ground Level
Subscribe to get the latest posts sent to your email.
