How to diagnose an organisation in 30 days

The diagnostic is not the work. The diagnostic is the permission to do the work.

Most consultants skip it, or fake it. They turn up with a framework already in their back pocket, run a handful of interviews to make the framework feel bespoke, then present it back with the client's logo on the front. That is decoration dressed as diagnosis. Thirty days done properly buys you something a framework never can: the right to be believed when you say what's actually wrong.

The maths of the 30 days

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

That's roughly twenty days of interviews, shadowing and document review, then eight or nine days pulling the threads together, then a landing. 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 that was reached in week one.

You'll know you're doing it right because week three feels uncomfortable. You should still be finding things that contradict what you thought in week one. If by day 15 nothing has surprised you, you've stopped listening and started confirming.

Who you actually need in the room

The org chart tells you who's senior. It tells you almost nothing about who's 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 the last two years, the engineer nobody promoted who everyone routes around blockers through. They rarely appear near the top of the chart. They are almost never in the first list of names leadership hands you.

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

This matters because the load-bearing people are the ones who know where the operating story and the operating reality diverge. Leadership knows the story. The load-bearing people live the reality.

The story versus the reality

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

The story is what leadership believes happens. The reality is what happens on Tuesday, at 4pm, when someone is behind on a deadline and takes the shortcut that actually gets the work out. Your job for the first twenty days is to build a picture of Tuesday-at-4pm, not a picture of the strategy deck.

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

Why week one recommendations kill the engagement

Recommend early and you've spent the trust the rest of the engagement runs on, and you won't get it back inside the same contract.

Here's the mechanism. A leadership team hires you because something isn't working and they can't see it clearly themselves, that's the whole premise. If you hand them a fix in week one, one of two things is true. Either you've solved in five days what they and their whole leadership team couldn't solve in however many months, unlikely, and they know it's unlikely. Or you've pattern-matched to a template you've used before and are selling it back to them with their org names inserted. They can smell the difference between the two, even if they can't articulate it, and the smell that lingers is: this person doesn't 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've lost the one asset that makes the eventual recommendations land: the sense that you earned the right to make them.

What the output actually needs to be

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

That's 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 needing the deck in front of them." If they can, the diagnosis is durable, it's become their own understanding rather than your professional opinion delivered with confidence. If they can't, if the readout impressed the room but nobody can reconstruct the argument afterwards, you've built something persuasive rather than something true. Persuasive fades. True gets used.

That's also why the synthesis third of the thirty days matters as much as the listening. Synthesis isn't summarising interview notes into themes. It's finding the two or three things that, once said, make forty separate observations click into a single coherent shape, the kind of shape people recognise instantly because it was always there, just never named. Get that shape right and the recommendations that follow feel less like your idea and more like the obvious next step from a diagnosis everyone in the room already agrees with.

Thirty days well spent buys you exactly one thing: permission. Spend it on anything else and you'll be running the rest of the engagement without it.