Naming the Real Problem

March 29, 2026

Reflect

Have you ever felt constantly tired, even after getting what should be enough rest? The first response often seems straightforward: adjust the schedule, try to sleep more, drink more caffeine, and look for small ways to regain energy. For a while, it seems to help, but the fatigue returns.

Over time, it becomes clear that the issue was never just lack of rest. It was a signal. The underlying problem was something else, poor sleep quality, unmanaged stress, or a routine that was not sustainable in the first place. Until that is addressed, the solutions remain temporary.

The same pattern shows up in leadership. A team struggles with communication, so more meetings are added. Progress feels slow, so timelines are tightened. Friction appears, so new processes are introduced to create more control. Each response makes sense, yet when the underlying issue is something deeper, misaligned priorities, unclear ownership, or competing goals, those fixes only address what is visible.

The problem that is easiest to name is not always the problem that needs to be solved. Until the real issue is identified, effort increases, but progress does not.

Anchor

Leaders rarely set out to solve the wrong problem.

What they respond to is what is most visible, the issue that is easiest to describe, the one that shows up in meetings, dashboards, and day-to-day friction. Those signals feel immediate and actionable, which is why they draw attention.

The challenge is that visible problems are often downstream. They reflect something deeper that is shaping the situation but is less obvious and harder to name.

Communication issues may point to misaligned priorities. Delays may reflect unclear ownership. Constant rework may signal that the standard for “good” has never been clearly defined.

Without pausing to examine what is driving the pattern, it is easy to respond to what is in front of you and assume it is the problem itself.

Clarity helps, but here it does something more. It creates enough space to ask a different question:

What is causing this to keep happening?

Momentum

When a problem keeps returning, it is often a signal that something deeper has not been addressed.

Before moving to solve it, pause long enough to test what you are seeing. If this issue were resolved today, would it stay resolved, or would it likely show up again in a different form?

Taiichi Ohno, one of the architects of the Toyota Production System, used a simple but disciplined approach to get to the root of problems. Rather than accepting the first explanation, he would ask “why” repeatedly, often five times, to move past surface symptoms and uncover what in the system was actually producing the result.

The goal was not to assign blame, but to understand how the process itself had broken down and to put in place a countermeasure that would prevent the issue from recurring.

The same discipline applies in leadership. The first answer is often incomplete, and what is most visible is not always what is most important. Taking the time to look one layer deeper can shift the focus from fixing what is obvious to addressing what is actually driving the problem.

Next week: The Power of a Well-Timed Question Once the problem is clear, the right question often moves the work forward faster than the right answer.

Subscribe toThe Weekly Momentum.