The difference between being an expert and being useful

I have watched some of the most technically accomplished consultants in the industry walk out of client engagements with their analysis intact and their recommendations unimplemented.

The decks were excellent. The logic was sound. The findings, in most cases, were exactly right.

They were also completely unusable.

There is a distinction the profession rarely makes explicitly, and almost never teaches. Being an expert means you can identify the right answer. Being useful means you can deliver it in a form the organisation can actually receive.

Those are not the same skill. And in my experience, the gap between them is where most transformation work quietly dies.

There is a reason this pattern repeats. Large organisations often commission the Big 4 not primarily for implementation, but for cover. A recommendation from a recognised global firm is harder to challenge in a board meeting than one from an independent practitioner. The advice becomes a defence mechanism as much as a solution. The implementation tends to arrive later, with a different kind of practitioner: someone required to actually understand the culture, the politics, and the absorptive capacity of the organisation.

I have been invited into engagements specifically to do the second thing. A large organisation commissions a Big 4 firm. The firm produces something brilliant, thorough, and entirely unsuited to the culture, the politics, and the absorptive capacity of the client. I am then asked to come in, take the analysis apart, and reassemble it in bite-sized pieces the organisation can digest. The expertise was already there. What was missing was translation.

But translation is not neutral. And this is where the challenge gets uncomfortable.

In the early part of my career, I was part of a team mapping the operating model of a large UK financial institution. The mandate was clear: find the complexity, name it, map it, make it visible.

We did exactly that. What we found was not evenly distributed. One function alone accounted for more than 70% of the process inefficiencies we catalogued. Roles without job descriptions. Data objects of unknown provenance. Performance metrics, in many cases, simply absent.

That function was headed by the programme sponsor.

A friendly Head took me to one side and offered what I can only describe as a professional education. The previous consultancy, he told me, had been shown the door for taking the Statement of Work literally. "You need to understand the politics here if you want to survive."

I understood the politics. I used that understanding to negotiate a version of the findings the Programme Sponsor could approve, selectively framed, stripped of the pattern that made them meaningful in aggregate. The 70% figure did not appear. What appeared instead were minor, tractable issues: the kind that could be acknowledged without threat and resolved without structural change.

The Programme Sponsor approved them. The engagement closed successfully by every conventional measure. The complexity we had mapped remained, as far as I am aware, exactly where we had found it.

I had translated. I had made the findings digestible. And in doing so, I had calibrated the impact to what the organisation was willing to receive, rather than what it needed to hear. The intervention landed. The full opportunity it represented did not.

That is the trap at the centre of this argument. Contextual intelligence, knowing the culture, reading the room, understanding what the organisation can receive, is a genuine skill and a legitimate part of the practitioner's role. But it has a shadow side. The same intelligence that allows you to make a solution land can be used to make an inconvenient truth disappear.

The Big 4 consultants whose decks I have been asked to translate were not failing because they lacked contextual intelligence. They were, in a specific sense, protected by its absence. They said what they found. The client could not use it. Everyone moved on with clean hands.

I said something the client could use. And in that engagement, what the client could use was not the truth.

So here is the challenge I want to put to practitioners who are proud, as I am, of their ability to translate expertise into something organisations can actually receive.

What are you translating, and in whose interest?

Contextual intelligence deployed in service of the answer makes transformation possible. Contextual intelligence deployed in service of the relationship makes you complicit in the status quo.

The expert who cannot read the room produces the right answer at the wrong frequency. The practitioner who can read the room but uses it to manage the finding rather than land it produces something more dangerous: a finding that looks like progress and changes nothing.

The question is not whether you are expert enough. Most experienced practitioners are. The question is whether you are using your contextual intelligence to serve the organisation or to protect yourself within it.

That question, asked honestly, tells you whether you are being useful.