The grain metaphor: reading your organisation

Reading your organisation means learning how work actually moves through it, which is almost never how the org chart says it moves. Every organisation has a grain: the real pattern of decisions, trust and routing that sits under the official structure. Here is the part people argue with. The org chart, the RACI and the process map someone built in Miro eighteen months ago are the least reliable documents in the building, and any change you design from them will spend the next year being sanded back. A carpenter does not argue with wood. They read it first.

The official structure and the operating structure are two different documents

Every company has an official structure and an operating structure, and they are rarely the same thing. The official structure lives in the org chart, the RACI, the process map nobody has opened since it was made. The operating structure lives in habits: who gets pinged before a decision goes to the exec team, which two people actually release the budget regardless of what the approval workflow says, which weekly meeting has quietly become a ritual that everyone attends and nobody needs.

Push a chisel the wrong way through oak and it splits, tears, goes ragged at the edge. Push it the right way and the wood almost does the work for you. Same tool, same force, different outcome, entirely down to whether you read the material first. Most organisational change fails for the same reason a bad joint fails: someone picked up the tool before they understood the grain.

I have sat in "decision-making" forums where the decision was made in a five-minute corridor conversation an hour earlier, and the forum existed to ratify it in front of an audience. That is not a criticism of the company. It is just the grain. The meeting is theatre. The corridor is where the wood actually runs. Once you see it, you stop trusting the artifacts and start reading the behaviour, because the two documents say different things:

Why the org chart is the least reliable document you own

The org chart tells you who reports to whom. It does not tell you who people actually go to when something breaks. Those are frequently different people, and the gap between them is one of the most reliable diagnostics I know for where an organisation is about to waste money. This is the same tell that separates strategy from operating reality: the document describes an intention, the behaviour describes the truth, and leaders keep managing the document.

This is why "just follow the process" so often lands as tone-deaf advice from outside the building. If the process fought the grain and lost, telling people to try the process harder just guarantees another loss. The process did not fail because people lacked discipline. It failed because it was cut against how the work moves, and the work won, the way it always does.

The cost of cutting against the grain

Cut with the grain and the work compounds. Cut against it and you spend the rest of the year sanding. That is not a metaphor for its own sake; it is a budget line. Every re-launch, every "adoption push", every awkward all-hands reminder to please use the new process is the cost of having cut against the grain the first time, and it is entirely avoidable.

I once watched a perfectly sensible new approvals workflow die a slow death over eight months. Not because anyone disagreed with it in the room, but because the two people whose sign-off actually mattered were never asked, on the record, whether the tool matched how they already worked. It did not. They routed around it. The tool is probably still live in the sense that it exists in a system somewhere. Nobody uses it. That is the pattern behind most change programmes that fail: the failure is designed in at the start, in the reading that never happened, and only becomes visible months later as quiet non-adoption.

There is a real financial version of this too. In one transit business, reading the grain surfaced a tool nobody's actual workflow touched, running on a licence that cost the company roughly £40,000 a year. Retiring it was not a cost-cutting exercise dreamed up in a spreadsheet. It fell out of watching how the work really flowed, and noticing the licence was paying for a process that had quietly moved somewhere else.

Reading your organisation before you change it

Reading your organisation is unglamorous and cheap, and almost nobody does it properly. There are four moves, and they run roughly in this order.

Walking the floor sounds old-fashioned because it is, and it still beats any survey. Reading six months of retro notes is the cheapest, most underused diagnostic available to any leader, because the data already exists and nobody has looked back across it. And the one-question move works because the question does not need to be clever. "What is the thing you keep having to work around?" said to the right person and followed by silence will get you further than any structured session. If you want the full field version of this, the art of the operating intervention walks the same read at engagement pace, and it is the first act of real operating leadership.

The load-bearing people

Identify the load-bearing people early, because they are rarely on the org chart in the place you expect. Every organisation has two or three people who, if they left tomorrow, would take a disproportionate amount of institutional knowledge and working trust with them, and it is almost never the most senior person in the room. It is the operations manager who has quietly run the actual planning process for four years under three different heads of ops. It is the engineer everyone routes questions to informally because the documented owner moved on and nobody updated the wiki.

Find them first. They are your fastest route to understanding how the place actually runs, and they are usually flattered rather than suspicious when someone finally asks them directly. They also tend to know exactly where the bodies are: which handoff drops things, which report gets rebuilt by hand every month because the automated one was never trusted, which "temporary" workaround has been load-bearing for two years. When you are learning to read the signals of operating health, these are the people who can point you straight at the ones that matter.

Run the change through the grain before you cut

Once you have read the grain, you can test any proposed change against it before you commit a single sprint. This is the filter I run, and it takes five minutes.

None of these questions are hard. What is hard is asking them before the launch date is set, when there is still time for the answer to change the plan. Most teams ask them afterwards, in the retro, when the answer is only useful as an explanation for why adoption stalled. If you want someone to run this read on one real process for you, that is exactly what the Grain Audit is: one process, end to end, in two weeks, with a ranked plan you keep.

The gap between the story and the reality is the work

Map the gap between the operating story and the operating reality, because the gap is the engagement. Every company has an official story about how it works: the values deck, the process documentation, the answer a senior leader gives when a client asks how you handle something. The operating reality is what actually happens on a Tuesday afternoon when nobody senior is watching. The size of that gap tells you roughly how much change work is ahead of you. The shape of it tells you where to start.

Reading the grain first takes more time than most leaders think they have, largely because most leaders are optimising for the appearance of speed rather than actual speed. And it saves more time than they can imagine, because every intervention built on the operating reality sticks the first time, while every intervention built on the operating story needs a second, third and fourth attempt before it either takes or gets quietly abandoned. A carpenter does not argue with wood. Read the grain first. Cut with it, and the rest of the job gets easier than anyone expects.