Why operational diagnostics fail before they start
An operational diagnostic is supposed to tell you where your organisation is losing time and money. Most of them do exactly that. The analysis is sound, the recommendations are reasonable, and the report sits in a shared drive for six months before anyone looks at it again. The diagnostic did not fail because the analysis was wrong. It failed before the first interview was conducted.
The sponsor problem
Every diagnostic needs a sponsor: someone with enough authority to act on the findings and enough genuine curiosity to want to know what they will say. Without that person, the report has nowhere to land. It gets circulated, acknowledged, and quietly shelved.
The sponsor does not need to be the most senior person in the organisation. They need to be the person who will still care about the findings in six weeks, when the initial energy has faded and the recommendations are competing with everything else on the agenda. Finding that person before you start is the first thing to establish.
Scope that is too broad to be actionable
A diagnostic that covers everything produces findings that apply to everything, which means they apply to nothing in particular. The most useful diagnostics are deliberately narrow: one process, one team, one decision type.
When a client asks us to look at 'how the organisation works generally', the first thing we do is spend time narrowing the scope. Not because broad questions are uninteresting, but because broad findings do not produce clear owners or clear next steps. A recommendation that says 'improve communication across the business' is not a recommendation. It is a wish.
Interviews without psychological safety
The quality of a diagnostic depends almost entirely on the quality of the conversations that feed it. People will tell you what they think you want to hear, or what they think is safe to say, unless the conditions are right for honesty.
We conduct interviews individually, not in groups. We do not share attribution without permission. We tell people explicitly that the goal is to understand how things actually work, not to assign blame. Those conditions take time to establish, but they are the difference between a diagnostic that surfaces real problems and one that confirms what the leadership team already believed.
A diagnostic that works has a named sponsor, a narrow scope, and interview conditions that produce honest answers. It also has a clear plan for what happens after the report is delivered: who reads it, who discusses it, and who is responsible for deciding what to act on. That plan should be agreed before the diagnostic begins, not after.
If you are considering a diagnostic and want to talk through whether the conditions are right, the discovery call is the right place to start.