The grain metaphor: reading your organisation

A carpenter doesn't argue with wood. They read it first.

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 before you touched it. Most organisational change fails for the same reason a bad joint fails: someone picked up the tool before they understood the grain.

What the grain is, in an organisation

The grain is the pattern of how things actually move: which Slack channels carry the real decisions, which meetings are theatre and which are signal, which people are quietly load-bearing.

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

I've 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's not a criticism of the company. It's just the grain. The meeting is theatre. The corridor is where the wood actually runs.

Why the org chart lies

The org chart tells you who reports to whom. It does not tell you who people actually go to when something is on fire. 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.

I worked with a business where the official escalation path for a client-facing outage ran through three layers of management. The real path, the one everyone used, was a single WhatsApp group with the CTO, one senior engineer, and a customer success lead who happened to have the best relationship with the client. That group had been quietly doing the job the incident process was meant to do, faster and better, for two years. The org chart said the process worked. The grain said something else entirely, and the grain was right.

This is why "just follow the process" so often lands as tone-deaf advice from outside consultants. If the process fought the grain and lost, telling people to try the process harder just guarantees another loss.

The cost of cutting against the grain

Cut with the grain and the work compounds: you build on the channel that already carries trust, you route through the person who already has the authority even if the title says otherwise, you keep the ritual meeting that's doing real cohesion work even though it looks inefficient on paper. Cut against it and you spend the rest of the year sanding: fighting the same resistance every quarter, re-explaining the same new process to the same people who quietly kept using the old one, wondering why adoption never sticks.

I've 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 new tool matched how they already worked. It didn't. They routed around it. The tool is probably still "live" in the sense that it exists in a system somewhere. Nobody uses it.

That's the sanding. 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. It is entirely avoidable, and it is avoided by doing the reading before the cutting, not after.

How to read it

Walk the floor. Sit in the standups. Read six months of retro notes. Ask one question and listen to the answer for an hour.

Walking the floor sounds old-fashioned because it is, and it still works better than any survey. You notice who leans over to whom before speaking in a meeting. You notice which desk cluster has become an informal ops room. None of that shows up in an engagement survey, and all of it shows up in five minutes of paying attention.

Sitting in the standups isn't about the standup content. It's about watching who defers to whom, which updates get real follow-up questions and which get a nod and a move-on, and whether the stated owner of a workstream is the person actually answering for it. Ownership on paper and ownership in the room are not always the same person, and the gap tells you something.

Reading six months of retro notes is the cheapest, most underused diagnostic available to any leader. Most teams already write down what's broken every fortnight and then never look back at the pattern across a dozen of those documents. Read them in sequence and the same three or four issues surface again and again, phrased differently each time because nobody connected them. That recurrence is the grain complaining. It's rarely subtle once you line the documents up.

And asking one good question, then genuinely listening for an hour rather than waiting for your turn to respond, surfaces more real information than a full day of structured workshops. The question doesn't need to be clever. "What's the thing you keep having to work around?" said to the right person and followed with silence will get you further than a facilitated session with sticky notes.

The load-bearing people

Identify the load-bearing people. 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's the operations manager who has quietly run the actual planning process for four years under three different heads of ops. It's the engineer everyone routes questions to informally because the documented owner moved on and nobody updated the wiki. Find them early. 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.

The gap between story and reality

Map the gap between the operating story and the operating reality. 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 do you handle X." 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, and the shape of that gap tells you where to start.

This is the entire premise behind reading the grain before you touch anything. It 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 requires a second, third, and fourth attempt before it either takes or gets quietly abandoned.

A carpenter doesn't argue with wood. Read the grain first. Cut with it, and the rest of the job gets easier than anyone expects.