Dependence, Feat. Hal Macomber & Felipe Engineer

The Production Laws Problem: Why Your Project Keeps Failing Laws You Never Learned

You’re running a project. Making decisions every day. The deck crew needs another day, so you extend just that piece of the schedule. The project falls behind, so you add more people. The electrician is waiting for information, so they start anyway and guess. Every decision seems reasonable. Practical. Based on years of experience. And every decision is violating production laws that govern how work actually flows. Laws you’ve never been taught. Laws that determine whether your project succeeds or fails regardless of how hard you work.

Here’s what Hal Macomber taught Jason Schroeder and Felipe Engineer Manriquez in St. Louis after they just walked past five scrum boards to get to a conference room on a multi-million-dollar Takt-planned project. These production laws have been around since the 1920s. A British engineer wrote about mass production and flow production. That material got into Toyota’s hands around 1945 to 1950. The rest of the world didn’t learn about it for decades. And most superintendents still don’t know these laws exist. Which means they’re violating them constantly, wondering why their projects struggle despite their best efforts.

The projects that succeed consistently aren’t led by superintendents who work harder. They’re led by people who understand the production laws that govern how work flows. Who know that Little’s Law says smaller batch sizes always produce faster throughput. Who recognize that bottlenecks are about capacity, not critical paths. Who’ve learned that variation stacks and compounds with dependence in ways that destroy projects. Who understand Kingman’s formula: cycle time multiplied by capacity utilization multiplied by variation effects equals overall duration. Who’ve discovered that fixing overburden first, then variation, then waste is the sequence that actually works.

The Problem Every Superintendent Creates

Walk onto any struggling project and you’ll find the same pattern. Decisions that seem reasonable are violating production laws. The superintendent extends just the deck schedule because that’s where the delay occurred, never recognizing that isolating one piece increases variation throughout the system. Leadership adds more people to recover schedule, never understanding that this violates Little’s Law and Brooks’s Law simultaneously. The electrician starts work without complete information because waiting seems wasteful, never seeing that this creates decision fatigue and compounds variation. Every decision makes sense in isolation. And every decision violates laws that determine project outcomes.

Most superintendents don’t recognize they’re violating production laws. They think they’re making practical decisions. Experience-based choices. Reasonable responses to field conditions. They frame intuitive management as good leadership instead of recognizing it as violation of fundamental principles. They don’t see that their “common sense” is breaking laws as real as gravity, laws that can’t be violated without consequences.

The pattern shows up everywhere in construction. The project team adjusts isolated pieces of the schedule instead of moving everything together to maintain rhythm, violating the law of variation without realizing it. Leadership focuses on eliminating waste before addressing overburden and variation, following Toyota’s misdirection instead of their actual practice. Superintendents push for one hundred percent utilization thinking efficiency equals productivity, never understanding that high utilization plus high variation creates massive delays. Everyone’s violating laws they’ve never been taught.

Think about the parade of trades in a seven-step operation. The first step finishes early but got off to a slow start. If they got off to a slow start, the second step doesn’t have as much work in process to do. They can’t do better than the slow start the previous person had. Variation compounds with dependence. If you’re reliable at a rate of 0.9, ninety percent of what you said you’d get done, 0.9 to the seventh power is a really small number. When percent promises complete drops below fifty percent, you can have people early in the process that are high, but there’s no way the painter at the end can be high because you’ve got all that compounded variation.

The painter at the end of the process bids the job to spray and back-roll the first two coats, roll the third. How often does that happen? It doesn’t. Do they lose money? No, because they bid based on experience. If they actually get to spray and back-roll the first two, they’re in the money. But it doesn’t happen because they’re at the long end of a chain that could be twenty or twenty-five or twenty-eight operations with compound dependence. That’s one of the fallacies, superintendents early in the process thinking that down the chain time can be made up. It can’t. Variation compounds.

The Failure Pattern Nobody Recognizes

