Flow Efficiency

Resource Efficiency vs. Flow Efficiency: Why Keeping Equipment Busy Is Destroying Your Schedule

Walk any construction site and ask the superintendent how things are going. You’ll hear the same answer everywhere. “We’re good. Equipment’s running. Crews are working. Everyone’s busy.” Then ask when the work will be finished. When the customer can take occupancy. When the flow unit will actually reach completion. And suddenly the answer gets vague. Maybe three weeks. Could be six. Depends on a lot of things.

Here’s what’s happening. The superintendent optimized resource efficiency. He made sure every piece of equipment stayed busy. Every crew had work. Every department was loaded. Individual resources are operating at maximum utilization. But the work isn’t flowing. Materials pile up between operations. Crews wait for handoffs. Areas sit incomplete while everyone moves on to keep busy. The project looks productive but nothing’s actually finishing. You optimized the wrong thing.

The Problem Hiding Behind All the Busyness

Here’s the pattern on most projects. A superintendent looks at idle equipment and thinks “waste.” He sees a crew without work and thinks “inefficiency.” He notices a department with downtime and thinks “poor utilization.” So he loads them up. He keeps everyone busy. He optimizes resource efficiency. And work slows down. Because keeping individual resources busy isn’t the same as getting work to flow. In fact, they’re often opposites. When you optimize resource efficiency, you create inventory between operations. You create waiting. You create handoffs. You create complexity. All of which slow down the flow of work from start to finish.

Think about Ford versus Toyota. Ford used to keep assembly lines running at maximum capacity, producing cars whether customers ordered them or not. Keep the equipment busy. Maximize resource utilization. The result? Massive inventory. Storage costs. Defects. Overproduction. Transportation waste. All because they optimized individual resource efficiency instead of flow efficiency.

Toyota said we have limited space, limited money, limited resources. We can’t waste anything. So if we get an order for three hundred seventy-five cars, we’ll produce four hundred, switch the tools, and make something else. We’ll reduce changeover times. We’ll only produce what the customer wants when they want it. We won’t keep equipment busy for the sake of being busy. We’ll attach people and resources to work that needs to flow, not attach work to people to keep them busy.

The System That Trains Us to Optimize the Wrong Thing

This isn’t about lazy superintendents or bad decisions. This is about an industry that measures the wrong metrics and rewards the wrong behaviors. Construction culture celebrates utilization. The superintendent who keeps every crew working. The project manager who loads every department. The company that bills maximum hours. We measure resource efficiency obsessively and barely track flow efficiency at all. So people do what gets measured. They optimize individual resource utilization. They keep equipment running. They batch work to maximize crew efficiency. They level workload within departments instead of leveling flow across the entire system.

And work piles up. Between the grading crew and the pipe crew. Between the architect’s review and the supplier’s fabrication. Between submittal approval and material delivery. Between overhead rough-in and wall framing. Everywhere you look, work in process accumulates because everyone optimized their own individual efficiency instead of optimizing the flow of work through the entire system. The system failed them. It didn’t fail the workers.

A Story That Reveals the Difference

I worked with a civil contractor in Jacksonville, Florida, that has some of the most advanced business systems in construction. They measure everything. They support field workers extensively. They’re deep into their lean journey. A team recently told me they were having trouble on a project. They just felt like work wasn’t flowing. So they all stood outside and watched the work. They took videos. They did a flow analysis. They got the team working together to make sure work was actually flowing instead of just keeping resources busy. They quadrupled their production.

Not by adding more equipment. Not by increasing crew sizes. Not by working longer hours. By optimizing flow instead of optimizing individual resource utilization. By attaching people to work that needed to flow instead of attaching work to people to keep them busy. They sent the results back to corporate with their production numbers. The president said “This is exactly what we need.” Because seeing flow, actually watching whether work is moving through the system efficiently, is what changes everything.

Why This Matters More Than Equipment Utilization

When you optimize resource efficiency over flow efficiency, work gets stuck everywhere. Think about submittals. Most projects treat the submittal process as a series of individual departments each optimizing their own efficiency instead of a flow that needs to move quickly to get information to workers.

The trade partner batches all submittals and sends them at once because that’s efficient for their detailer. The general contractor queues them up according to when it’s convenient for the project engineer to review them. The architect prioritizes them based on their own workload instead of when workers need the information. The supplier processes them according to their production schedule. Every department optimizes its own individual efficiency. And the submittal sits for weeks. The information doesn’t reach the worker when needed. The material doesn’t arrive in time. Work stops waiting for approvals that are stuck in queues designed for resource efficiency, not flow efficiency.

