The Problem They Brought You Is Not Always the Problem

The call that starts an engagement almost always begins the same way. Someone describes what they are seeing \u2014 the tension that has been building on the senior team, the turnover that keeps happening in the same department, the initiative that has stalled for the third time in two years \u2014 and they tell you what they think is causing it. They have a theory. Most clients do. They have been living with the problem long enough to have developed an explanation for it, and that explanation is usually reasonable, usually partial, and usually wrong in at least one important direction.

Your job is not to correct them in that first conversation. Your job is to listen carefully enough to understand not just what they are describing, but what they are not describing. The gap between those two things is often where the work actually lives.

---

Why presenting problems mislead

A presenting problem is not a fiction. The client is telling you something real. The turnover is real. The stalled initiative is real. The tension on the senior team is real. What is not reliable is the causal story wrapped around it \u2014 because that story was constructed by someone inside the system, using the information available to someone inside the system, which is by definition incomplete.

This is not a failure of intelligence or honesty. It is a structural condition. The leader who calls you in can see the effects of the friction clearly. What they cannot see, with the same clarity, is the mechanism producing it \u2014 because the mechanism is often operating at a level of the organization they do not have clean visibility into, or it involves dynamics that the people around them have learned not to surface, or it requires a vantage point that is simply not available from where they sit.

The presenting problem is what the system looks like from the inside. The diagnostic is what it looks like from somewhere else. Those two views will rarely be identical, and the distance between them is not a problem to be managed. It is the most valuable thing the engagement produces.

---

What the intake conversation is actually for

Most practitioners treat the intake conversation as information gathering. It is \u2014 but only partially. The more important function of that conversation is calibration: understanding not just what the client believes is happening, but how they are thinking about it, what they have already tried, and where their theory of the problem has the most investment.

That last one matters more than it might seem. A client who has staked organizational capital on a particular explanation of the problem \u2014 who has already told the board it is a communication issue, or has already restructured the team around a theory about role clarity, or has already let someone go based on a diagnosis that may not have been accurate \u2014 is a client who has something to protect in the intake conversation, whether they know it or not. They are not being dishonest. They are being human. The explanation they brought you is not just a theory. It is a decision they already made. Revising it has a cost.

The practitioner who understands this will not treat the intake conversation as a neutral information exchange. They will listen for the places where the client's explanation is doing extra work \u2014 carrying more certainty than the evidence warrants, or accounting for more of the problem than one cause could plausibly explain, or quietly foreclosing lines of inquiry that might produce an uncomfortable answer. Those are the places worth returning to once the diagnostic has run.

---

How the gap surfaces

The diagnostic will rarely produce a finding that directly contradicts the presenting problem. More often it will reframe it \u2014 shifting the level at which the problem is operating, or revealing a cause that the presenting problem was masking, or identifying a pattern that the client's explanation was treating as background noise.

A leadership team described as "misaligned" turns out to be operating under a decision-making authority structure that has never been made explicit \u2014 three people who each believe they have final say on different categories of decision, and who have been managing the resulting confusion through a series of informal workarounds that have become load-bearing. The problem is not alignment. It is architecture.

A department with a persistent retention problem and a presenting theory of inadequate compensation turns out to have a protected source of friction that compensation increases will not touch and that three people in that department could describe in detail if anyone asked them directly. The problem is not pay. The problem has a name, and it is sitting in a corner office.

A cross-functional initiative that keeps stalling around the same decision point, attributed by the client to "competing priorities," turns out to reflect a much older dynamic \u2014 two leaders whose working relationship broke down eighteen months ago over something that was never resolved, and whose teams have been absorbing the cost of that unresolved tension ever since. The problem is not priorities. The problem is a conversation that has not happened yet.

In each of these cases, the presenting problem was real. The turnover was happening, the initiative was stalling, the leadership team was struggling to move. What was not accurate was the explanation \u2014 and an intervention aimed at the explanation rather than the mechanism would have produced activity without resolution.

---

How to redirect without losing the client

This is the part that requires the most care. The client came to you with a theory. The diagnostic has produced a different one. How you handle that transition will determine whether the engagement moves forward productively or whether it stalls in a negotiation about whose explanation is correct.

The answer is not to argue for the new finding at the expense of the presenting problem. The presenting problem is still real, and the client's experience of it is still valid. What the diagnostic has done is not disprove their theory \u2014 it has given you a more complete picture of what is generating the conditions they described. That is a meaningful distinction, and it is worth making explicit.

Start from what you both agree on. The friction is real. The cost is real. The desire to resolve it is shared. From that foundation, introduce the finding not as a correction but as an addition \u2014 something the diagnostic surfaced that adds to the picture rather than replacing it. "What the instrument found underneath the retention problem" is a different sentence than "the retention problem is not actually the problem," and it produces a much more productive conversation.

Then let the client do the connecting. In almost every case, once the practitioner surfaces the underlying mechanism, the client can see it. They have been living inside this organization. The data is not foreign to them \u2014 it is familiar in a way they may not have had language for before. A good finding does not surprise the client so much as it names something they already knew in a different register. When that recognition happens \u2014 and you will see it when it does, in the particular quality of the silence that follows \u2014 the presenting problem and the diagnostic finding have become the same conversation.

That is the moment the engagement actually begins.

---

What this asks of the practitioner

Redirecting a client's presenting problem requires a particular kind of confidence \u2014 not the confidence of someone who is certain they are right, but the confidence of someone who trusts the instrument and is willing to follow where it leads even when it leads somewhere the client did not expect.

It also requires genuine humility about the limits of the diagnostic. The instrument surfaces patterns. It does not have access to the full history of the organization, the relationship dynamics that predate anyone currently in the room, or the strategic context that may make a particular friction worth carrying for reasons that have not been shared. The practitioner who presents a finding as the complete picture is not being rigorous. They are being overconfident. The finding is the beginning of a conversation, not the end of one.

What the client brought you was real. What the diagnostic found is also real. The work is to hold both with enough steadiness that the client can see them at the same time \u2014 and decide, with your help, what to do about what they are actually looking at.

That is harder than confirming what they already believed. It is also the only version of this work that produces something that lasts.