The Levers You Can Pull for Change – Part 1

A Lever, Not a Guess: Why Systems Thinking Changes How You Fix Construction Problems

A Lever, Not a Guess

Picture a balance scale. On one side sits the entire system you are trying to change, a project, a company, an industry. On the other side sits a row of twelve pressure points, ranked from weakest to strongest, that determine how much leverage you actually have to move that system.

That image comes from Donella Meadows, and it reframes something every builder eventually runs into. Change in a complex system almost never comes from randomly pulling on whatever lever is closest. It comes from knowing exactly which lever you are pulling, and how much weight it actually carries.

The Real Pain: Fixing Symptoms One at a Time

Most teams do not approach change this way. A schedule slips, so someone adds a meeting. Costs run over, so someone adds another approval step. Quality suffers, so someone adds another inspection.

Each fix feels reasonable in isolation. None of them ask the deeper question: what is this system actually designed to produce, and is that even the outcome we want? Without that question, teams end up making dozens of small adjustments that never touch the real source of the problem.

The Failure Pattern: Pulling the Weakest Levers

Meadows’ framework ranks leverage points from weak to strong for a reason. Numbers, parameters, and buffer sizes sit near the bottom. They are the easiest to change and the least powerful, which is exactly why most organizations default to them.

Paradigms and goals sit near the top. They are harder to touch, but they carry far more weight, because changing a goal changes everything beneath it: the rules, the structure, the information flows, all of it. Teams that only ever adjust the weak levers stay stuck making the same mistakes with slightly different numbers attached.

A few low-leverage habits tend to show up in teams stuck in this pattern, and they are worth naming honestly:

• Adding more meetings or more approval steps instead of asking why the current process keeps producing delays.
• Extending the schedule or adding manpower instead of examining whether the plan was ever realistic in the first place.
• Changing a policy’s wording without changing the mindset or goal the policy was actually built to serve.

This Isn’t a People Problem, It’s a Leverage Problem

None of this means a team is careless or unwilling to improve. Most people were simply never taught to look at a system’s paradigm or goal before reaching for a fix. They were taught to solve the problem in front of them, which is a reasonable instinct, just not always the most effective one.

The system failed them by never showing them where the real leverage lives. Once a team understands that paradigms, mindsets, and goals sit at the top of that lever, the whole approach to problem solving changes.

The Delivery Rule and the Wallet Story

Here is what that looks like in practice. On one project, the rule was simple: if a delivery arrived late and got in the way of another trade, it got turned around, no exceptions. Some people on that job saw that rule and assumed leadership was simply being difficult.

So during a morning huddle, the response was to pull out a wallet and ask a direct question. If someone reached in and took a couple hundred dollars in cash, would that be acceptable? Everyone agreed it would not. Then came the connection: when a rogue delivery blocks another trade’s crew, and five or six workers sit idle for an hour at forty to eighty-five dollars an hour in burdened labor that is not an inconvenience that is real money taken from real people.

That single conversation did more to shift the mindset on that project than any written policy could have. It did not just enforce a rule, it changed how people saw the paradigm behind the rule, which is exactly the kind of high-leverage move Meadows describes.

Why It Matters: You Can’t Fix a Symptom the System Is Built to Produce

This distinction matters far beyond one delivery rule. It explains something much bigger about why construction, as an industry, keeps getting the same disappointing results year after year. As Jason likes to say, borrowing from his friend Hal Macomber, systems are perfectly designed to achieve the results that they are getting.

Look at how many projects in the United States finish late, and ask what goal the current system is actually optimized for. A schedule format that is dense, siloed, and hard to read in a courtroom does not accidentally survive for decades. It survives because an opaque, hard-to-litigate schedule serves the goal of shifting risk downstream rather than the goal of finishing on time. A visual, transparent plan like a Takt plan makes delays and responsibility obvious to everyone, which is precisely why systems built around avoiding accountability tend to resist it.

