What is organisational consultancy?

Most consulting sells answers. Organisational consultancy sells better questions, and the discipline to live with the answers once they arrive.

The grain, not the diagram

Every organisation has a grain: the way decisions actually move, the way work flows, the way trust is earned. Most leadership teams have never read it. They have an org chart, a strategy deck, a values poster. The grain is something else.

The org chart says the Head of Ops reports to the COO. The grain says every decision over £50k actually gets a nod from the founder's old co-founder first, in a side conversation nobody minutes. The values poster says "customer first". The grain says the team that protects the customer is the one two people quietly route escalations to, because the official process takes four days and everyone knows it. You cannot read any of this off a slide. You read it by watching what people do when nobody is checking, and by asking who they call when something goes wrong.

Organisational consultancy is the practice of reading the grain, then choosing where to cut with it and where to cut against it.

A carpenter doesn't argue with wood. They read it first. Cut with the grain and the piece holds. Cut against it blind and it splits, often weeks later, in a place you weren't looking. Organisations split the same way. A restructure that ignores where trust actually sits doesn't fail in the town hall. It fails three months later when the people who quietly made things work stop bothering, because nobody asked them how things worked in the first place.

What it is not

• It is not change management.
• It is not a transformation programme.
• It is not a McKinsey deck with three horizons.

Closer to craft than to strategy. You spend weeks listening before you touch anything.

Change management assumes the target state is already correct and the job is adoption: comms plans, training decks, a RACI chart nobody reads twice. Transformation programming assumes bigger is better: more workstreams, more steering committees, more slides per week to prove the spend is justified. The three-horizons deck assumes the future can be planned in a workshop with sticky notes and then handed to a project manager to execute. All three skip the same step. None of them ask what is happening in the building right now, and why it got that way. Organisational consultancy starts there, because most operating problems are not knowledge problems. The leadership team usually already knows something is wrong. What they don't have is a reliable read on why, stripped of the politics and the wishful thinking that builds up around any story people tell about themselves.

Where it usually goes wrong

The failure mode is almost always the same: someone arrives with a fix before they have the diagnosis. A new COO flattens a layer of management that looked redundant on the chart, not realising it was the only place two warring departments resolved disputes without escalating to the CEO. A consultant introduces a formal decision-rights framework, and the informal one it replaces was faster and better understood, it just wasn't written down. Both interventions are defensible on paper. Both break something that was quietly load-bearing, and the people who could have said so were never asked.

This is why the listening phase is not politeness. It is risk management. You cannot know what a change will break until you know what is currently holding the structure together, including the parts that look inefficient from the outside. Some inefficiency is waste. Some of it is the price of trust, or the residue of a fix for a problem that no longer exists but whose absence would cause a new one. Telling the difference is the entire job.

The three movements

Read. Diagnose the operating reality, not the operating story. This means interviews that go past the first, rehearsed answer, shadowing how decisions get made in the room, and tracing two or three recent decisions end to end to see who was really consulted versus who was told. It is slow on purpose. Most engagements that fail, fail because this step got compressed into a week of workshops instead of a month of watching.

Craft. Design interventions that fit the grain. Not the interventions that would work in a textbook org, the ones that will work in this one, given who has influence, what has already been tried and failed, and how much change the culture can absorb before it revolts. Craft means sequencing: which team goes first, which decision gets the new process piloted on before it touches anything that matters, which existing informal channel you keep because replacing it would cost more trust than it's worth.

Scale. Compound the work without breaking it. The interventions that survive contact with the wider organisation are the ones tested small first, on real decisions with real stakes, then extended once they've proven they hold. Scaling too early is the second most common way this work fails, right behind skipping the listening. A pilot that worked in one team because that team already trusted each other tells you almost nothing about whether it will work in a team that doesn't.

Who actually needs this

Companies reach for organisational consultancy at predictable moments: past a headcount threshold where the informal habits that got them here stop scaling, after a merger where two grains collide and nobody has reconciled them, or after a change programme has already been tried and quietly failed to stick. The tell is usually the same complaint from the leadership team: "we made the decision months ago and nothing has actually changed." That gap between decided and done is where the real grain of the organisation lives, and it is almost never where the org chart says it should be.

Read, Craft, Scale is not a methodology slide. It is the order operations actually have to happen in if you want the change to survive past the announcement.