Are You Fixing Problems or Just Reacting to Them Over and Over?

There is a version of continuous improvement that feels productive but changes nothing. You run a plus delta at the end of every meeting. You collect the feedback. You write it on the board. And then the next meeting, the same comments show up again. And the next meeting after that. And the one after that. The problems are being surfaced. They are just not being fixed. Jason Schroeder calls this one of the most expensive patterns in construction, and it is hiding inside some of the most well-intentioned lean efforts on job sites today.

The Difference Between Reacting and Fixing

Jason drew a sharp line in this episode between two very different responses to a problem. The first response is reactive. Something comes up in a huddle, a look-ahead review, or a plus delta. You acknowledge it. You handle that specific instance. You move on. The problem comes back next week because nothing structural changed. The second response is systemic. Something comes up and instead of handling the instance, you ask: what needs to change in the process, the culture, the behavior, or the system so this does not come back?

He used a procurement example to make this concrete. Say your six-week look-ahead keeps surfacing the same issue: materials are not on site when the work needs them. You can scramble to find the materials that week and feel good about putting out the fire. Or you can step back and ask whether your procurement log is actually being managed, whether you have a weekly procurement meeting in place, and whether the designer approval loop has been leveled out. One response fixes the instance. The other fixes the system. Only one of them keeps the problem from coming back.

The same principle extends to every corner of the project. A trade partner leaves a pile in the wrong zone and creates a roadblock in the morning huddle. You can move the pile. Or you can look at whether your visual constraint board is working, whether the right people are tracking roadblocks consistently, and whether the conditions that produced the pile are going to produce it again next week. Reactive thinking handles what happened. Systemic thinking handles why it keeps happening.

Why Stability Feels Boring and Why That Is the Point

Jason was direct about the perception problem here. The systems that keep problems fixed, the procurement log, the quality process, the daily huddle, the coverage schedule, the safety walk, the organizational standards, are not exciting. They are not the butterflies and kittens of lean culture conversations. They are the boring disciplined work that makes a project feel stable, clean, and uneventful. And uneventful is exactly what you want.

He shared something that has happened to him more than once. A superintendent tells him they stopped running the daily huddle because it felt like there was nothing left to talk about. And Jason wants to scream. That silence is not a sign that the huddle is unnecessary. It is evidence that the huddle has been working. The problems are staying fixed. The project is stable. The system is doing exactly what it was designed to do. Stopping the system because it appears to no longer be needed is how the problems come back.

This is the core of what Jason means when he says stabilize before you optimize. You cannot optimize a project that is not stable. You cannot squeeze more efficiency, better flow, or higher quality out of a system that is still lurching from one reactive firefight to the next. Stability is not the backdrop for the real work. It is the work. And the systems that create it are not overhead. They are the foundation everything else is built on.

Here are the system categories Jason pointed to as the ones that keep construction projects stable and problems from recurring:

• Personal organization systems for every person on the project team
• Team coverage, balance, and health so no single person is a single point of failure
•  Remarkable safety, cleanliness, and site organization maintained daily
•  Operational control through meeting structures, huddles, and visual management
•  Takt planning driving the schedule with flow and rhythm

When these five things are in place and running consistently, a project becomes what Jason described: clean, calm, focused, and boring in the best possible way. And when a genuinely difficult problem does surface, the team has the capacity and the clarity to address it fully rather than triaging it on top of twenty other fires.

The Personal Dimension

Jason brought this principle into his own life as well, and it is worth noting because it reveals something important about how he applies it. He acknowledged that in building Elevate Construction he has made mistakes. Missed calls. Missed meetings. Things he is not proud of. But his response to each of those instances is not just to apologize and reschedule. It is to ask what he did structurally, culturally, or behaviorally that allowed it to happen, and then change that thing so it does not happen again.

That is the same question a great superintendent asks every time something goes wrong on a project. Not just how do we fix this, but what needs to change so we never have this conversation again. The leaders who build that habit at a personal level are the same ones who build it into their project cultures. And the projects that run on that habit are the ones where the daily huddle feels routine, the site always looks the same, and the work just keeps flowing forward.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

The Challenge

Look at your last three plus deltas or huddle debriefs and ask one honest question: are the same issues showing up every time? If they are, you are reacting. Pick one recurring problem this week and ask what system change would keep it fixed permanently. Build that change. Protect it. Run it consistently. Boring is not failure. Boring is the goal.

“Standardization is not an end in itself. It is a means to an end.” W. Edwards Deming

On we go.

FAQ

What is a plus delta and why does it matter?

A plus delta is a meeting reflection where the team identifies what went well and what could be improved. It only creates value if the deltas are tracked and acted on structurally, not just acknowledged and repeated week after week.

What does stabilize before optimize mean?

It means you cannot improve a system that is not yet stable. Get the foundational systems running consistently first. Optimization on top of instability just produces faster chaos.

Why should you keep running huddles when the project feels smooth?

Because the smoothness is the huddle working. Stopping the system because problems are staying fixed is exactly how the problems come back.

How do I know if I am reacting versus fixing?

Ask whether the same problem has come up more than once. If it has, the instance was handled but the system was not changed. That is a reaction, not a fix.