The Waiting You Pay For and the Waiting You Don’t.

The Waiting You Pay For, and the Waiting You Do Not

Here’s the deal. There are two kinds of waiting on a construction project that look remarkably similar from a distance and carry completely different real costs. Learning to tell them apart changes how you should actually respond when you see a zone sitting idle or a worker not fully occupied.

What Triggers the Expensive Kind of Waiting

The waiting you pay for usually starts with someone in authority insisting on something that sounds reasonable on the surface. I want every worker busy. I want extra crews. I want overtime. I want every single zone being worked on at all times. That demand is exactly what creates the expensive version of waiting.

Waiting, in this context, means people standing around for information, for a roadblock to clear, for materials that have not arrived. It means genuine treasure hunts, searching for something that should have been staged properly. It means busywork invented simply to look occupied, or someone doing planning work that genuinely belonged to a project engineer instead.

A colleague once came back from a real Last Planner training with a useful way to frame this. It is either workers waiting on work, or work waiting on workers. Workers tend to wait constantly in construction, which is genuinely different from manufacturing, and one of those two situations is considerably worse than the other.

Why Niklas Modig’s Framework Is Missing a Third Category

Niklas Modig writes about resource efficiency and flow efficiency, and his work is genuinely excellent. Because he is not writing specifically about construction, he never fully pulls apart both extremes and explains the real middle ground between them. There is actually a third concept worth naming directly, work efficiency, sitting as its own distinct failure mode alongside resource efficiency.

Here is how these three genuinely differ from each other.

• Resource efficiency optimizes each individual piece of equipment or each individual trade on its own, which can quietly sub-optimize the overall project and hurt genuine flow.
• Work efficiency means keeping every single zone worked on constantly, so each area looks efficient within itself, which also ends up hurting overall workflow.
• Flow efficiency sits genuinely in the middle, matching the actual pace and capability of your resources with the genuine demand of the client, balancing supply and demand rather than optimizing either extreme in isolation.

A trade that wants the entire building to themselves, free to stage however they like because it feels maximally efficient for them individually, is actually detrimental to overall production. Insisting that every single zone must be worked on and every person must stay busy at all times is just as false, and it genuinely hurts people in the process.

Why Adding More Workers Does Not Automatically Create More Speed

When everyone tries to work at full efficiency inside every zone simultaneously, aggregated across an entire project, you get real trade stacking and genuine trade burdening. You end up throwing large numbers of people at work that may not even be ready for them yet.

Here is something I say constantly in trainings and conferences. You could add ten additional trained people to every single crew on a site and genuinely not go any faster, if the areas are not ready, if the overall system is not in rhythm, and if the materials or information required simply are not there yet. More labor thrown at an unready system does not create speed. It mostly creates cost.

If you are genuinely operating inside a real Takt production system, some zones will always, at any given moment, not be actively worked on. Some people will not be at one hundred percent capacity at every moment either. That is completely normal. The moment an owner notices this and demands that something be done about it without understanding why, that is exactly the moment a project tips into the expensive version of waiting.

Telling the Two Kinds of Waiting Apart

The waiting you pay for looks like this. Work is not genuinely made ready, and in response, additional crews get brought in, trades get stacked or burdened, extra workers show up, overtime gets authorized, and the whole team shifts into rushing, pushing, and panicking. That version of waiting is genuinely expensive.

The waiting you do not pay for looks completely different. A zone might sit waiting briefly for a crew because of a small natural gap, or because trades are genuinely moving at slightly different paces. A crew might even get intentionally reduced in size to match the pace of everyone else around them. Nobody is working at full individual efficiency in this scenario, and nobody is actually paying for it either, because the overall production plan still finishes at the soonest reasonable point, without panic, without additional overtime costs, without wasted treasure hunts, and without idle labor nobody can genuinely put to use.

Watch for these specific signs you are experiencing the expensive version of waiting rather than the genuinely harmless kind.

• Extra crews or additional labor brought in specifically because a zone sat briefly idle, rather than because the actual schedule genuinely required it.
• Overtime, time and a half, or double time costs appearing directly in response to pressure to keep every zone constantly occupied.
• A visible shift into rushing, pushing, or panicking triggered by an owner or executive noticing an empty zone without understanding why it is temporarily empty.

What I Am Not Actually Saying Here

I want to be genuinely clear about something. I am not saying work everyone at full resource efficiency, since that creates real gaps elsewhere in the schedule. I am also not saying focus purely on work efficiency, keeping every zone occupied at all times. What I am actually recommending is a genuinely balanced plan between those two extremes, landing on real flow efficiency.

If every trade simply does whatever is best for itself individually, that is sub-optimization, and it is genuinely harmful. If an owner insists there should never be an empty zone, demands overtime, and does not care about trade stacking or trade burdening, that is equally harmful. The genuinely intelligent, educated approach keeps everyone moving in real flow, optimized for the shortest overall throughput time and the highest quality, while still genuinely respecting the people doing the work. That balance is the only way to actually win.

Building This Understanding Into Your Own Project

None of this requires choosing one extreme over the other. It requires understanding that some amount of idle time, in a zone or in an individual worker, is genuinely normal and healthy inside a well run Takt system, and resisting the instinct to throw expensive resources at something that does not actually need fixing.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your teams genuinely distinguish between the waiting worth paying to eliminate and the waiting that simply reflects a healthy, well balanced production system.

So here is the challenge. The next time you notice an idle zone or an underutilized worker, pause before reacting. Ask honestly whether that gap reflects a real roadblock genuinely worth addressing, or a normal, healthy rhythm you would actually be paying real money to eliminate unnecessarily.

Jason Schroeder said it plainly: “Lean is about finishing a project or a phase at the shortest duration, highest level of quality, that takes care of our people, at the lowest overall total project cost.” Learn to tell these two kinds of waiting apart, and you protect every single part of that definition at once.

On we go.

FAQ

Why does the article argue that Niklas Modig’s resource efficiency and flow efficiency framework is missing something important for construction?

Because Modig’s work was not written specifically about construction, and it only fully explains one extreme, resource efficiency, alongside the balanced middle ground of flow efficiency. The article argues construction genuinely needs a third category named directly, work efficiency, to describe the opposite extreme of insisting every zone stay constantly occupied, which causes its own distinct set of problems.

Why would adding ten extra trained workers to every crew on a site not necessarily make the project move faster?

Because speed in a Takt system depends on zones being genuinely ready, the overall system being in rhythm, and materials and information actually being available when needed, not simply on how many people are physically present. Extra labor thrown at an unready system adds real cost without addressing the actual constraint slowing the project down.

What is the practical difference between a zone sitting idle due to “waiting you pay for” versus “waiting you don’t pay for”?

The expensive version involves a reactive response, extra crews, overtime, trade stacking, rushing and panicking, triggered by the idle zone itself. The non-expensive version involves a zone or worker genuinely not at full utilization simply because trades move at slightly different paces, with the overall schedule still finishing at the soonest reasonable point without any of those extra costs being incurred.

Why does the article warn against an owner reacting negatively to seeing an empty zone or an idle worker?

Because some amount of idle time is a completely normal, expected feature of a well functioning Takt production system, not necessarily a sign of inefficiency worth correcting. An owner who pushes a team to eliminate all idle time without understanding this risks triggering the expensive form of waiting, since that pressure typically gets answered with extra crews, overtime, and rushed decision making rather than genuine improvement.