This isn’t about lazy superintendents or incompetent teams. This is about violating production laws nobody taught you existed. That intuitive management breaks fundamental principles. That experience-based decisions violate laws as real as physics. That the system never equipped you with the knowledge required to succeed.

Construction culture treats intuition as sufficient for management. The superintendent who makes decisions based on feel. The project manager who relies on experience. The leadership team that trusts gut instinct. These patterns look like wisdom, like practical knowledge, like real-world expertise. And they’re dangerous because they replace systematic understanding with guesswork, production laws with hope, and knowledge with intuition that’s almost always wrong.

So superintendents make reasonable decisions that violate Little’s Law. They focus on waste elimination while ignoring overburden and variation. They push for high utilization without understanding its relationship to delay. They adjust isolated pieces of schedules without recognizing how variation stacks. They never learn that variation doesn’t offset, it stacks. That early slow starts can’t be made up later because variation compounds with dependence. That the production laws governing their work have been known for a century but never taught to them.

Nobody teaches superintendents that pursuing flow is the preferred way of doing any production work. That architects and engineers getting out of flow have the same problems, rework, losing track of what they were doing, their humanness showing up. That the law of variation is so powerful that Toyota normalizes arrival rates on highway onramps with stoplights every six seconds just to reduce variation in the rightmost lane. That Kingman’s formula explains why the middle two highway lanes during rush hour are generally better than the rightmost lane (high variation) or leftmost lane (high utilization).

A Story From the Field About Discovering Production Laws

Jason Schroeder sat down with Hal Macomber and Felipe Engineer Manriquez in St. Louis. They’d just walked past five scrum boards, five different teams using systematic approaches to manage work. Jason had been implementing production laws for three weeks without fully understanding them. His life had already changed. But he needed to understand why these things worked.

Hal started with history. These laws aren’t new. A British engineer in the 1920s wrote about mass production and flow production. Toyota got that material around 1945 to 1950. The rest of the world didn’t learn about it for decades. In 1999, Lean Construction Institute white paper number three said we must use a continuous flow approach, that’s the ground floor, with Last Planner on top to make flow work. That same year, Hal did his first Takt plan project at the Neinan Company in Fort Collins, Colorado. They completed an entire middle school in seventeen weeks using Takt planning and onsite prefabrication.

Jason interrupted, he does that, with an observation that feels revolutionary but isn’t. “I feel like we’re getting back to what was always supposed to be. When somebody says, ‘Oh, we pre-fabricated onsite,’ they act like it’s some new thing. It’s not new. The Hensel Phelps Pentagon renovation used Takt. The Empire State Building used certain things that were line-of-balance, location-based, Takt-ish. These are decades, hundreds of years ago. I think it’s what it was always supposed to be.”

Hal taught the law of variation. Every human being is born with amnesia, they don’t know what was done before them. The systems we encounter are complex. We have variation and chaos in how we procure and build. To bring order back, you need someone to increase awareness of what production laws are. If your project needs superintendent coaching, project support, or leadership development to understand and apply production laws instead of violating them through intuition, Elevate Construction can help your field teams stabilize, schedule, and flow.

He explained that Toyota teaches waste, variation, and overburden in that order. But Hal told Jim Womack in 1999: “You got it backwards. You need to do it in the other order: overburden, variation, and then waste.” Why? Because in construction, there’s already so much systemic pressure on people trying to do their best. Deming said the worker is just trying to do their best with best efforts, but it’s not enough because of how the system operates on them, sometimes operates against them. When you remove overburden from people, you create capacity to look at variation and understand how it’s wreaking havoc. Then you can get better about removing waste to enable flow because now you have breathing room.

Hal used the highway analogy to teach Kingman’s formula. During rush hour, two lanes on a four-lane highway have the highest delay: the rightmost lane (high variation from people getting on and off) and the leftmost lane (high utilization from everyone trying to go fast). The middle two lanes are better because they have lower utilization and are positioned to absorb variation. Major metropolitan areas deal with the rightmost lane variation problem by putting stoplights at onramp bottoms, green every six seconds, normalizing the arrival rate so variation doesn’t ripple through traffic.

