Don’t Just Do Something – Stand There! Feat. John Coffman

“You Can Never Do That”

Picture a concrete pour going sideways. Trucks are backed up five and six deep, a general superintendent is out there kicking rocks and throwing his hard hat, and a quality control manager runs in right behind him to help fix it. Together they dive straight into the chaos and, eventually, get it sorted out.

Later that afternoon, the project manager called both of them into his office and asked what happened. After hearing the story, he said something neither of them ever forgot: you both ran straight into the middle of that pour and started doing stuff, and neither one of you had a clue what was actually happening yet. He compared it to walking into a forest and only being able to see the trees immediately in front of you. You cannot see the flow of what is really going on until you stand back far enough to see the whole picture first.

The Real Pain: Running In Without Knowing What’s Happening

This happens constantly in construction, and it rarely looks like a mistake in the moment. Something goes wrong, word travels fast, and the instinct is to move immediately, get to the site, get hands on, get involved.

The problem is that arriving fast and arriving informed are two completely different things. Running toward a crisis before understanding it usually means reacting to whatever is loudest or most visible, which is not the same as understanding what is actually causing the problem.

The Failure Pattern: Confusing Motion with Leadership

The failure pattern looks like urgency, but it is not the same thing as effectiveness. Yelling, throwing a hard hat, jumping straight into the middle of a crew without knowing what they are already handling, all of it feels like decisive leadership in the moment.

In practice, it often produces nothing but noise. As one superintendent put it plainly after learning this lesson the hard way, doing it the old way would have meant running out there, jumping right on top of the person already working the problem, demanding to know what happened, and accomplishing absolutely nothing except making a lot of dust.

A few signs tend to show up when motion is getting confused with real problem-solving, and they are worth checking honestly:

• Arriving at a problem and immediately starting to physically do the work, rather than first understanding what has already been tried.
• Raising your voice or visibly venting frustration before anyone has confirmed what actually caused the issue.
• Assuming the person already on site does not know what they are doing, without first observing what they are actually doing.

This Isn’t About Being Slow, It’s About Seeing Clearly First

None of this means the instinct to jump in fast comes from a bad place. It almost always comes from genuinely caring about the outcome and wanting to help as quickly as possible. The problem is simply that speed without observation usually slows things down rather than speeding them up. That instinct can be retrained, the same way any habit gets retrained, by building in one deliberate pause before acting.

The Paving Crew and the Bull Float

Here is what that retraining looks like under real pressure. On a large paving job pouring three million square feet of concrete, word came in that a pour was going badly enough that inspectors expected the whole thing to need to be torn out. The instruction from the inspectors was blunt: get out there and fix it.

Instead of running straight into the crew, the response was to stop, stand back, and simply watch what was happening before touching anything. What became clear from that distance was that the area superintendent already had it under control in every way that mattered. He had slowed the paver, slowed the batch plant, and kept only enough concrete on the ground to keep the leading edge alive. He was not failing, he was simply short on people to keep the finishers caught up. A single radio call brought in a truckload of extra finishers from a subcontractor within a half hour. In the meantime, rather than taking over or second-guessing the superintendent already running the show, the response was to pick up a bull float and become one more set of hands until help arrived. The inspectors were confused, expecting to see someone come in and take charge. Instead, they got a problem that was already under control, just short-staffed, and now it was not anymore.

Why It Matters: The Cost of Running In Blind

This matters because running in blind carries real costs beyond wasted energy. It can undercut the person already working the problem correctly, waste time chasing the wrong fix, and leave the actual root cause completely unaddressed while everyone feels busy putting out what looks like a fire. Worse, it teaches a crew that leadership shows up to create noise rather than to help, which erodes trust exactly when a team needs it most.

Teach the Framework: The Battle Perch and the Ohno Circle

This lesson has a name in Lean thinking, and it goes back to Taiichi Ohno, the inventor of the Toyota Production System. Ohno would draw a chalk circle on the factory floor and ask a new engineer or team leader to stand inside it, sometimes for half a day or longer, and simply watch without stepping out to intervene. The goal was to strip away the instinct to solve before truly seeing, to stop pattern-matching to a pre-made answer, and to actually observe what was happening at the real place of work.

The construction version of that same discipline is standing far enough back to see the flow of an entire operation rather than the isolated piece directly in front of you. For a small crew, that might mean fifty feet. For a large pour with multiple trucks and crews working together, it might mean fifty yards. The distance is not the point, the clarity it produces is. Only from that vantage point can you tell the difference between a crew that is struggling because something is broken and a crew that is simply short-handed and already doing everything right.

A few practical questions turn this into something usable in the moment, before ever stepping toward a problem:

• What has the person already in charge of this situation already tried, and is it actually working?
• Am I about to intervene because something is genuinely broken, or because it simply looks chaotic from a distance?
• What does this team actually need from me right now, more hands, more information, or simply more time?

Turning This into Daily Practice

This does not require a dramatic pause every time something goes wrong. A daily reflection walk, observing the flow, energy, and pace of a project before reacting to any single issue, builds the same muscle over time. The habit of watching before touching becomes automatic with enough repetition.

It also changes the question a leader asks when arriving at a problem. Instead of walking in ready to tell people what to do, the better question is simply what does this team need right now, and often the honest answer is more hands, not more instructions.

Connecting It Back to Building People, Not Just Projects

None of this comes naturally to people trained their whole careers to move fast and solve problems immediately. It takes real discipline to stand still long enough to actually see what is happening before acting on it.

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams build exactly this kind of discipline, seeing clearly before acting, so the right fix happens the first time.

The Challenge

So here is the challenge worth carrying onto your next jobsite crisis: the next time something looks like it is falling apart, resist the urge to run straight into it. Stand back far enough to see the whole flow first, then act on what you actually see. As Art Archer used to say, “Don’t just do something, stand there until you know what to do, and then do that.” On we go.

FAQ

Why is running straight at a problem often the wrong first move?

Arriving fast and arriving informed are not the same thing. Without first observing what is actually happening, it is easy to react to whatever looks or sounds most urgent instead of addressing the real cause, which often wastes time and undermines whoever is already handling it correctly.

What is an Ohno circle, and what does it teach?

It is a technique used by Taiichi Ohno, the inventor of the Toyota Production System, where a person stands inside a chalk circle on the factory floor and simply observes, sometimes for hours, without stepping out to intervene. It trains people to see what is truly happening at the place of work instead of jumping to a pre-made solution.

How far back should you stand before assessing a problem on a jobsite?

It depends on the scale of what you are observing. A small crew might only require standing back fifty feet, while a large operation with multiple crews and equipment may require fifty yards or more, enough distance to see the flow of the whole operation rather than just the piece directly in front of you.

What does it mean to become “a hand” instead of taking over a struggling crew?

It means recognizing when the person already in charge has the situation correctly diagnosed and simply needs more support, not new instructions. Rather than taking control, you jump in and provide the extra labor or resources needed, letting the person already leading continue to lead.

How can a leader build this habit of observing before acting?

A daily reflection walk, taking time to observe the flow, pace, and energy of a project before responding to any single issue, builds this discipline over time. The habit shifts the first question from what should I tell people to do, to what does this team actually need from me right now.