Now imagine the same submittal process optimized for flow. Don’t batch all submittals at once. Send them one package at a time according to when workers need them in sequence. Don’t queue them for review when convenient. Swarm them when they arrive so they move through quickly. Don’t wait weeks for architect review. Invite them to tabletop reviews or virtual sessions to turn them around in real time. Don’t let them sit in supplier queues. Track them and push them through. The second approach might feel less efficient for individual departments. The detailer can’t batch everything. The project engineer might have uneven workload. The architect has to coordinate schedules. But the submittal flows to the worker faster. The information arrives when needed. Work doesn’t stop waiting. That’s flow efficiency.

Signs Your Project Is Optimizing the Wrong Thing

Watch for these symptoms that you’re prioritizing resource efficiency over flow efficiency:

• Equipment stays busy grading entire sites or working everywhere at once, but areas sit incomplete for weeks waiting for the next trade to start because work in process accumulated instead of flowing
• Crews jump between multiple areas to stay utilized, but nothing finishes completely because everyone’s optimizing individual efficiency instead of completing flow units
• Submittals batch in large packages to maximize detailer efficiency, then sit in queues for weeks because every department optimized its own workload instead of information flow to workers
• Project teams level workload within offices to keep everyone equally busy, but RFIs and procurement requests stack up waiting for review because internal efficiency destroyed external flow
• Materials arrive in bulk orders to maximize delivery efficiency, then pile up on site creating congestion and damage because supplier scheduling ignored installation sequence

The Framework: What Flow Efficiency Actually Means

Flow efficiency means optimizing how fast work moves from start to finish through the entire system. Resource efficiency means optimizing how busy individual resources stay. You want both, but when you have to choose, flow efficiency wins.

Here’s why. In the book The Goal, a factory has equipment operating at full individual efficiency. But it creates bottlenecks because it’s overproducing inventory between machines. When they stop focusing on keeping every machine maximally utilized and start focusing on flow through the entire system, production increases dramatically. They slow down some machines to match the bottleneck. They reduce work in process. They optimize the whole instead of the parts.

Construction works the same way. When a contractor says “I want to order, deliver, and install all the ductwork at once because that’s efficient for my crew,” they’re optimizing resource efficiency. They’re not worried about burying other trades under materials. They’re not worried about creating work in process. They’re not worried about flow through the entire building. They’re keeping their crew and equipment busy.

When that same contractor says “How can I sequence my work to optimize flow for the entire project?” they’re thinking differently. Maybe that means delivering materials just-in-time in smaller batches. Maybe that means smaller crew sizes working in sequence instead of large crews working everywhere at once. Maybe that means coordinating with other trades to maintain flow even if it creates slight inefficiency for individual resources.

The Japanese principle is clear: don’t attach work to people, attach people to work. Don’t load up resources to keep them busy. Focus resources on work that needs to flow. Everything should flow to the worker.

Practical Examples of Prioritizing Flow Over Resource Efficiency

Think about how this plays out on actual projects. A grading contractor has sixteen pieces of equipment and wants to keep them all running. So they grade the entire five-hundred-acre site at once to maximize equipment utilization. Resource efficiency looks great.

But now you’re maintaining five hundred acres. Running water trucks across massive areas. Managing SWPPP everywhere. Regrading damaged pads. Dealing with rain exposure. You created work in process everywhere instead of focusing equipment on the areas where pipe installation is ready to start. You optimized resource efficiency and destroyed flow efficiency.

Or think about project management teams. The project manager levels workload within the office, making sure all engineers stay equally busy. Resource efficiency within the department looks optimized. But submittals sit in queues. RFIs wait for review. Procurement gets delayed. Information doesn’t flow to workers when needed because the office optimized its own efficiency instead of optimizing flow to the field.

The shift is simple. Instead of asking “Is this equipment busy?” ask “Is work flowing to completion?” Instead of “Are my crews fully utilized?” ask “Is the flow unit moving through the system efficiently?” Instead of “Is my department loaded evenly?” ask “Is information reaching workers when they need it?”

Takt planning lets you see both resource efficiency and flow efficiency simultaneously. You can watch work flow through areas while also seeing how crews flow from area to area. But even with Takt, you prioritize flow efficiency. If you have to choose between keeping a crew busy in the wrong area or accepting slight downtime to maintain proper flow sequence, you choose flow.

The Paradigm Shift: Everything Flows to the Worker

Here’s the fundamental shift in thinking. Right now, most people focus on their own area of responsibility and optimize efficiency within that silo. Superintendents optimize their field operations. Project engineers optimize their office workflow. Trade partners optimize their crew utilization. Equipment operators maximize machine time. Everyone optimizes locally. Nobody optimizes globally. And work gets stuck at every handoff because the handoffs weren’t designed for flow. They were designed for individual resource efficiency.