How does that apply to construction? You’ve got to look at any given crew and the operations they perform in a period of time. How much of that time do they need to be working? On the Pentagon remodel, those wedges were five-day wedges. For the most part, everybody needed four and a half days to do the work, except Selfland Industries when they first worked there. They had five and a half days of work. There’s no way to get building access late in the day or on Saturday to pick up that half day. Selfland had to reduce their cycle time through improvements and prefabrication. They learned how to purposefully always get it done in four and a half days. That buffer protected them from variation.

Why This Matters More Than Working Harder

When you violate production laws you don’t know exist, working harder makes things worse. More effort applied to broken systems amplifies dysfunction. Longer hours violating Little’s Law extend duration instead of shortening it. Better intentions while violating the law of variation compound problems instead of solving them. The production laws govern outcomes regardless of effort, intention, or experience.

Think about Little’s Law. Smaller batch sizes always produce faster throughput. If you’ve got a batch of ten, at any point in time you’re only working on one, nine are idle. Drop that to batches of five and only four are idle. Get it down to one and you never have anything idle. With the same number of people, it goes through faster. Yet superintendents routinely create massive batches thinking efficiency requires scale, violating Little’s Law constantly without knowing it exists.

Think about bottlenecks. They’re about capacity, not critical paths. On a Toyota Camry production line with ninety-second Takt time, there might be one hundred operations. No more than fifteen percent operate close to seventy-five seconds. Many are in the low sixties. One or two might be below sixty. Making improvements to operations below sixty doesn’t help flow. Making improvements to the dozen operating at seventy-two seconds improves the speed of the line. With Takt planning, you find your bottleneck, establish pace based on what the bottleneck activity can do, and everybody falls in line with higher capacity on their wagon than the limiting operation.

Think about variation stacking. People think variation offsets each other. It doesn’t, it stacks. Variation compounds with dependence. When you’ve got twenty or twenty-five or twenty-eight dependent operations, that 0.9 reliability rate becomes minuscule by the end. The painter at the end can never recover time lost early in the sequence because variation has compounded through every dependent handoff. Yet superintendents in the honeymoon phase lose time thinking it can be made up later. It can’t.

Think about Kingman’s formula. Cycle time multiplied by capacity utilization multiplied by variation effects equals overall duration. If electricians can do overhead in a three-thousand-square-foot area in five days at one hundred percent capacity with no variation, that’s your baseline. Add eighty percent utilization from overtime fatigue and you’re at six-point-two-five days. Add variation from coordination failures and you’re at eight or nine days. The five-day task became nine days because you violated production laws trying to go faster.

The Framework: Learning and Applying Production Laws

The goal isn’t memorizing formulas. It’s understanding fundamental principles that govern how work flows so you can make decisions that work with these laws instead of against them. Building systems that respect production laws instead of violating them through intuition.

Little’s Law says smaller batch sizes produce faster throughput. Limit work in process. Finish as you go. Prepare work ahead of time. Make work ready for people and people ready for work. The paradox that Nicholas Modig and Par Ahlstrom write about in This Is Lean gets resolved, there isn’t a tradeoff when work is ready for people and people are ready for work. You have both flow and high productivity. The problem is construction doesn’t take seriously the make-ready planning process used in Last Planner System.

The law of bottlenecks says identify and optimize capacity constraints systematically. Think about Takt wagons. You establish pace, say two days, for all work on given flow units. Inevitably, most people on those wagons can perform better than two days, but some are the limiting ones bottlenecking you. You’ve set the pace for the whole line based on the bottleneck activity. Everyone else has higher capacity on their wagon. You could add blocking to framer wagons that doesn’t interfere with other work. Or you provide standby capacity, when every fifth wagon has a three-bedroom-plus-den apartment needing another framer, you pull somebody off workable backlog for two days, then return them.