None of this is really about individual people being dishonest. It is about a contracting system whose actual goal, whether anyone admits it out loud or not, has quietly become risk avoidance rather than on-time delivery. Until that underlying goal changes, no amount of software, extra meetings, or schedule tweaks will fix it, because the system is already accomplishing exactly what it was built to accomplish.

Teach the Framework: Where the Real Leverage Lives

Meadows organizes twelve leverage points into a few categories: physical events like buffer sizes and constants, informational patterns like feedback loops and information flows, system structure like rules and structure itself, and, at the very top, the mindsets and paradigms a system springs from.

Paradigms are the deepest lever of all, the shared, often unstated assumptions a system is built on. A company whose paradigm is pure profit will make different decisions than a company whose paradigm is blessing the lives of the people it serves, even facing the identical problem. Mindsets are the individual beliefs people hold within that paradigm, and they can shift even when the paradigm itself stays the same, which is exactly what happened with the wallet story above. Goals sit just below paradigms and mindsets, and changing a goal cascades down through every rule, structure, and feedback loop beneath it.

Before touching any system, three questions are worth asking in order, and they are worth keeping close at hand:

• What is the paradigm this system was built on, and do the people inside it actually share it?
• What individual mindsets exist inside that paradigm, and could shifting them change the outcome?
• What is this system’s actual goal, not the stated one, but the one its current results suggest it is really optimized for?

Turning This Into Daily Practice

The good news is that the highest-leverage tools available are often simple and already within reach. Morning huddles, orientations, and onboarding are not just administrative checkboxes, they are one of the most direct ways to shape mindset inside a project’s paradigm, the same way the wallet story did.

A simple plus-delta exercise illustrates this well. Asking “what did you like and dislike about this meeting” targets a completely different goal than asking “did we accomplish the purpose of this meeting, and where did we fall short.” Same format, same five minutes, but a different goal produces a different outcome entirely.

Connecting It Back to Building People, Not Just Projects

None of this happens without leaders who are willing to look past the nearest fix and ask harder questions about paradigm, mindset, and goal. That is a different kind of training than teaching someone to read a schedule, and it is just as important.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow, starting with the mindsets and goals that shape everything else on the job.

The Challenge

So here is the challenge worth carrying into your next team meeting: before you reach for another policy tweak or another meeting to fix a problem, stop and ask what your system’s actual goal seems to be, based on the results it keeps producing. As Jason likes to say, borrowing from his friend Hal Macomber, systems are perfectly designed to achieve the results that they are getting. If you do not like your results, the goal, not the schedule, is probably the place to start. On we go.

FAQ

What are Donella Meadows’ leverage points, in simple terms?

They are twelve places you can intervene in a complex system, ranked from weak to strong. The weakest are things like numbers and buffer sizes, and the strongest are the paradigm and mindset a system is built on, along with the goal it is actually pursuing.

Why do paradigms and goals carry more leverage than rules or numbers?

Because changing a goal or a paradigm cascades down through everything beneath it, including the rules, the structure, and the information flows a system uses. Changing a number or a buffer size only affects that one component, which is why it takes far more effort for far less lasting change.

What does it mean to say a system is “perfectly designed to get the results it’s getting”?

It means that current outcomes, good or bad, are not random accidents, they are the natural output of how the system is actually built and what it is actually optimized for. If the results are disappointing, the fix has to start with the system’s real goal, not just its surface-level processes.

How does the delivery rule story connect to systems thinking?

Simply announcing a rule changes very little if people do not understand or agree with the paradigm behind it. Reframing the rule around respect and real financial impact shifted people’s mindset within the existing paradigm, which is a much higher-leverage move than just repeating the rule louder.

How can a project team start applying this without reading the whole book?

Start with the three questions: what paradigm is this system built on, what mindsets exist inside that paradigm, and what is the system’s real goal based on its actual results. Asking those questions before reaching for a fix is often enough to reveal where the real leverage lives.