Need Data when Opinions Gridlock

Data When Opinions Hold

Here’s a problem that kills projects: the team is gridlocked. The superintendent wants to add labor to recover from a delay. The PM wants to work overtime. The foreman wants to shorten durations and tell the crew to figure it out. And the Lean consultant is suggesting intelligent alternatives like rezoning, changing sequence, or isolating the problem. But nobody has data. So, the senior-most person says, “If all we have are opinions, let’s go with mine.” And the project crashes because the wrong decision won.

This is about what to do when opinions hold and data is missing.

The Pain of Crashing Activities the Old Way

I was prompted to do this podcast because of a situation. One of the most limiting factors that we have at LeanTakt, which is not a problem, we’re not upset, I’m not being negative, but is working through untrained people a lot of times that don’t know production systems, they don’t know Lean thinking, they’ve not been taught project management 101 principles. And a lot of times our folks, it’s never technical, it’s never, “Oh, let me solve this technical problem.” It’s always working through somebody’s prompting in their brains, which is fine, super love it, we build people before we build things.

And there’s times, one of the biggest problems that we have is that your construction projects get delayed. That’s just how life is. Construction projects sustain impacts and delays. No matter how much you’re trying to prevent it, they will still happen. And the worst thing that a person can do is to throw more untrained, non-onboarded labor last minute, work overtime, rush, push, and panic, add materials, and you know, stock too many materials, and start adding excess crews. It’s just a toxic environment. Or throw money at the problem. Those are all the typical CPM crashing activities answers, and none of them work.

Here’s what happens. The project falls behind. The superintendent panics. The PM says, “We need to make up time.” And the knee-jerk reaction is to add labor, work weekends, shorten durations, and push harder. Nobody maps out the options. Nobody simulates the scenarios. Nobody looks at the data. They just react with the old CPM playbook that has never worked. And the project spirals deeper because adding untrained labor, working overtime without planning, and rushing the crew creates more chaos, not less.

The Intelligent Alternatives Nobody Considers

There are some really smart ways to make up for delays: utilizing a buffer, changing the sequence as long as you have prerequisite work and it works and you have the materials, or isolating the problem, or rezoning after the problem. Or there’s twelve, to my knowledge, documented ways to accelerate and fix these problems. And we have posters that are available for free. They’re actually, I don’t know if everybody knows this, but there’s a toolbox tab on the Elevate Construction website now where you can go get any of these tools for free and just download them. You don’t even have to mess with me. They’re just right there in the Canva files.

So, this is all ready to go. And there’s a proper way to recover from delays, and there’s a proper way not to. And there are some times where our folks will be working with a project team, and the project manager or the superintendent will want to go do one of those old-timey crashing the activities type things. “Well, let’s just add a last-minute crew. Let’s just start working overtime. Let’s just shorten the duration and tell them to figure it out. Let’s just add eighteen people.”

Okay, okay, hold on, hold on. And when we offer suggestions, it’s turned down. And we do gate meetings in the process, and we do builder reviews, and we have what’s called a wolf meeting. When things go bad on a project, we do the Pulp Fiction. You’re sending in the wolf, right? So we send some of our top builders to help them before it becomes a problem. It’s not reactionary, it’s preventative.

And this team that I was working with had suggested the project team do some really intelligent things to recover from this impact and this delay. And they were like, “No.”

And so, it was opinions, opinions, opinions.

The Famous Quote: Data Versus Opinions

And I finally got to the point where I was like, “Hey, the only way you can do this is to simulate what all of the different what-if scenarios look like.” And I told the person that famous quote: “If we have data, let’s go with data. If all we have are opinions, let’s go with mine.”

That’s the way the famous quote goes. And so, a superintendent is going to pull that, or the PM is going to pull that trump card. They’re going to say, “If we have data, let’s go with data. But if all we have are opinions, let’s go with mine.”

Here’s the problem with that quote. It sounds reasonable. It sounds like leadership. But it’s a power play disguised as decision-making. And when the senior-most person pulls rank and overrides intelligent alternatives with their opinion, the project suffers. Not because they’re bad people. But because opinions without data are just guesses. And guesses don’t recover schedules.

The only way we are able to get past some of these sticky situations is to say, “Okay, well, if you add labor, this is what it’s going to look like. And this is how it’s going to extend the schedule or the production plan. It could be a schedule. But if you actually rezone it, this is what it looks like. If you change the sequence, this is what it looks like. If you isolate the delay and handle it with a change order and a separate paid crew, this is what it looks like.”

And so, we just need to get to a point where we have data.

Why Opinions Without Data Fail

And my point is, if you don’t have data and it’s just opinions, the senior-most person is just going to say, “Let’s just go with my opinion.” And so it’s time in those situations to just pivot to, “Let’s map it out on paper. Let’s get some data. Let’s go ahead and simulate some what-if scenarios and let’s map it out so we can see it visually and put it on the table.” That’s what we have to do when we’re gridlocked in a team.

