Building Better Solutions: A Practical Framework for Problem Solving

FIELD NOTES BY MATTHEW CURRY, PROJECT MANAGER

There is a myth in our industry that problem-solving is a talent reserved for the corner office. That the superintendent, the project executive, or the seasoned owner is the one who “figures it out” while everyone else waits for direction. In reality, the best-run projects I have seen are the ones where problem-solving happens at every level, from the laborer who flags a conflict before it becomes a rework order to the PM who reframes a schedule crisis into a phasing opportunity.

The difference between people who solve problems well and people who just react to them is rarely intelligence. It is discipline. A repeatable way of thinking that keeps you from jumping to the first fix that comes to mind.

Here is a simple four-question framework that works whether you’re running a $200M program or coordinating a single trade partner in the field.

1. What is the problem? (Big picture, not data)

Most of us are trained to reach for numbers first. The concrete is three days late. The RFI has been open for two weeks. The budget line is 8 percent over. Those are symptoms. They are important, but they are not the problem.

The real skill is stepping back far enough to name what is actually happening. “The concrete is late” is data. “We do not have a reliable way to confirm material readiness before we commit crews” is a problem. One points you at a single delivery. The other points you at a pattern you can actually fix.

Before you touch a spreadsheet, be able to say the problem out loud in one plain sentence that anyone on the job site would understand. If you can’t, you’re still looking at symptoms.

Field truth: Naming the problem clearly is the majority of solving it. Ambiguity is where projects go to die.

2. How does this relate to us? (Impact, and why we should care)

Field truth: If you cannot explain why a problem matters to the person you need help from, you will be solving it alone.

3. What are my options? (Solutions, not more problems)

4. What happens after the solution? (Consequences of the action)

Every fix creates a new reality. The mark of a mature problem solver is thinking one move past the solution.

If you accelerate this trade, what does it do to the one behind it? If you approve the substitution to save time, what does it cost in warranty or owner relationship down the line? If you fix it yourself instead of coaching the person who should own it, what does that teach them for next time?

This is also where accountability lives. Deciding is not the end. Someone owns the action, someone confirms it worked, and someone captures what we learned so we are not solving the same problem on the next project. The teams that improve year over year are the ones that treat the consequence step as seriously as the decision itself.

Field truth: Solving a problem without anticipating its consequences is just relocating the problem.

Why this matters at every level

The reason this framework travels across every title in our industry is that it’s not about authority. It’s about ownership.

A first-year field engineer who can name a problem, explain its impact, offer options, and think through consequences is more valuable than a twenty-year veteran who only knows how to escalate. And a leader who models these four questions instead of just barking answers builds a team of problem solvers rather than a team of order-takers.

Construction is, at its core, thousands of problems solved in sequence under pressure. We will never eliminate the problems. What we can control is how well, and how consistently, we think our way through them.

So the next time something goes sideways on your project, resist the urge to react. Ask the four questions.

Do that consistently, and you won’t just solve more problems. You’ll become the person others trust to solve the ones that matter most.