Clarify the Problem Before You Solve It

Here’s the pattern that wastes more time than almost anything else in construction leadership. Someone brings you a problem. And before they finish explaining it, you’re already proposing solutions. You’re an extrovert. You think out loud. You process by talking. And in your mind, jumping straight to solutions shows you’re decisive and action-oriented. But what you’re actually doing is solving the wrong problem because you never took time to understand what the real problem is.

I’ve watched this destroy decisions repeatedly. A superintendent asks about schedule delays. Before the conversation explores why delays are happening, someone proposes adding overtime. A foreman mentions quality issues. Before anyone investigates root causes, someone suggests more inspections. A project manager brings up budget overruns. Before the team examines what’s driving costs, someone recommends value engineering. And every time, the proposed solution misses the actual problem because nobody slowed down long enough to understand what’s really happening.

This isn’t just inefficiency. This is how good teams make terrible decisions. Because when you jump to solutions without clarifying problems, you build consensus around answers that don’t address what’s actually wrong. You implement fixes that don’t fix anything. And six weeks later, you’re back in the same meeting wondering why the problem hasn’t improved.

The Pain of Solutions That Don’t Solve Anything

You’ve experienced this frustration. Your team identified a problem. Everyone agreed on a solution. You implemented it. And the problem is still there. Maybe it got worse. Maybe it morphed into a different problem. But it definitely didn’t go away like you expected.

That’s because you never understood the problem in the first place. You had symptoms. You had complaints. You had frustrations. But you didn’t have clarity on what was actually causing those symptoms. So you solved for what you thought the problem was, not what it actually was. And now you’ve wasted time, energy, and credibility on a solution that doesn’t work.

I see this constantly in construction. Teams rush to implement new software without understanding why current processes aren’t working. Leaders add more meetings without diagnosing why communication is breaking down. Companies hire more people without clarifying why productivity is low. And every one of these solutions misses the mark because the problem was never properly defined.

Think about Samsonite. Not the luggage company, but the movie reference. In the movie “Dumb and Dumber,” the character thinks he’s supposed to be in Aspen when he’s actually supposed to be somewhere completely different. Someone tells him where to go, and he responds, “We were way off.” That’s what happens when you jump to solutions without understanding problems. You end up way off because you were solving for Aspen when the actual destination was somewhere else entirely.

The System Rewards Quick Answers Over Right Answers

Here’s what I want you to understand. The construction industry rewards people who appear decisive. Who jump into action. Who propose solutions immediately. We promote extroverts who think out loud and generate ideas quickly. We value speed over accuracy. And that cultural preference for rapid response creates a systematic bias toward solving problems before we understand them.

But here’s the truth about decision-making that nobody wants to admit. Extroverts process by talking. They generate options out loud. They think through problems verbally. And while that creates energy and momentum, it also creates premature solutions. Because when you’re talking through options before you’ve analyzed the problem, you’re building consensus around ideas that might be completely wrong.

Introverts process differently. They think before they talk. They analyze internally. And while that can feel slower or less engaging in meetings, it often leads to better decisions because they’ve actually thought through the problem before proposing solutions. But we kick introverts off leadership teams because we don’t like how they operate. We say they’re not engaged or not contributing. And we lose the very people who could help us avoid jumping to wrong solutions.

The book “Decisive” by Chip and Dan Heath breaks down why we make bad decisions and how to make better ones. They identify common biases that destroy decision quality: narrow framing where we only see limited options, confirmation bias where we collect information that supports what we already believe, short-term emotion that overrides long-term thinking, and overconfidence that we know how things will unfold. Every one of these biases gets worse when we rush to solutions without clarifying problems.

The WRAP Process That Improves Every Decision

Let me walk you through the framework that transforms how you approach problems. It’s called the WRAP process, and it comes from the book “Decisive.” These four steps systematically overcome the biases that lead to bad decisions and create space for understanding problems before solving them.

First is Widen Your Options. Narrow framing leads us to overlook options. We think in terms of “whether or not” decisions. Should we add overtime or not? Should we hire more people or not? Should we change software or not? But that binary thinking limits our ability to find better solutions. Instead, we need to think in terms of “and.” What are all the possible options? Can we consider multiple approaches simultaneously through multi-tracking?

Where do you find these new options? Look for bright spots where this problem has already been solved. Find someone who’s dealt with similar challenges and ask what worked for them. Look for analogies in other industries or projects. Ask an introvert to think about it and come back with perspectives you haven’t considered. The more options you generate, the less likely you are to get locked into a bad solution just because it was the first one proposed.

Second is Reality Test Your Assumptions. Confirmation bias leads us to collect skewed, self-serving information that supports the solution we already like. To combat this, ask disconfirming questions. What problems does this solution actually have? What data contradicts our assumptions? Zoom out and look objectively at costs, consequences, and outcomes. Run a choosing-by-advantages analysis that compares options on specific criteria instead of just going with gut feelings.