Here’s why opinions fail. Opinions are based on past experience. And past experience might not apply to the current situation. The superintendent’s experience with adding labor on a previous project might have worked because the conditions were different. The crew was already onboarded. The zone was ready. The sequence aligned. But on this project, adding labor might create coordination chaos, extend durations, and burn out the existing crew.

Without data, you can’t know. You’re just guessing based on what worked before. And when multiple people are guessing based on different experiences, the loudest voice wins. Or the senior voice wins. And the project pays the price.

How to Get Data When Opinions Are Holding

Here’s the solution. When the team is gridlocked and opinions are flying, stop talking and start mapping. Take the Takt plan. Simulate the scenarios. Map out what happens if you add labor. Map out what happens if you rezone. Map out what happens if you change the sequence. Map out what happens if you isolate the delay and handle it separately. Put all the options on paper. Show the team the visual. Let them see the consequences of each decision before they commit.

This is what we do in wolf meetings. We don’t argue. We don’t debate. We don’t let opinions hold. We map scenarios. We show data. And we let the data drive the decision.

Here’s what that looks like practically:

• Option one: Add untrained labor. Result: coordination chaos, extended durations, crew burnout. Visual: show the train stacking, the zones extending, the timeline slipping further.
• Option two: Rezone after the problem. Result: smaller zones, maintained rhythm, buffers preserved. Visual: show the train flowing, the buffers intact, the timeline recovering.
• Option three: Change the sequence. Result: prerequisite work ready, trades flow in new order, delay isolated. Visual: show the adjusted sequence, the handoffs realigning, the timeline stabilizing.
• Option four: Isolate the delay and handle it separately with a change order crew. Result: train continues flowing, delay handled independently, schedule protected. Visual: show the main train moving, the separate crew handling the delay, the timeline unaffected.

Now the team isn’t arguing opinions. They’re looking at data. And the senior person can’t pull rank because the data is right there. The best option is visible. The consequences are clear. And the decision becomes obvious.

Connecting This to Respect for People

This is a respect-for-people issue. When you override intelligent alternatives with your opinion just because you’re senior, you disrespect the people who offered those alternatives. You disrespect the data. You disrespect the process. And you disrespect the crew who will suffer the consequences of the wrong decision.

Respect for people means you listen to alternatives. You simulate scenarios. You look at the data. And you make decisions based on what the data shows, not on who has the loudest voice or the highest title. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

And here’s the truth: the senior person’s opinion might be right. But you don’t know until you test it against the alternatives. Data reveals the truth. Opinions hide it. And when the project is on the line, you owe it to the team to get the data before you decide.

A Challenge for Project Teams

Here’s what I want you to do this week. The next time your team is gridlocked and opinions are holding, stop. Don’t let the senior person pull rank. Don’t let the loudest voice win. Map the scenarios. Simulate the options. Put them on paper. Show the team the visual. Let the data drive the decision.

And if you’re the senior person, resist the urge to say, “If all we have are opinions, let’s go with mine.” Instead, say this: “Let’s map out the options. Let’s simulate the scenarios. Let’s look at the data and make the best decision for the project.” That’s leadership. That’s respect. That’s how you protect the team from the consequences of uninformed decisions. As we say at Elevate, data beats opinions every time. When the team is gridlocked, map the scenarios, show the visual, and let the data decide.

On we go.

Frequently Asked Questions

What does “if we have data, let’s go with data, but if all we have are opinions, let’s go with mine” mean?

It’s a famous quote that sounds reasonable but often becomes a power play. The senior person pulls rank and overrides alternatives with their opinion when data is missing. The solution is to get data by mapping scenarios so decisions are based on evidence, not hierarchy.

What are the intelligent alternatives to adding labor when projects fall behind?

Utilize buffers, change the sequence (if prerequisite work is ready), rezone after the problem, isolate the delay and handle it separately with a change order crew. There are twelve documented ways to recover from delays without crashing activities the old CPM way.

How do you simulate what-if scenarios when the team is gridlocked?

Take the Takt plan and map out each option visually. Show what happens if you add labor, rezone, change sequence, or isolate the delay. Put the scenarios on paper so the team can see the consequences before committing. Let the data drive the decision.

Why does adding untrained labor last minute usually fail?

Because it creates coordination chaos, extends durations, and burns out the existing crew. Untrained labor needs onboarding. They slow down the experienced crew. They don’t know the plan. And they create variation instead of reducing it. Data shows this. Opinions ignore it.

Where can I find the recovery tools and posters mentioned?

On the Elevate Construction website under the toolbox tab. The tools are free to download in Canva files. You don’t have to contact anyone. Just download them and use them to map scenarios and recover from delays intelligently.