Data, Risk, and Authority

Data, Risk, and Authority: How to Actually Resolve a Disagreement in Pre-Construction

Here’s the deal. Somebody recently described a real situation to me. A superintendent had gone through a fresh eyes review during pre-construction, the kind of session where an outside team looks at a plan with genuinely fresh perspective before construction starts. The review team came across as forceful and dismissive of his ideas, wanted things done a different way, and the whole experience left him nervous rather than genuinely collaborative. His question was simple and fair. How much authority should the fresh eyes team actually have over the superintendent when they disagree?

That question deserves a real answer, not a vague appeal to teamwork. Here is the actual hierarchy I use.

If We Have Data, Use the Data

There is a line I genuinely love, even though I recognize it can sound a little sharp if said the wrong way. If we have data, let’s go with data. If all we have is opinions, let’s go with mine. Said with the right tone, that is not an authoritarian power move. It is an honest statement about what should actually break a tie, and data comes first, before anyone’s personal preference, mine included.

In practice, that means when two people disagree during pre-construction, the first move is never simply picking whoever argues more forcefully. It is asking whether a historical reference class exists, whether a real what-if scenario can be modeled, or whether actual research can settle the question. If the data exists, let it decide, regardless of whose idea it happens to support.

This step alone resolves more disagreements than people expect, precisely because it changes what the conversation is actually about. Instead of two people defending their own instincts, the room shifts toward jointly investigating what the evidence actually shows, which tends to defuse the personal tension that makes disagreements feel adversarial in the first place.

If It Is Genuinely Risky, Take the Safer Path

When no clear data exists to settle a disagreement, the next question is risk. If one option carries genuine potential to put the business, the company, or actual people at real risk, that risk should decide the outcome, again regardless of personal preference. A safer option beats a slightly more convenient one every time real risk is on the table.

Watch for these signs a disagreement is actually being resolved by force of personality rather than this hierarchy:

• A decision made simply because one person pushed harder or louder in the room.
• No attempt to check historical data or model a what-if scenario before settling an argument.
• Risk to the business or to people treated as a secondary concern rather than a genuine deciding factor.

Past Data and Risk, Default to the Superintendent and PM

Once you have genuinely checked for data and ruled out significant risk, and a real disagreement still remains, my honest default leans toward letting the superintendent and project manager make the call. That is not because their opinion outranks everyone else’s by default. It is because somebody has to make the decision, and the people accountable for actually running the project are a reasonable default when the choice is otherwise a genuine toss-up.

Notice that this is explicitly a default, not a rule applied automatically in every case. The next distinction below explains exactly when that default should shift toward the broader team instead, which is where this hierarchy actually gets interesting rather than simply restating a standard chain of command.

The What Versus the How

Here is a distinction that changes how this actually plays out in practice, and it comes up constantly in my own thinking. What we are doing on a project is fundamentally a company leadership decision. How we are doing it, the actual means and methods, belongs mainly to the people with boots on the ground, the trade partners actually executing the work.

That distinction matters directly for the fresh eyes scenario that started this whole conversation. If a disagreement is genuinely about means and methods, with no real data available and no significant risk difference between the two approaches, meaning it is close to a coin flip either way, my instinct leans toward letting the team closest to that decision make the call themselves, rather than the superintendent or PM overriding it by default.

Why Letting the Team Decide Actually Matters

That preference is not just about being nice or building consensus for its own sake. It connects directly to a real leadership principle worth taking seriously. Jocko Willink’s laws of combat, built around the extreme ownership framework, make a specific point. If a team made the plan themselves, they genuinely own it, and they can be held properly accountable for how it plays out.

That accountability only holds up if the team actually had real input into the decision in the first place. Override a team’s means and methods call by default, even when data and risk genuinely do not favor either side, and you quietly remove their ownership over the outcome. Then, when something does not go perfectly, holding them fully accountable for a decision they never truly made becomes much harder to justify.

Applying This Back to the Fresh Eyes Scenario

Go back to the original situation. A superintendent felt steamrolled during a fresh eyes review, not genuinely collaborated with. Run that disagreement through this hierarchy honestly, and the fix becomes clear. Start by asking whether real data actually existed to settle whatever the disagreement was about. If it did, that should have decided the outcome regardless of who felt strongly about it. If no data existed, ask whether real risk was genuinely at stake. If it was not, and the disagreement was really about means and methods with the two options roughly equivalent, the superintendent’s team, the people who would actually own executing the plan, deserved real weight in that decision, not a forceful override from reviewers who would not be the ones held accountable for how it went.

A fresh eyes review is genuinely valuable when it surfaces real data or real risk nobody had considered yet. It becomes counterproductive the moment it turns into simply overriding the field team’s judgment on a genuine toss-up decision, because that erodes the very ownership that makes accountability meaningful later.

Building This Hierarchy Into Your Own Team

None of this requires a formal policy document to implement. It requires a shared, genuinely understood order of operations that everyone in a room actually applies consistently, rather than defaulting to whoever argues the loudest or holds the most senior title.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams build genuine decision making discipline around data, risk, and authority, so pre-construction reviews and fresh eyes sessions actually build ownership instead of quietly eroding it.

So here is the challenge. The next time a genuine disagreement comes up in pre-construction or during a fresh eyes review, walk through this hierarchy out loud with the room. Is there real data? Is there real risk? And if neither settles it, is this a means and methods question that genuinely belongs to the people who will own executing it? That simple sequence turns a personality contest into an actual decision process everyone can respect afterward.

Jason Schroeder said it plainly: “If we have data, let’s go with data. If all we have is opinions, let’s go with mine.” Said with the right intent, that is not arrogance. It is a genuine commitment to letting evidence, not force of personality, decide.

On we go.

FAQ

Why should data outrank even a senior leader’s strong opinion when resolving a disagreement?

Because personal conviction, no matter how confident, is not the same thing as verified evidence, and a historical reference class or a modeled what-if scenario reflects reality more reliably than anyone’s gut feeling, regardless of their seniority. Prioritizing data over opinion protects a project from decisions driven by whoever argues most forcefully rather than what actually tends to work.

What is the actual difference between a “what” decision and a “how” decision?

A “what” decision covers the overall direction or goal a project is working toward, which generally belongs to company leadership. A “how” decision covers the specific means and methods used to accomplish that goal, which generally belongs to the people actually doing the work, since they carry the practical knowledge and the eventual accountability for how well that method performs.

Why does letting a team make its own means and methods decision matter for accountability later?

Because genuine accountability depends on genuine ownership, and a team that never actually got to make a real decision cannot fairly be held fully responsible for how that decision turned out. Letting the team closest to the work make a genuine toss-up call preserves their ownership over the outcome, which is exactly what makes holding them accountable later fair and meaningful.

When does a fresh eyes review in pre-construction become counterproductive?

It becomes counterproductive when it shifts from genuinely surfacing new data or risk the original team had not considered into simply overriding the field team’s judgment on a decision that was really a toss-up. A fresh eyes review adds real value when it changes the actual inputs to a decision. It causes harm when it just replaces one opinion with another more forceful one.