Don’t Get Lopsided! Feat. Kevin Rice

The Aggregation of Marginal Gains: Why There Is No Single Magic Bullet in Construction

Someone is going to walk up to you at some point and offer you a deal that sounds very reasonable. Pick one thing, they will say. One area to focus on. One skill to sharpen. One system to implement. And you will improve. The problem is not that the advice is wrong. The problem is that construction does not work that way. A project does not fail in one area. It fails in the gap between seventeen things that all have to work at the same time. And the superintendent, project manager, or company leader who is waiting for a single breakthrough is going to keep waiting while the organizations willing to grind through every domain are already pulling away.

The Comfortable and Dangerous Idea

There is a seductive idea spreading through the construction improvement conversation. It sounds professional and measured when people say it out loud: let’s just pick one thing. Let’s not overwhelm the team. Let’s focus. Underneath that framing is a real problem, which is the belief that transformation is achievable through selective effort that a project or a person or a company can get to the next level by improving one isolated capability while leaving everything else exactly where it is. That is not how complex systems work. And construction is one of the most complex systems there is.

The Failure Pattern

The pattern shows up in companies that spend a year implementing one tool without addressing the conditions that make the tool effective. It shows up in superintendents who attend one training and come back to a project that still has all of the same structural problems it had before they left. It shows up in organizations that define their one thing for the year and then discover that the one thing depends on five other things they chose not to address. The gains from improving in isolation are real, but they are limited and often temporary. The system corrects back toward its old behavior because the surrounding domains were never touched.

The Instinct Is Understandable

This is not a criticism of anyone trying to make progress. Choosing to focus on one thing is often a rational response to feeling overwhelmed. When every domain needs attention and there are not enough hours or energy or resources to address all of them at once, narrowing the focus feels responsible. The problem is not the instinct to prioritize. The problem is believing that one improvement, done in isolation, is enough to move the whole system forward in a meaningful and lasting way. Complex systems do not respond to partial effort. They are interconnected in ways that make selective improvement unstable. That is a systems design problem, not a character flaw.

What a Cycling Coach Figured Out That Construction Has Not

In 2003, British cycling hired a coach named Dave Brailsford. The sport had not produced a Tour de France winner in its history. Gold medals were rare. The team was underperforming across the board. Brailsford’s theory, which Kevin Rice introduced on this episode and has been examining deeply as a business professional and owner, was not to identify the single biggest weakness and fix it. It was to identify every possible area where a 1% improvement was achievable and pursue all of them simultaneously. The suit. The helmet aerodynamics. The training protocols. The recovery nutrition. The paint on the inside of the team trailer. Sleep quality. Morale. More than twenty domains, each improved by the smallest measurable amount. Within a few years, British cycling was winning the majority of cycling gold medals at the Olympics and claiming Tour de France titles repeatedly.

What Brailsford understood, and what Kevin and Jason unpack in this conversation, is that the gains were not meaningful in isolation. A marginally better helmet does not win a race. A marginally better recovery protocol does not win a race. But when twenty or more domains are each marginally better at the same time, the compounding effect is transformative. The system as a whole becomes something it could not have been through selective improvement. That is the aggregation of marginal gains, and it applies to construction with as much force as it applies to cycling.

Why This Is the Right Framework for Field Leaders

This matters because the default conversation in construction improvement is still oriented around single solutions. Last Planner will fix the coordination problem. Takt will fix the schedule. A 5S initiative will fix site cleanliness. Those statements are all partially true. They are also all incomplete. A Takt plan in a team that has no capacity to execute it produces a well-designed schedule and nothing else. A Last Planner system in an organization that has not addressed procurement produces weekly planning meetings where the same constraints appear every week because the root cause was never resolved. Lean tools work inside systems that are ready for them. Getting the system ready requires attention to many domains, not one.

Focus on One Goal. Improve Every Lever.

The aggregation of marginal gains is not an argument against focus. It is an argument for understanding what focus actually means. Brailsford had one goal: go faster. Everything he did served that goal. The mistake people make is confusing the goal with the method. The goal can be singular. The method must be comprehensive. If a construction company sets a goal of improving field operations, that goal will not be achieved by addressing field operations alone. It will require better preconstruction, better procurement, better team health, better training, better meeting systems, and better leadership development, all pulling toward the same target. The goal is one. The levers are many.

Kevin Rice introduced a concept during this conversation that deserves its own attention: lopsidedness. A system becomes lopsided when improvement in one domain outpaces improvement in surrounding domains to the point where the imbalance creates new failures. The athlete with extraordinary upper-body development and underdeveloped legs looks impressive and performs poorly. The construction company with world-class scheduling and underdeveloped quality systems wins bids and loses margins. The superintendent with exceptional relationship skills and weak organizational systems builds crew trust and misses critical coordination deadlines. Lopsidedness is not a failure of effort. It is a signal that the system needs rebalancing. When something stops working, the question is not who to blame. The question is: what domain has been neglected while attention was concentrated elsewhere?

Here Is How to Start

Before applying any framework, take stock honestly of where your gaps are and where your effort has been concentrated:

