When Everything Goes Wrong on a 450-Million-Dollar Project, Do This First

There is a moment on every major project when something does not fit. The pieces that should line up simply do not. The pressure is immediate, the stakes are enormous, and everyone around you is waiting for an answer. What happens next determines everything. Jason Schroeder lived this moment over a Thanksgiving holiday on one of the most technically complex projects of his career, and the lesson he brought back from it applies to every problem on every job site.

The Project and the Problem

The Phoenix Sky Harbor Airport guideway project was a 450-million-dollar infrastructure build connecting Terminal 4 to the East Economy lot and the 44th Street station. The structure used precast columns and girders to form an elevated guideway where rubber-tire trains would run along a central guide rail. Ride quality depended on precision. Everything had to be exactly where the design said it needed to be.

Construction was well underway when the team identified that something was wrong. Sections of the guideway were not aligning correctly. Rather than push forward and move defects downstream, the general superintendent made the call to stop. No more work until the problem was understood. That decision, as uncomfortable as it was, is what made everything that followed possible.

Jason described what it felt like to be called in over the Thanksgiving holiday with his family in tow, knowing that a project of this scale was waiting on answers. There was pressure from every direction to move fast, get to conclusions, and get people back to work. He resisted that pressure every single day of the investigation. The refusal to skip steps is what separated this outcome from a disaster.

The Investigation

The first move was not to fix anything. It was to traverse the entire site network, running a full survey loop from Terminal 4 through the East Economy lot and the 44th Street station and tying everything together within acceptable accuracy. People questioned whether there was really time for this level of thoroughness. Jason’s answer was yes, every time, without exception.

Once the traverse was established, the team took thousands of side shots to map the actual location of every edge, curb, and stem wall along the guideway. All of that data was plotted in AutoCAD against the design centerline. When someone suggested skipping the verification step of repeating data entries back aloud, Jason held the line there too. The data had to be right before any conclusion could be trusted.

The root cause emerged from a whiteboard brainstorming session. One segment had been laid out using GPS rather than a total station. When the team tracked down the person responsible, they found he had falsified a coordinate geometry system without telling anyone, rotating the grid because things were not matching up. GPS localization does not skew with a rotated coordinate system. It centralizes on the offset and shifts everything by half the error. A five-inch falsification produced a two-and-a-half-inch bust in the field, cascading through every curve derived from that setup.

The Fix

Once the root cause was confirmed, the team built a solution designed to preserve as much finished work as possible. The 44th Street station was already built to a high standard and its location could be made to work. The answer was a custom modified spiral for one specific guideway segment, a fabricated guide rail section matched to the modification, and updated primary control coordinates issued to every contractor on the project.

By the time crews returned from the holiday break, the fix was ready. Updated coordinate files were in everyone’s hands. The modified segment was defined. The project moved forward. The only rework required was in the section where the falsified GPS setup had caused the bust. Everything else was preserved.

This outcome was only possible because the team slowed down when everything was screaming at them to speed up. That is the core lesson, and it applies to every job site regardless of scale or complexity.

What Problem Solving Actually Looks Like

Jason laid out an eight-step framework from this experience that holds across any type of construction problem. Step one is defining the problem clearly before touching anything. Step two is clarifying the scope of what is actually wrong. Step three is defining the desired outcome so the team is solving toward the same target. Step four is identifying the true root cause rather than fixing the first visible symptom. Step five is developing the action plan. Step six is executing it together. Step seven is evaluating the results. Step eight is continuously improving so the same problem does not return.

He was equally clear about how problem solving should be structured as a team activity. Appoint a leader first. Then gather input from everyone. Then build the plan together. Then communicate it before anyone executes. Problems in construction do not belong to individuals. They belong to the team. The best information about what went wrong is distributed across the people closest to the work, and a whiteboard session where everyone contributes is how root causes that no individual would find on their own actually surface.

Here are the patterns that show up when teams handle crises well:

• They stop before they fix • They gather data before they guess
•  They stay calm when the pressure is highest
•  They appoint a leader and communicate the plan before executing
• They evaluate results rather than assume the fix worked

The temptation when things go wrong is to move fast and look busy. A principle worth carrying: if you had an hour to solve a problem, spend fifty-five minutes defining it and five minutes solving it. The leaders who resist the pressure to react prematurely find the actual problem and fix it for good.

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

The Challenge

The next time something does not fit on your project, resist the instinct to start fixing immediately. Gather your team. Appoint a leader. Collect the data before you reach for a solution. Stay calm even when the pressure is real, the holidays are coming, and a project worth hundreds of millions is waiting on you. The calm that feels like inaction is almost always what the situation actually needs.

“If I had six hours to chop down a tree, I would spend the first four hours sharpening the axe.” Abraham Lincoln

On we go.

FAQ

Why is defining the problem the most important step?

Because most tactical fixes address symptoms rather than root causes. Time spent truly defining the problem is the only reliable shortcut to a solution that actually holds.

Why does staying calm matter so much in a crisis?

Because panic leads to skipped steps, and skipped steps in a crisis amplify the original problem. Calm is not a personality trait here. It is a professional discipline.

What does it mean that problems belong to the team?

It means no one person should be isolated with a crisis and expected to solve it alone. The best information is always distributed across the people closest to the work.

How does this framework apply to smaller projects?

The scale changes but the steps do not. Define the problem, identify the root cause, build the fix as a team, and communicate the plan before executing. Every time.