The law of variation says variation stacks and compounds with dependence. Variation in something as simple as window systems over long walls requires engineering to take up tolerances. If you’re plus-or-minus a half-inch and twenty elements are each plus-an-eighth, you now have a problem. Variation doesn’t offset, it stacks. With Takt, you take out variation of pace and frequency of performing. You now have drumbeat. That train has no variation, every two days that car is in a different spot. You’ve taken out variation so there’s no compounding even though dependence still exists.

Address overburden first, then variation, then waste. Overburden shows up as eighty-pound cement bags when OSHA limits are fifty pounds. As cranes loaded beyond capacity. As eleven decisions required every time someone installs parts five hundred times per shift, creating decision fatigue that produces errors. Toyota reduced decisions from eleven to five by kitting interior parts together, everything in the tote is sandal-colored, not mixed with gray. That’s twenty-five hundred fewer decisions per person per shift. Take care of overburden first so people have capacity to see and address variation.

Kingman’s formula: cycle time × capacity utilization × variation effects = overall duration. On the Pentagon, Selfland learned to always finish in four and a half days instead of five and a half because variation would push them over otherwise. They needed buffer within their cycle time to absorb variation. If you’re highly utilized, using almost all available time, and you have variation that causes you to go over, you ruin yourself. Know your utilization. Know your variation. Build buffer to absorb variation instead of planning to one hundred percent utilization with no margin.

The Practical Path Forward

Here’s how this works in practice. You’re making a decision on your project. Before executing it, ask: does this violate production laws?

Am I creating large batches when Little’s Law says smaller is faster? Am I pushing isolated schedule pieces instead of moving everything together to maintain rhythm? Am I ignoring bottlenecks by improving non-limiting operations? Am I increasing variation instead of reducing it? Am I pushing utilization to one hundred percent without buffer for variation? If any answer is yes, find a different approach.

Study the laws systematically. These aren’t basic concepts, they’re fundamental principles that reveal themselves deeper the more you investigate. Jason walked into that conversation having implemented production laws for three weeks. His life had already changed. But sitting with Hal and Felipe, he kept discovering new applications. The law of variation alone opened his eyes to where it shows up in cycle times, project management, instructions, and schedules, everywhere. Investigate thoroughly like Musashi taught.

Apply them in sequence: overburden, variation, waste. Don’t start with waste elimination like most Lean teaching suggests. That was Taiichi Ohno’s misdirection to maintain competitive advantage. Start with overburden, remove systemic pressure so people can breathe. Then address variation, create rhythm and stability. Then eliminate waste, now that you have capacity and stability to see where waste actually exists and how to remove it without breaking flow.

Build systems that respect these laws. Takt planning takes out variation of pace. Make-ready planning addresses Little’s Law by preparing work before starting it. Bottleneck analysis identifies where to focus improvement. Buffer built into cycle times absorbs variation. These aren’t separate systems, they’re integrated approaches respecting production laws instead of violating them.

Why This Protects Projects and People

We’re not just building projects. We’re protecting jobs, families, and futures from the dysfunction that violating production laws creates. And whether we learn and apply these laws or keep violating them through intuition determines whether we build sustainable success or chronic failure.

When you violate production laws, you’re not just hurting efficiency. You’re overburdening people, compounding variation that destroys their work, forcing them into unsustainable patterns. The electrician who had to guess and do rework because the architect didn’t share information wasn’t lazy or incompetent—the system reinforced behaviors where starting and billing was prioritized over having complete information. That’s a production law violation that harms people.

When you understand and apply production laws, you’re protecting everyone. Overburden gets removed so people can do their best work. Variation gets controlled so handoffs are predictable. Batch sizes get optimized so work flows instead of stalling. Capacity gets right-sized with buffer for variation instead of pushed to one hundred percent. People can succeed because systems respect fundamental laws instead of violating them.

