How to diagnose an organisation in 30 days

A sixty-person climate venture brought me in certain the problem was onboarding. New joiners were slow to get productive, and the leadership team had the fix in mind before I arrived. Three weeks of listening said something else: the joiner-to-leaver lifecycle snagged in more than one place, and onboarding was only the loudest of them. That is how to diagnose an organisation. You listen for the reality underneath the story leadership already believes, you find the shape that makes forty scattered complaints click into one, and you recommend nothing until you have earned the right. Thirty days done properly does not buy you a framework. It buys you the right to be believed when you say what is actually wrong.

How to diagnose an organisation without faking it

Most consultants skip the diagnosis, or fake it. They turn up with a framework already in the back pocket, run a handful of interviews to make it feel bespoke, then present it back with the client's logo on the front. That is decoration dressed as diagnosis, and the people inside the company can smell it.

Thirty days done properly buys you the one thing a framework never can: the right to be believed when you say what is broken. The diagnostic is not the work. The diagnostic is the permission to do the work. Every recommendation you make later, every system you rebuild, every workflow you redesign, lands or bounces depending on whether the room believes you actually understand them. You cannot buy that belief with polish. You earn it by listening long enough to say something true that leadership had not managed to say themselves.

This is the Read in Read, Craft, Scale. Get the reading wrong and everything downstream is built on a guess. Get it right and the craft that follows feels less like your idea and more like the obvious next step from a diagnosis the room already agrees with.

The maths: two thirds listening, one third synthesis, zero recommending

Split the thirty days two-thirds, one-third, zero. Two-thirds of the time listening. One-third synthesising. Zero recommending until both of those are finished.

Most people invert this without noticing. They listen for a week, spot a pattern that confirms what they suspected on the sales call, and start building the deck. The deck gets more polished as the days go on. The listening stops doing any real work. It just becomes evidence-gathering for a conclusion reached in week one.

You will know you are doing it right because week three feels uncomfortable. You should still be finding things that contradict what you thought on day two. If by day fifteen nothing has surprised you, you have stopped listening and started confirming. Surprise is the signal that the reading is still live. The absence of surprise is not a sign you were right early. It is a sign you went deaf.

The synthesis third matters as much as the listening, and people underrate it because it looks like tidying up. It is not. Summarising interview notes into themes is tidying up. Synthesis is finding the small number of things that, once said, make the mess legible: the shape people recognise instantly because it was always there, just never named. That is the difference between the difference between strategy and operating reality and a themed summary of complaints.

Who is actually load-bearing

The org chart tells you who is senior. It tells you almost nothing about who is load-bearing.

Every organisation has a small number of people the whole operation quietly depends on. The ops manager who actually knows why the reporting process works the way it does. The account handler three people have gone to instead of their own manager for two years. The engineer nobody promoted who everyone routes blockers through. They rarely sit near the top of the chart, and they are almost never on the first list of names leadership hands you.

Ask for that list anyway, then build your own alongside it. You find the load-bearing people by asking everyone the same question: if you were stuck and it actually mattered, who would you go to? Three or four names keep coming back regardless of function or level. Those are the people to talk to properly, not as a box-ticking exercise squeezed in after the leadership interviews.

This matters because the load-bearing people are where the operating story and the operating reality diverge. Leadership knows the story. The load-bearing people live the reality. If your interview list is just the leadership team plus whoever they nominated, you will produce a very confident account of the story and learn almost nothing about the reality. The whole point of the operating leadership read is to get underneath the account leadership can already give you.

The operating story and the operating reality

Every leadership team has a story about how the organisation works. It is coherent, well-rehearsed, and frequently wrong, not through dishonesty but through distance. The CEO believes the sales process is stage-gated because that is what the CRM says. The reps know half of them skip stage three, because stage three adds a day and nobody has ever been penalised for skipping it.

You get at the reality through specifics, not opinions. Do not ask how the handover between sales and delivery works. Ask someone to walk you through the last deal they closed, from signature to the client's first meeting with the delivery team. Specifics drag people out of the rehearsed story and into what they actually did. Opinions invite the story straight back in.

The right-hand column is doing one job: forcing the answer down from the level of policy to the level of the specific Tuesday. Policy answers are the story. A specific Tuesday is the reality. Do this in enough interviews and the reality starts to repeat itself, and the repetition is your diagnosis forming.

That £40k line is not the interesting part. The interesting part is that it was invisible to everyone whose job it was to know. It lived in the gap between the story and the reality, which is exactly where the money and the pain usually sit.

Why a week-one recommendation costs you the engagement

Recommend early and you spend the trust the rest of the engagement runs on, and you will not get it back inside the same contract.

Here is the mechanism. A leadership team hires you because something is not working and they cannot see it clearly themselves. That is the whole premise. Hand them a fix in week one and one of two things is true. Either you solved in five days what they and their entire leadership team could not solve in however many months, which is unlikely and they know it is unlikely. Or you pattern-matched to a template you have used before and are selling it back with their org names inserted. They can smell the difference even when they cannot articulate it, and the smell that lingers is: this person does not actually know us yet.

Everything after that point gets read through a filter of "is this genuinely about us, or is this the template again." You have lost the one asset that makes the eventual recommendations land: the sense that you earned the right to make them. This is the same failure mode that sinks so many change programmes, and it is one of the reasons most change programmes fail before the first intervention is even chosen. The fix arrived before the understanding did.

The discipline is dull and it works: hold the recommendation until the synthesis is done, even when you are fairly sure by day ten. Being right early and staying quiet buys you more than being right early and saying so. The diagnosis you deliver on day thirty, backed by three weeks of specifics, lands. The same diagnosis blurted on day five, backed by a hunch, gets filed under "consultant with a template".

What the diagnosis has to be when you land it

The output of thirty days is a diagnosis the leadership team can repeat, in their own words, in a room you are not in.

That is the test. Not "did they nod at the readout" but "three weeks later, does the ops director explain the core problem to a new hire using language close to yours, without the deck in front of them." If they can, the diagnosis is durable. It has become their own understanding rather than your professional opinion delivered with confidence. If they cannot, if the readout impressed the room but nobody can reconstruct the argument afterwards, you built something persuasive rather than something true. Persuasive fades. True gets used.

Get the shape right and the recommendations that follow feel less like your idea and more like the obvious next move from a diagnosis everyone already agrees with. That is the whole return on the thirty days. It is also why a real diagnostic is worth paying for as its own step: the Grain Audit exists precisely because reading one process to the click level, before anyone touches it, is what makes the rebuild stick. Skip the read and you are redesigning a workflow you only half understand.

None of this is exotic. It is listening for longer than is comfortable, talking to the people the chart hides, chasing specifics instead of opinions, and holding your conclusions until they have earned the right to be conclusions. Do that and you will know what good looks like when you find it, because the signals of operating health show up in the reality column, never the story column. Thirty days well spent buys you exactly one thing: permission. Spend it on anything else and you will run the rest of the engagement without it.