I learned this fixing surveying and control problems on big construction projects. The more data I collected, the better solutions I found. I remember one huge civil project where I discovered the problem by analyzing GPS equipment data and their localization. They were 0.25 feet off in the localization, which told me the control points were skewed and the GPS wasn’t recognizing the skewed coordinate system. Instead of assuming what was wrong, I collected data until I understood what was actually happening. That’s reality testing your assumptions.

Third is Attain Distance Before Deciding. Short-term emotion tempts us to make choices that are bad in the long term. To avoid this, shift perspective before deciding. What would you tell your best friend to do in this situation? What would your successor do? Give it time. Ask introverted team members to process and come back with their analysis. When decisions are agonizing, clarify your core priorities and make choices that align with them instead of reacting emotionally.

Especially if you’re an extrovert, you’ll struggle with this. You want to decide now. You want to talk it through and move forward. But that urgency creates bad decisions when problems aren’t clear yet. Get some distance. Step out of the emotion. Shift your perspective so you can see what’s actually going on before committing to solutions.

Fourth is Prepare To Be Wrong. We’re overconfident about how the future will unfold. We think we know exactly how our solution will work. But we should always ask ourselves from the beginning: could we be wrong about this? Accept that possibility instead of getting married to your decision. Be ready to adapt if you’re wrong or to accept someone else’s opinion as you head in a better direction.

Here’s what this process looks like in practice:

• When someone brings you a problem, resist the urge to immediately propose solutions • Ask clarifying questions that help everyone understand what’s actually causing the issue • Generate multiple options by asking people with different perspectives and looking for bright spots • Reality test those options with data and disconfirming questions before choosing • Get emotional distance before deciding, especially on high-stakes choices • Acknowledge you might be wrong and stay open to adjusting as you learn more

These aren’t delays. These are disciplines that prevent wasting months implementing solutions that don’t solve anything.

Why Taking Time Saves Time

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that clarifying problems before solving them isn’t slow leadership. It’s the only way to avoid implementing solutions that waste everyone’s time by missing the actual issue.

The vision for this approach is that you should be able to move forward with your team using the best information together, but by first defining the problem very clearly. Start there. This is our problem. Let’s understand it completely before we start solving it. Then with that problem clearly defined, ask what all our options are for solutions. Ask different types of people. Get some distance. Reality test these options. Make sure you have all the possibilities. Assume you could be wrong. And you’ll get to better solutions that actually work because they address real problems instead of imagined ones.

Think about the alternative. When you jump to solutions without understanding problems, you end up implementing fixes that don’t work, which means you have to revisit the problem again later after wasting time and credibility. Taking time to clarify problems upfront actually saves massive amounts of time downstream by ensuring your solutions address what’s actually wrong.

The Challenge: Define One Problem Clearly This Week

So here’s my challenge to you. This week when someone brings you a problem, stop yourself before proposing solutions. Ask clarifying questions. Take time to understand what’s actually happening. Generate multiple options. Reality test your assumptions. Get distance before deciding. And prepare to be wrong.

Read “Decisive” if you want the full framework. But even without the book, you can start practicing the core principle: clarify the problem before you solve it. Give your introverts time to process. Collect data before making assumptions. Ask disconfirming questions. Look for bright spots where this problem has already been solved. And resist the cultural pressure to appear decisive by jumping to quick answers.

The world doesn’t need more leaders who make fast decisions. It needs more leaders who make right decisions. And right decisions start with understanding problems deeply before proposing solutions.

As Peter Drucker wrote, “The most serious mistakes are not being made as a result of wrong answers. The true dangerous thing is asking the wrong question.” Don’t solve wrong problems quickly. Solve right problems carefully. That’s how you lead teams that actually improve instead of just staying busy implementing solutions that don’t work.

On we go.

Frequently Asked Questions

How do I balance taking time to clarify problems with the need to make timely decisions?

Clarifying problems doesn’t mean endless analysis. It means asking the right questions before committing to solutions. Most problem clarification takes hours or days, not weeks. The time you invest upfront saves weeks or months of implementing wrong solutions. Speed without accuracy just means you’re wrong faster.

What if my team culture values quick decisions and sees taking time as weakness?

Then your culture is rewarding activity over results. Show them the cost of implementing solutions that don’t solve actual problems. Track how much time gets wasted revisiting issues because solutions missed the real problem. Culture changes when people see evidence that better processes produce better outcomes.

How do I get introverts to contribute if they need time to process?

Give them time. Don’t expect everyone to think out loud in meetings. Send problems ahead so introverts can analyze before discussing. Create space for written input. Ask them directly for their perspective after they’ve had time to think. The best insights often come from people who need time to process before speaking.

What if we genuinely don’t have time for the full WRAP process?

Start with just one element. Before deciding, ask “what are we missing?” or “could we be wrong about this?” Even minimal process improvement prevents some bad decisions. But recognize that “not having time” often means you’ll waste more time later fixing problems that wrong solutions created.

How do I know when we’ve clarified the problem enough to start solving it?

When everyone can state the problem clearly and agrees that’s actually what’s happening. When you have data supporting your understanding. When you’ve looked for disconfirming evidence and found your understanding holds up. When the solution space becomes obvious because the problem is so clear. Clarity feels different than confusion dressed up as confidence.