What Construction Phrases Actually Mean: A Systems Thinking Wake Up Call

There is a Saturday Night Live sketch Jason Schroeder and his wife Katie reference often. A character says something that lands badly, then backtracks with “see, what I had said was…” The humor is in the gap between intention and actual meaning. That same gap exists all over the construction industry, and it is costing projects millions.

This episode is about thinking in systems. Not just taking contract provisions, owner requirements, and field directives at face value, but tracing the feedback loops they create and understanding what they actually produce.

What Systems Thinking Actually Is

The book Thinking in Systems by Donella Meadows defines a system as a grouping of stocks, flows, and feedback loops. When a stock changes, or when something affects the inflow or outflow of that stock, it creates a feedback loop that shapes behavior. Some of those loops are reinforcing, compounding in one direction. Others are balancing, pushing back against change. Either way, the system produces consequences that the original decision may never have intended.

The construction industry is full of systems that produce consequences their designers never anticipated or never acknowledged. The danger is not bad intent. It is the assumption that the phrase means what it sounds like, when the actual feedback loops tell a completely different story.

Six Phrases and What They Actually Mean

“We have a fixed fee in a GMP contract.”

On the surface: the contractor will be paid a fixed amount above cost, and costs are capped. Sounds like a reasonable arrangement that aligns incentives.

What it actually means in systems terms: the contractor is incentivized to keep more people on the project longer. If general conditions are chargeable against the GMP and the contractor earns labor gains on management positions, adding two or three people to the team and keeping them there longer generates additional fee. There is no incentive to finish early or run a lean team. There is also an incentive to transfer self performed labor costs from a lump sum concrete or framing scope into the main project budget, increasing reported project cost while reducing their reported self perform loss. The feedback loop rewards staying longer and spending more, not finishing efficiently.

“The designer says: we have a system that works for us. Just fit into it and we’ll release design as we finish.”

On the surface: the designer has an established workflow and wants to maintain it. Sounds like a reasonable request for continuity.

What it actually means: there will be no collaborative design process. The contractor and trade partners will react to design releases with costs, triggering a pinball cycle of the project being over budget, the designer wanting more scope, and the owner being forced through value engineering to reconcile the two. The designer’s feedback loop pushes them to include as much as possible to build a strong portfolio project for future work. The contractor becomes the villain for flagging the cost. Problems that could have been prevented in design get handed to the contractor to absorb in the field.

“We have shared float on the schedule.”

On the surface: both parties have access to schedule contingency and will manage it collaboratively. Sounds equitable.

What it actually means: the owner will consume the float for design changes, leaving none for legitimate contractor delays. The contractor, knowing this, will hide their contingency and maintain two schedules: one for the owner and one for actual project management. This is not dishonesty in isolation. It is the predictable result of a system that eliminates the contractor’s ability to protect legitimate delay claims. You now have policy resistance, tragedy of the commons, performance drift, and rule breaking: four system archetypes created by one clause.

“We need to competitively bid the project and get three prices for everything.”

On the surface: fiscal responsibility, good stewardship of someone else’s money. Sounds like the right thing to do.

What it actually means: selecting based on lowest cost rather than best value. The feedback loop in a lowest cost selection prioritizes the number that looks smallest at bid time, not the partner most likely to deliver on time, at quality, without contingency erosion. The lowest cost trade partner is often the one who missed scope, underestimated risk, or cannot perform at the level required. The contingency that was saved at bid gets consumed executing around failed vendors and trade partners. The system designed to save money costs more than it saves.

“Show me the critical path.”

On the surface: the owner or consultant wants to understand what is driving the schedule. Sounds like informed oversight.

What it actually means: attention is diverted from the actual causes of project delay. Projects do not delay because of a critical path activity. They delay because of broken flow, missing readiness, constrained trade access, and productivity problems at the task level. A focus on the critical path forces contractors to defend a theoretical model rather than address the real production system. It also allows owners to use the absence of a critical path hit as evidence that the contractor cannot claim delay, even when the project is clearly behind due to owner caused conditions.

“You need to add more manpower.”

On the surface: the project is behind, so more people should accelerate progress. Sounds like a logical response to a schedule problem.

What it actually means: the trade partner’s productivity will decrease. Adding workers to a constrained work area increases interference, coordination burden, and overhead. More people competing for the same space move slower, not faster. The escalation archetype takes over: the general contractor adds pressure, productivity drops, more manpower is demanded, productivity drops further, and the trade partner burns through their margin while the GC explains the delay to the owner. What the directive really means in practice: add people so it looks like progress is being made, which slows you down so we can blame you for the delay while your profit disappears.

A Critical Caution

Jason is direct about something important here. These are analyses of systems and their consequences, not accusations of bad intent. The owner who says “show me the critical path” may genuinely believe that is the right tool. The designer who wants to fit contractors into their workflow may not realize they are creating a design bid build dynamic. The GC who says “add manpower” may legitimately want to help.

Assuming negative intent is both unfair and unproductive. The work is to assume positive intent while being clear eyed about negative consequences. When you hear these phrases, the right response is not cynicism. It is a systems thinking question: what feedback loops does this create, and how do we design around the destructive ones while preserving the intent behind the request?

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. Understanding the systems underneath the phrases is one of the most powerful skills a construction leader can develop.

The Challenge This Week

Pick one phrase or provision from your current project that you have accepted at face value. Trace the feedback loops it creates. Ask what behavior it incentivizes. Then ask whether that behavior matches what everyone involved actually wants from the project.

As Donella Meadows wrote in Thinking in Systems, “Before you disturb the system in any way, watch how it behaves.” In construction, that watching starts with understanding what the words actually produce, not just what they were intended to mean.

On we go.

Frequently Asked Questions

How do you raise concerns about a destructive system without damaging the relationship?

Frame it around shared consequences, not blame. “I want to flag something about how this provision typically plays out, because I think it creates a dynamic that hurts both of us.” Most owners and designers have not traced these feedback loops themselves. Bringing the conversation as a shared problem to solve is more effective than presenting it as a grievance.

Is systems thinking a skill that can be learned, or is it just how some people think?

It is absolutely a learnable skill. The book Thinking in Systems by Donella Meadows is the clearest introduction available. Reading it once will permanently change how you hear construction decisions, contract provisions, and field directives.

What is the most common destructive system in construction projects today?

Based on what Jason observes across dozens of projects and companies: the combination of shared float and lowest cost selection. Together, they eliminate schedule transparency and bring in under resourced trade partners, creating the conditions for a project that crash lands regardless of how well the field team performs.

How do you protect your team from destructive feedback loops you cannot change?

By naming them explicitly in your project kickoff and planning conversations. When everyone on the team understands that a shared float provision will incentivize hiding contingency, they can make a conscious choice about how to respond rather than simply reacting to the pressure the system creates.

Can these same systems thinking principles apply to managing a crew or department, not just contracts?

Yes. Every policy, incentive structure, and communication norm creates feedback loops. A crew culture that punishes people for flagging problems will produce a crew that hides problems. A performance review system that  rewards busyness over output will produce busy but unproductive teams. The principles apply at every level of the organization.