Why You Should Start with the 5 Where’s Before the 5 Whys

Why Most Problem-Solving in Construction Goes Nowhere and What to Do Instead

When something goes wrong on a construction project, the instinct is to find out who did it and fix the symptom. The schedule slipped who missed the handoff? The quality was rejected whose crew did the work? The materials were wrong, who placed the order? Those questions feel productive because they produce answers. They are almost never solving the actual problem. They are identifying the person who happened to be standing at the place where the symptom appeared, which is usually nowhere near the place where the problem actually started.

Taiichi Ohno, the manufacturing genius behind the Toyota Production System, the person most responsible for developing the Lean thinking that construction is now trying to apply, understood this so deeply that he built his entire teaching practice around a single discipline: stand in the place where the problem is, observe what is actually happening, and ask why. Not who. Why. And before you ask why, ask where. Five times, if necessary, until you are standing at the actual point of cause.

The Ohno Circle

The story of the Ohno circle is worth knowing in full because it captures something that rarely exists in modern construction culture: the willingness to invest deep time in genuine observation. Ohno would stand in a circle drawn on the factory floor, watch what was happening, and keep asking why, sometimes for hours. He would bring a student with him, a group leader, which is the equivalent of a superintendent in construction and leave them in the circle to observe while he stepped away. He would return later and ask what they had seen. He would do this multiple times across an entire day, expecting each return to produce a deeper analysis.

On one occasion, according to Jeff Liker, Ohno forgot about a student at the end of the day. The student stayed in the circle, overnight, into the next day until his wife called the factory and blasted Ohno for the oversight. There is something in that story that is both amusing and instructive. The student stayed because the culture demanded deep observation. The problem with suggesting that approach to most superintendents today is that ten minutes of deliberate observation in one place feels like the most unproductive thing imaginable when there are thirty things demanding attention simultaneously. The irony is that those thirty demands often persist precisely because nobody has stood still long enough to find their actual origin.

What Happens When We Skip the “Where”

Here is the pattern that plays out on nearly every construction project where problems are solved at the symptom level. A quality defect appears in zone three. Someone is identified. A correction is made. The correction is documented. And three weeks later, the same type of defect appears in zone seven, because the condition that produced it somewhere upstream in the process, weeks before the defect became visible was never found and never changed. The symptom was eliminated. The point of cause was never reached.

This is not just inefficient. It is actively harmful. By eliminating the symptom without finding the point of cause, the connection to the source of the problem is severed. The problem will return. And when it returns, it will return in a condition that is harder to trace back to its origin because the previous correction created the impression that the problem was solved. In safety terms, this is how serious incidents develop: through a series of near-misses that were resolved at the symptom level, each one quietly worsening the underlying condition.

The System Failed the Problem-Solver

Most people in construction were never taught disciplined problem-solving. They were taught to identify what went wrong, fix it, and move on. The pace of construction projects, the daily urgency of handoffs, deliveries, inspections, and schedule pressures, makes that approach feel like the only viable one. There is no time to stand in a circle and observ  e for two hours. There is barely time to get through the morning huddle.

But that time pressure is itself a symptom. Projects that are chronically too busy to solve problems at the root level are projects that will keep encountering the same problems, forever, because the system was never changed. The busyness that prevents root cause analysis is often generated by the problems that root cause analysis would have prevented. The system built the cycle. The people inside it are running as fast as the system allows.

5 Wheres Before 5 Whys

Here is the discipline that changes everything about how problem-solving works. Before asking why five times, ask where five times. Where did this problem come from? Where are the instructions that should have prevented it? Where in the process did the actual cause originate? Where is the answer detailed? Where does the system break down that allowed this to reach the point where it became visible?

The 5 Whys is a powerful tool. But it only produces useful results when it is applied at the point of cause, the actual location in the process where the problem originated not at the point of discovery, which is usually much further downstream. Most problem-solving in construction applies the 5 Whys at the point of discovery and calls the answer a root cause. What it actually found is the most recent place the problem became impossible to ignore.

