Skip to content Skip to footer

You Could See Your Client Was Hurting. So You Tried To Help.

You could see the client was hurting

They opened up to you – a tangle of thoughts, some of them business, some of them not, all of them weighing on the client’s mind. So, you did what a good adviser does. You listened. You didn’t rush them. And when they’d finished, you offered what you had: your experience, a few things you’d seen work, and what you’d do in their shoes. You were trying to help. And somewhere in there, something shifted.

Not dramatically. They didn’t disagree. But they pulled back – not all the way, just enough that you felt it. The energy went out of the room. The conversation, which moments ago was open and alive, quietly closed down. You left knowing your advice was sound. And knowing, somehow, that they’ll do little or nothing with it. What went wrong?

Here’s my best answer. You treated an adaptive challenge as if it were a technical problem. It’s a distinction from Ronald Heifetz at Harvard, and it explains exactly what you just felt in that room. Some problems are technical: the answer is known, the expert supplies it, and the client can more or less receive it and move on. A great deal of what you’re paid for is exactly this – and for that work, giving the answer is precisely right.

But some problems aren’t like that. They’re messy, personal, tangled up in the client’s own situation and values. There’s no best-practice answer sitting on a shelf. Heifetz put it concisely: “The most common failure in leadership is produced by treating adaptive challenges as if they were technical problems.” And that’s what the telling did. The moment you reached for your answer, you took the problem onto your side of the table. For a technical problem, that’s a gift. For this one, it quietly let the client off the hook of a problem that was only ever going to be solved by them owning it. They felt handled, not heard – and quietly withdrew.

Because the two kinds of problems aren’t just different problems. They’re different conversations. One is **Ask, Diagnose, Tell** – the expert’s conversation, and the right one when the answer is known. The other is **Ask, Explore, Co-create** – where you don’t supply the answer; you help them find it themselves – the one they own. The withdrawal you felt was the sound of the first conversation being used on a problem that needed the second.

Many client problems contain both. The skill is recognising which conversation is needed now. Most of us were only ever trained in the first.

Cart0
Cart0
Cart0