There is a version of business problem-solving that goes like this: something is not working, you identify what it is, you fix it, and it stays fixed. That version exists, but it is rarer than most people think. More often, the thing that is not working is pointing at something else, and fixing the surface problem just moves the pressure somewhere new.

The presenting problem is usually a symptom

In most clarity sessions, the problem described in the pre-session brief is not the problem we end up working on. A founder says they have a sales problem. After 20 minutes of questions, it becomes clear that the sales process is fine but the positioning is muddled, so the right people are not finding them in the first place. Fixing the sales process would not have helped. The presenting problem was real. It just was not the root.

A useful diagnostic question

One question that tends to crack things open is this: what would have to be true for this to not be a problem? If your answer involves changing something external (the market, your customers, your team), that is worth noticing. If your answer involves changing something you actually control, that is usually where the real work is. The question forces you to think about conditions rather than symptoms, and conditions are where use lives.

The three-layer test

When we are trying to identify the real problem, we use a rough three-layer test. The first layer is what is visibly not working. The second layer is what would have to change for the first layer to resolve. The third layer is what is preventing that change from happening. Most people spend their time on layer one. The useful work is almost always on layer three. It is slower to get there, but the solutions tend to stick.

What to do with this

Before you spend money or time solving a problem, write down the problem as you understand it. Then write down what you have already tried. Then write down what you are afraid the real problem might be. That third question is the one that matters. If you are not sure what to write there, that uncertainty is itself useful information. It means you are probably still at layer one.

When to get a second opinion

Sometimes you are too close to the situation to see the layers clearly. That is not a failure of intelligence. It is just how proximity works. A good thinking partner, whether that is a consultant, a trusted peer, or a well-chosen advisor, can often see the layer structure in about 20 minutes of careful questioning. If you have been working on the same problem for more than three months without meaningful progress, it is worth asking whether you are solving the right thing.

The free intro call at FlowShiftWaveMind is a good place to test whether the problem you are working on is the real one. Thirty minutes, no pitch, and you will leave with a clearer sense of where to look next.