The word diagnostic gets used a lot in consulting, often to mean different things. Some firms use it to describe a two-hour conversation before they propose a larger engagement. We use it to describe a structured four-week process that produces a written findings report with prioritised recommendations. This article explains what that process looks like in practice.
Why start with a diagnostic at all ¶
The instinct when something is not working is to fix it. The problem is that the thing that appears to be broken is often not the actual source of the problem. A leadership team that cannot agree on priorities might have a strategy problem, or it might have a meeting design problem, or it might have a single interpersonal dynamic that is suppressing honest conversation. Treating the wrong problem is expensive. A diagnostic review is designed to establish what is actually happening before any recommendations are made.
What happens in the four weeks ¶
Week one is interviews. We speak individually with each member of the leadership team and, depending on the organisation, with two to four people at the level below. The conversations are confidential and follow a consistent structure, though they rarely feel like a formal interview. Week two is document review and process observation. We look at how decisions are currently made, how information flows, and where the gaps are. Weeks three and four are analysis and writing. We draft the findings, test them against the evidence, and prepare the report.
What the report contains ¶
The report has three sections. The first is a one-page summary of the three to five findings that matter most, written without qualifications or consulting language. The second is a prioritised action list, with each item assigned to a realistic owner and timeframe. The third is the supporting detail for those who want to understand the reasoning behind each finding. The debrief conversation, which is included in the engagement, is where we work through the findings together and discuss what to do next.
What a diagnostic does not do ¶
A diagnostic review is not a strategy. It does not tell you where to take your business. It tells you what is currently getting in the way of executing whatever direction you have chosen. If the findings suggest that the strategy itself needs revisiting, we will say so, but that is a separate piece of work. Keeping the diagnostic focused on the operational and organisational reality is what makes it useful.
Who it is most useful for ¶
The diagnostic review tends to be most valuable for organisations that have grown quickly and feel like the internal machinery has not kept up, for leadership teams that are about to make a significant decision and want a clear picture of where they are starting from, and for businesses that have tried to fix the same problem more than once without it staying fixed. If any of those descriptions fit your situation, it is probably worth a conversation.
If you would like to understand whether a diagnostic review makes sense for your organisation, the best starting point is a thirty-minute call. There is no preparation required on your side.