What is organisational consultancy?

"We agreed this in the offsite. Why is nothing different?" That is the question a CEO actually asks, usually six months after a decision everyone in the room supported. Organisational consultancy is the practice of answering it honestly: reading how the company actually operates, at the level of decisions and workflows, then changing it without breaking what quietly holds it together. Most consulting sells answers. Organisational consultancy sells a truthful read of the operating reality and the discipline to act on it in an order the organisation can survive. It is closer to craft than to strategy, and it starts with weeks of listening before anyone touches the structure.

The grain, not the org chart

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, and it is where the real operating model lives. This is the difference between strategy and operating reality: one is the story the company tells about itself, the other is what happens on a Tuesday when the story is not watching.

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. The grain metaphor is the whole discipline in one image.

Organisational consultancy is the practice of reading the grain, choosing where to cut with it and where to cut against it, and doing that in an order the organisation can survive.

A carpenter does not 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 were not looking. Organisations split the same way. A restructure that ignores where trust actually sits does not 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. Reading the grain is not the soft part of the job. It is the risk management.

What organisational consultancy is, and what it is not

The clearest way to define the practice is against the three things people usually mistake it for. Change management, transformation programming and the strategy deck all have their place. None of them is this.

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 run. All three skip the same step. None asks what is happening in the building right now, and why it got that way. This is a large part of why most change programmes fail: they manage the change into a design nobody diagnosed.

Organisational consultancy starts at the diagnosis, because most operating problems are not knowledge problems. The leadership team usually already knows something is wrong. What they do not 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. Get the read wrong and every downstream decision inherits the error.

Where the work actually 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 was not 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. 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 instinct to buy a tool or add a layer is nearly always faster than the instinct to read first, and nearly always more expensive.

The three movements: Read, Craft, Scale

The work runs in three movements, in this order. The order is not a preference. It is the sequence operations actually have to happen in if the change is going to survive. This is the spine of how Deepgrain runs an engagement, and skipping or reordering it is the most reliable way to waste it.

Read is slow on purpose. It 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. Most engagements that fail, fail because this step got compressed into a week of workshops instead of a month of watching. A workshop gives you the operating story in high definition. It does not give you the grain.

Craft designs 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 is mostly 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 is worth.

Scale compounds 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 have proven they hold. Scaling too early is the second most common way this work fails, right behind skipping the listening. And there is a quieter failure at this stage, the one every dependency-based consultancy leaves behind: "The builders left. The capability went with them." Scale exists to prevent exactly that. The test is not the report. It is what the team ships after you leave. On one engagement, two months on, the champions had shipped five more agents we never scoped. That is the test.

When a board should actually reach for 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. After a change programme has already been tried and quietly failed to stick. The board-level version of the trigger is blunter: "The board wants a roadmap. You don't have one." The symptoms look different from the outside, but they resolve to the same gap between decided and done.

Before commissioning anyone, a leadership team can run its own situation through a short filter. It is the same one I use to decide whether an engagement is even the right instrument, or whether the problem is smaller and more specific than it feels.

If the answers are uncomfortable but the scope feels large, the smallest honest version of this work is a Grain Audit: one process read end to end in two weeks, with a ranked plan you keep whether or not you go further. It is deliberately narrow. Reading one workflow properly tells you more about the grain than a company-wide survey ever will, and it costs a fraction of the programme most boards reach for first.

What it costs to get the order wrong

The expensive mistakes in this work are almost never the interventions themselves. They are the order. Fix before diagnosis breaks something load-bearing. Scale before proof spreads a design that only worked because one team already trusted each other. Announce before craft leaves a decision hanging in the air with no path to the workflow it was meant to change. Each one is defensible in isolation and costly in sequence, and each one is avoidable by holding to Read, then Craft, then Scale.

That is the whole argument for treating this as a craft rather than a deck, and it is the core of operating leadership: the discipline of reading how work actually flows before you change it. A carpenter who reads the wood wastes less of it. An operator who reads the grain wastes less of the organisation: less trust, less goodwill, fewer quietly load-bearing people deciding to stop bothering. The diagnosis is not the deliverable and the report is not the point. The point is a company that operates the way it says it does, and keeps operating that way after the consultant has gone.