The new paradigm is everything should flow to the worker. Not to the department. Not to the equipment. To the worker at the point of production who actually installs the work. Every decision gets filtered through: does this help work flow to that worker faster with higher quality? If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

This changes how you think about everything. Layout doesn’t optimize the surveyor’s efficiency. It flows to workers when they need it. Quality information doesn’t optimize the engineer’s schedule. It flows to crews before work starts. Materials don’t optimize the supplier’s delivery routes. They arrive just-in-time to support installation flow. Safety briefs don’t optimize the superintendent’s meeting schedule. They happen when and where workers need the information.

You can’t manage fifty flow units simultaneously. But you can focus on what’s starting in the next two to six weeks and make sure layout, information, quality processes, safety protocols, materials, workers, and equipment all flow to those starting scopes without interruption. That’s why Last Planner’s six-week make-ready and weekly work planning is genius. That’s why Takt planning works. They’re designed for flow efficiency first, resource efficiency second.

The Decision in Front of You

You can keep measuring equipment utilization, crew hours worked, and department loading. You can keep optimizing how busy individual resources stay. You can keep attaching work to people to prevent idle time. You can keep batching tasks for individual efficiency.

Or you can start measuring flow. How fast work moves from start to finish. How quickly information reaches workers. How efficiently materials arrive when needed. How smoothly handoffs happen between operations. How short the timeline is from raw material to installed work.

The projects that finish fast aren’t the ones with the highest resource utilization. They’re the ones with the best flow efficiency. They attach people to work instead of work to people. They optimize the whole instead of the parts. They watch work flow and remove anything that interrupts it.

The Shifts Required to Prioritize Flow

Making this transition requires changing how you think about several key areas:

• Stop batching submittals to maximize detailer efficiency and start sending packages one at a time according to when workers need information in sequence, even if it means the detailer has uneven workload
• Stop grading entire sites to keep equipment running and start grading just ahead of installation to reduce work in process, even if it means some equipment sits idle between phases
• Stop leveling workload evenly within office departments and start swarming critical path items to push them through quickly, even if it creates temporary uneven loading across project engineers
• Stop optimizing delivery routes for supplier efficiency and start delivering materials just-in-time to match installation sequence, even if it means more frequent smaller deliveries with higher per-unit transport costs

Nicholas Modic teaches this brilliantly in This Is Lean. Read that book. Watch his YouTube videos. Understand that everything you’ve been taught about maximizing resource utilization might be slowing you down. The goal isn’t keeping equipment busy. It’s getting work to flow.

Like juggling. A professional juggler doesn’t focus on all six balls at once. They focus on the ones in their hands and make sure handoffs are perfect. The balls in the air are self-sustaining because the transitions were managed well. Same with construction. You focus on work starting in the next short interval and make sure handoffs are clean. The work already flowing takes care of itself if you designed the system for flow.

Buy a red car and suddenly you see red cars everywhere. Learn about flow and suddenly you see every place it’s missing. Stop measuring busyness. Start measuring flow. Attach people to work, not work to people. Optimize the whole, not the parts. On we go.

Frequently Asked Questions

What’s the difference between resource efficiency and flow efficiency?

Resource efficiency optimizes how busy individual resources stay, like keeping equipment running or crews fully loaded. Flow efficiency optimizes how fast work moves through the entire system from start to finish. You want both, but flow efficiency takes priority because keeping resources busy while work sits stalled destroys schedules and costs.

How do you measure flow efficiency on a construction project?

Track how long it takes work to move from initiation to completion through the entire system. For submittals, measure days from package sent to information in workers’ hands. For materials, measure days from order to jobsite delivery. For areas, measure time from make-ready complete to work fully installed and inspected. Shorter timelines with less waiting mean better flow.

What’s an example of prioritizing resource efficiency destroying flow?

A grading contractor keeping sixteen machines busy by grading an entire five-hundred-acre site at once instead of grading just ahead of pipe installation. Equipment utilization looks great, but you’re maintaining massive areas, regrading damaged pads, managing SWPPP everywhere, and creating work in process instead of flow.

How does Takt planning help balance resource and flow efficiency?

Takt lets you see work flowing through areas left to right and crews flowing from area to area top to bottom. You can optimize both simultaneously, but Takt is designed to prioritize flow, so if crew utilization requires breaking flow sequence, you maintain sequence and accept slight resource inefficiency.

What’s the practical first step to shift from resource to flow focus?

Stop asking “Is this resource busy?” and start asking “Is work flowing to completion?” Watch work move through the system. Do a flow analysis like the Jacksonville team: stand outside, observe, take videos, identify where work stalls. Then remove those stalls even if it means accepting slight resource downtime to maintain flow.