• Define the one primary goal clearly: go faster, run better projects, develop better leaders. Keep the goal singular.
• List every domain that contributes to that goal, from procurement and team health to personal organization and technology skills.
• Choose one domain at a time, improve it by a measurable increment, and finish before moving on. Do not leave things at 95%.
• When progress stalls, ask what surrounding domain is creating a bottleneck. That is the next place to look.
• Work in 90-day intervals with a specific plan for what gets learned and what gets finished in that window.
• Recognize lopsidedness as a system signal, not as evidence that the goal is impossible.

Finish What You Start

The path to mastery is not a single breakthrough. It is the accumulation of many small ones, done sequentially and completed before moving to the next. The discipline is to take one domain, grind it to functional mastery, add it to the tool belt, and then move forward. When enough of those domains are completed and working together, what looks effortless to an outside observer is the result of years of compounded effort.

Jason’s version of this is one-piece flow applied to skill development. Starting seventeen different learning efforts at once and making 5% progress on each is not aggregation of marginal gains. It is fragmented effort that produces no completed capabilities. When Jason set up Elevate Construction, building the podcast alone required learning Libsyn, audio editing, on-camera delivery, outline structure, research, upload protocols, and more than thirty other components. When he and his team came back from Sweden and were asked to set up a recording studio with a green screen, chroma key compositing, video editing, and audio processing in less than a week, there was no other option but to grind through each piece one at a time until the system worked. That studio now produces content in minutes. That is what mastery looks like from the outside. From the inside, it was thirty-five separate skills, each taken to functional completion.

Built for People, Not Just Projects

The reason this conversation matters beyond theory is that the construction industry has real people in it who want to grow and do not have a clear picture of the path. A young superintendent who wants to be a general superintendent one day but cannot open Excel is not failing. They are missing a framework for how mastery is actually built. A company that keeps implementing new systems without seeing lasting results is not incompetent. They are pursuing transformation through selective effort in a complex system that requires balanced investment. The North Star of this work is building people who build things. That is not achieved through one program or one tool. It is achieved through the aggregation of every marginal gain available to every person willing to show up and do the work. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Make the List and Start Grinding

Knowledge is not power. Action is power. The person who understands the aggregation of marginal gains and does nothing with it is in exactly the same position as the person who never heard of it. The person who makes a list, works in 90-day intervals, finishes what they start, and rebalances when lopsidedness appears will be a different person in two years. As James Clear wrote in Atomic Habits: if you get 1% better every day for a year, you will end up thirty-seven times better than when you started. The math is not motivational. It is literal. Start the list. Pick one thing. Finish it. Then pick the next.

On we go.

FAQ

What is the aggregation of marginal gains and where does the idea come from?

The concept was popularized by Dave Brailsford, the British cycling coach who took a historically underperforming team and transformed them into one of the most dominant cycling programs in the world. His method was to identify every possible domain related to performance, from equipment and nutrition to sleep quality and team morale, and improve each one by 1%. The individual gains were too small to measure meaningfully in isolation. Compounded across twenty or more domains and sustained over time, they produced a system that was dramatically better than any single-domain improvement could have created. Kevin Rice and Jason Schroeder applied this framework to construction in this episode, arguing that mastery in any field comes from the same approach.

Why is improving just one thing at a time not enough in construction?

Because construction is a complex system where every domain is connected to every other. Scheduling depends on procurement. Procurement depends on preconstruction quality. Field execution depends on team health and capacity. Quality depends on training and standard work. If any one of those domains fails, it creates pressure on all the others. Improving scheduling while leaving procurement dysfunctional produces a better-looking plan and the same material delays. Improving field leadership while leaving preconstruction weak produces better-managed problems that should never have existed. The system needs balanced attention, not selective focus, to move forward in a stable and lasting way.

How do you know when your system is becoming lopsided?

Kevin Rice and Jason both land on the same honest answer: you know because you stop winning. When a project keeps hitting the same failure point, when a company keeps losing money in the same place, when a superintendent keeps running into the same coordination problem, the system is signaling that one domain has been neglected while attention was focused elsewhere. The lopsidedness becomes self-evident because the gains in the improved areas start being erased by losses in the underdeveloped ones. That is the moment to stop, assess all the contributing domains, and identify which one is now the limiting factor.

How does this apply to individual skill development for superintendents?

Directly and without exception. A superintendent who wants to advance to general superintendent needs more than one skill. They need scheduling competence, technology literacy, quality management, safety leadership, communication skills, financial awareness, people development capability, and more. Improving one of those in isolation while leaving the others undeveloped produces a lopsided leader who performs well in one context and struggles in all the others. The path is to identify all the domains required for the target role, make a list, and work through them systematically in 90-day intervals, finishing each one before starting the next. That is how mastery is actually built.

What does one-piece flow have to do with learning new skills?

One-piece flow is the principle of completing one unit of work fully before starting the next. Applied to skill development, it means taking one learning domain to functional completion before starting another. The failure mode Jason describes is starting seventeen different improvement efforts at once and making partial progress on all of them without finishing any. Partial progress does not add to the tool belt. A skill that is 90% developed is not available when you need it. Finishing each domain and making it functional before moving forward is what allows the gains to actually aggregate. The list keeps getting longer. The tool belt keeps getting heavier. Eventually, the compounding effect of many completed capabilities produces mastery that looks effortless from the outside.