Respect for people means building systems based on production laws instead of intuition. It means learning the principles that govern work so decisions work with reality instead of against it. It means stopping the amnesia where every generation rediscovers through pain what was documented a century ago.

The Challenge in Front of You

You can keep making intuitive decisions that violate production laws. You can keep trusting experience built on broken systems. You can keep working harder within approaches that fundamentally don’t work. You can wonder why reasonable decisions produce unreasonable results.

Or you can learn production laws. You can study Little’s Law, the law of bottlenecks, the law of variation, Kingman’s formula. You can understand why overburden first, then variation, then waste is the sequence that works. You can build systems respecting these laws instead of violating them. You can make decisions based on principles instead of guesses.

The projects that succeed consistently aren’t led by superintendents who work harder. They’re led by people who understand production laws. Who know these aren’t basic concepts but fundamental principles revealing themselves deeper the more you investigate. Who’ve learned that what seems reasonable often violates laws as real as gravity. Who’ve discovered that systematic understanding beats intuitive management every time.

These laws have been known since the 1920s. Toyota has built competitive advantage on them since the 1940s. Construction is just starting to rediscover them. You can be part of that rediscovery or keep violating laws you don’t know exist.

Investigate this thoroughly.

On we go.

Frequently Asked Questions

What are the five core production laws and why do they matter?

Little’s Law: smaller batch sizes produce faster throughput, limit work in process, finish as you go. Law of Bottlenecks: identify and optimize capacity constraints, not non-limiting operations. Law of Variation: variation stacks and compounds with dependence, it doesn’t offset. Kingman’s Formula: cycle time × capacity utilization × variation effects = overall duration. The overburden-variation-waste sequence: address overburden first so people have capacity to see variation, then eliminate waste to enable flow. These aren’t suggestions, they’re laws governing how work flows that you violate at your peril.

Why should I address overburden before variation and waste?

In construction there’s already massive systemic pressure on people trying to do their best. Deming said best efforts aren’t enough when the system operates against you. When you remove overburden from people, you create capacity to look at variation and understand how it’s wreaking havoc on your system. Then you can get better about removing waste to enable flow because now you have breathing room. Toyota taught waste-first to maintain competitive advantage, it was misdirection. The actual sequence that works is overburden, then variation, then waste.

How does variation compound with dependence in ways that destroy projects?

In a seven-step operation, if you’re reliable at 0.9 (ninety percent), 0.9 to the seventh power is a really small number. Early slow starts can’t be made up later because variation compounds through every dependent handoff. The painter at the end of a twenty-operation sequence can never recover time lost early. That’s why they bid assuming they won’t get to spray and back-roll, they price in the compounded variation they know is coming. Superintendents in the honeymoon phase lose time thinking it can be made up. It can’t. Variation stacks—it doesn’t offset.

What does Kingman’s formula mean practically for my project?

If a task takes five days at one hundred percent capacity with no variation, that’s baseline. Add eighty percent utilization from fatigue and it becomes six-point-two-five days. Add variation from coordination failures and you’re at eight or nine days. The five-day task became nine days because you violated production laws. Selfland on the Pentagon learned this—they needed four-and-a-half-day actual work in five-day Takt wagons because variation would push them over otherwise. If you’re highly utilized with high variation, you ruin yourself. You need buffer within cycle time to absorb variation.

How do I start learning and applying these laws on my projects?

Study them systematically—these reveal themselves deeper the more you investigate. Read This Is Lean by Modig and Ahlstrom. Study Toyota’s actual practices, not just their public teaching. Implement Takt planning to remove variation of pace. Use Last Planner System for make-ready planning that respects Little’s Law. Analyze bottlenecks to focus improvements where they matter. Build buffer into cycle times for variation absorption. Before any decision, ask: does this violate production laws? If yes, find a different approach that works with these laws instead of against them.