Don’t Just Do Something, Stand There

Don’t Just Do Something, Stand There

Here’s the deal. There is a quote I want credit going to the right place for. Hal Macomber said it, and Adam Hoots is who reminded me of both the line and who said it. Don’t just do something, stand there. I love this quote, and I think it captures one of the most misunderstood ideas in all of construction.

Who gets credit for a good idea matters far less than whether the idea actually gets used. This one deserves to get used constantly, because it corrects a mistake that costs real money on almost every jobsite in America.

Why Keeping Everyone Busy Is a Bad Goal

Go back to Eliyahu Goldratt’s thinking on full kit and flow, and a specific truth becomes clear. People trying to look busy is a bad thing, not a good one.

Here is the example that makes it concrete. Picture a factory that needs a throughput of four parts an hour. The equipment on the line has different production rates: four parts an hour, then four, then two, then four, four, four, four. If you tell every single piece of equipment to run at its own maximum speed regardless of the others, you actually end up with something like one point two to one point eight parts an hour of real throughput. Everyone working flat out produces the worst result on the list.

If you double the capacity of that slow two part per hour machine, your throughput can reach the full four parts an hour the system needs. Alternatively, if you deliberately slow every other machine down to match that same two part per hour pace, running the faster machines only half the time, your throughput becomes two parts an hour. Slower on paper for most of the equipment, but a better real number than the chaos of everyone running full speed independently. Full speed everywhere is the worst option on the table, and matched pace beats maximum busyness every single time.

The Excavator Story That Makes This Real

Here is my favorite illustration of this, because it happens on real jobsites constantly. Picture an excavator operator on a civil crew who comes up to an unknown pipe that might or might not be in the way of the planned trench. The crew needs to figure out how to proceed, and rather than staying with the problem or stepping out of the cab to help solve it, the operator decides to go look busy somewhere else, wanting to impress the boss with visible activity.

Watch what actually happens next. Diesel gets burned for no productive reason. Equipment takes wear and tear it did not need to take. The work done elsewhere is now uncoordinated and has to be reworked, because it was not planned as part of the sequence. A pile that got moved during that detour is now sitting in the wrong spot, blocking something else. The equipment risks breaking down doing unplanned work. And once the original crew is ready to continue, they now have to wait for the operator to come all the way back and get reoriented to the actual problem, on top of whatever finished work got run over or disturbed during the detour.

All of that dollar waste happened because staying busy felt more valuable in the moment than standing still and solving the actual problem. It was not.

Watch for these signs someone is optimizing for looking busy instead of for flow:

• A worker or piece of equipment relocating to unrelated work the moment the original task hits an unknown or a problem
• A crew treating idle time as inherently bad, even when the alternative is uncoordinated, unplanned activity
• Finished work getting disturbed or reworked because someone needed something to do in the meantime

Stop, Call, Wait

There is a phrase worth adopting directly from this. Stop, call, wait. Sometimes having a worker actually wait is the better outcome. Sometimes a foreman not actively working is the better outcome. Sometimes a zone sitting temporarily idle is the better outcome, because the alternative is pushing ahead without full kit or without a clear plan, and pushing a defect or an uncoordinated decision down the line is far more expensive than the appearance of lost time in the moment.

This connects directly to something worth holding as a standing habit on any project. If you see, hear, or sense something is not right, the correct response is to stop, call the right people in, and wait for a real answer before proceeding, not to keep moving in some other direction just to avoid looking idle.

Why “Don’t Just Stand There, Do Something” Gets Us in Trouble

Here is the instinct working against us. Our default in the United States tends to run the opposite direction. Don’t just stand there, do something. That instinct, so deeply ingrained that it feels like common sense, is exactly what produces the excavator story above, over and over, on jobsites everywhere.

The correct instinct runs the other way. Don’t just do something. Stand there until you actually know what you are supposed to do, which comes down to preparation, doing the work correctly the first time, and staying in a genuine flow rather than filling time with activity that has not been thought through. Worrying more about whether the work is actually flowing than whether everyone looks occupied is the entire shift in mindset this quote is pointing toward.

Resource Efficiency vs Flow Efficiency

There is a real framework behind why this works, described by researcher Niklas Modig as the distinction between resource efficiency and flow efficiency. Resource efficiency asks whether every person and every piece of equipment is being used as much as possible. Flow efficiency asks whether the actual work is moving smoothly and completely through the system.

Those two goals are not the same, and optimizing for the first one frequently damages the second. A jobsite obsessed with resource efficiency keeps everyone visibly busy and produces uncoordinated rework, wasted material, and wear on equipment that did not need to happen. A jobsite that genuinely prioritizes flow efficiency accepts that a worker standing still, a foreman not actively swinging a tool, or a zone temporarily unworked can be exactly the correct state, because the actual measure of success is whether work moves cleanly through the system, not whether every second looks productive on the surface.

Building This Into How Your Team Operates

None of this works if it stays a clever quote nobody actually applies under pressure. The instinct to look busy runs deep, and it takes real discipline, and real permission from leadership, to let a crew stop and wait when that is genuinely the correct move.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build the discipline to prioritize flow over the appearance of busyness, including giving crews explicit permission to stop, call, and wait when a real problem shows up instead of filling the gap with unplanned activity. That permission has to come from leadership directly, because nobody wants to be the person standing still if they think it will be read as laziness.

So here is the challenge. Think about the last time someone on your project filled idle time with unplanned activity rather than stopping to solve the actual problem in front of them. Calculate honestly what that decision actually cost in rework, wasted material, or lost coordination. That number is usually a lot larger than the cost of simply standing there and waiting for the right answer.

Jason Schroeder said it plainly: “Stop, call, wait.” Sometimes the most productive thing a worker can do is exactly nothing, until the real problem gets solved.

On we go.

FAQ

Isn’t it always better to keep workers and equipment busy to maximize productivity?
No, and this is the core misunderstanding the quote addresses. Keeping every resource maximally busy regardless of the actual bottleneck in the system frequently produces worse total throughput than intentionally matching pace to the true constraint. A factory or jobsite optimized purely for resource utilization can end up slower overall than one that accepts some idle time in exchange for coordinated, planned flow.

What should a worker actually do when they hit an unexpected problem instead of finding other work to look busy?
Stop, call the right people in to look at the problem, and wait for a genuine resolution before proceeding, rather than moving to unrelated work in the meantime. Staying present with the problem, or stepping in to help solve it directly, avoids the uncoordinated rework, wasted material, and equipment wear that come from filling the gap with unplanned activity elsewhere.

What is the difference between resource efficiency and flow efficiency?
Resource efficiency measures whether every person and piece of equipment is being used as much as possible at any given moment. Flow efficiency measures whether the actual work is moving smoothly and completely through the system from start to finish. Optimizing heavily for resource efficiency often damages flow efficiency, since keeping everyone busy regardless of coordination tends to produce rework and waste that slows the overall project down.