Ohno’s lesson to Hayashi makes this precise. Hayashi identified a serious quality problem in assembly and was ready to start solving it. Ohno stopped him and demanded to know where the problem had actually occurred. Hayashi realized the defective part might have originated in how it was manufactured at an earlier stage. Ohno asked why he was standing in assembly if the problem was in manufacturing. Then, when Hayashi moved to go upstream, Ohno stopped him again because the assembly problem still had to be contained before the root cause upstream could be addressed. Two separate actions: contain the symptom where it is visible, then trace back to the actual origin and change the condition there.

That sequence is the complete problem-solving discipline: identify the symptom, contain it at the point of discovery, then find the point of cause by asking where the problem originated and only then ask why the system allowed that condition to exist.

Here are the signals that a project team is doing symptom-solving rather than root cause problem-solving:

• The same type of problem reappears in different zones after being corrected once.
• Problem-solving conversations begin with identifying who is responsible rather than where the problem originated.
• Corrections are made without any change to the system condition that produced the defect.
• Lessons learned are documented but the process that generated the lesson remains unchanged.
• The team is too busy managing recurring problems to have time for structured problem-solving.

Source Management

Ritsuo Shingo, son of Shigeo Shingo, teaches a principle he calls source management. The meaning is the same as what Ohno was teaching through the circle: we must get to the source, and only at the source can real change happen. Dealing with what appears to be the problem at the point of discovery, downstream from where it originated is exhausting, demoralizing, and ultimately futile. It is a waste that Lean practitioners sometimes call a waste of life: wasting time and energy solving problems that will return because the actual source was never found and never changed.

It encompasses all the other wastes and exceeds them. You can eliminate the eight operational wastes on a project and still be destroying value if the team is spending its capacity repeatedly addressing the same symptoms instead of finding their origin. The waste of life is what happens when problem-solving looks productive on the surface and produces nothing durable underneath.

Connecting to the Mission

At Elevate Construction, the system-first diagnostic is foundational. When something goes wrong on a project, the first question is not who failed. It is where in the system the condition that produced the failure was allowed to exist. That framing protects the people and produces better outcomes. It also requires the discipline that Ohno spent his career demanding from his students: the willingness to observe carefully, trace problems to their origin, and change the system at the source rather than the symptom.

That discipline is what separates a Lean organization from an organization that is performing Lean. If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow.

Ask the 5 Wheres before the 5 Whys. Stand at the point of cause before asking why. Contain the symptom. Change the source. Then the improvement holds.

On we go.

Frequently Asked Questions

What is the difference between the point of discovery and the point of cause?

The point of discovery is where a problem becomes visible where the defect is found, where the delay is noticed, where the complaint is made. The point of cause is where the problem actually originated, which is almost always upstream in the process from where it was discovered. Solving the problem at the point of discovery without reaching the point of cause only eliminates the symptom.

Why ask the 5 Wheres before the 5 Whys?

Because the 5 Whys only produces useful root cause analysis when it is applied at the point of cause. Asking why at the point of discovery produces an explanation for the symptom, not the source. The 5 Wheres narrows the problem from a vague symptom to a specific location in the process where the investigation can begin.

Why does eliminating a symptom make the underlying problem worse?

Because it severs the visible connection between the symptom and its cause. When the symptom disappears, the problem appears solved. The underlying condition continues unchanged, returning later in a form that is harder to trace and often more serious particularly in safety contexts.

What is “source management” as taught by Ritsuo Shingo?

Source management is the principle that real, lasting change only happens at the source of the problem not at the point where it becomes visible. It requires tracing problems upstream to their origin and changing the system condition that allowed them to develop.

How does this connect to the system-first philosophy in Lean construction?

Lean construction treats almost all failures as system failures rather than people failures. When a problem occurs, the first diagnostic question is what in the system allowed this condition to develop. The 5 Wheres operationalizes that diagnostic by directing the investigation upstream to the system origin before the 5 Whys asks why the system failed.