What a real diagnostic looks like
A diagnostic is not an assessment. The two have been conflated for so long that operators no longer expect the distinction to matter. It does.
An assessment describes what is happening. A diagnostic identifies what is causing it.
The difference shows up in the work.
An assessment is built from data the operator hands over. Financials. KPIs. Customer reports. Org charts. The assessor reviews what the operator already has and produces a document that reflects, with marginal additions, the operator's existing view of the business.
A diagnostic is built from inside the operation. The diagnostician sits with the controller for a day to understand why month-end takes nine business days. They walk the floor and count the judgment calls that should be in a spec. They ride along on a sales call to see who actually closes the business. They read the last six months of executive emails to identify the recurring decisions that route through the founder.
This is different work, and it produces different findings.
The constraints, dependencies, and decision rights that are actually governing performance are usually not visible in the data the operator hands over. If they were, the operator would have addressed them already. The diagnosis lives in what is missing from that data, and the only way to find it is to be inside the operation rather than across a conference table from it.
A real diagnostic is also time-boxed.
Most consulting engagements expand to fill the time available. The scope grows, the analysis deepens, the document gets longer, and the decision the operator is trying to make recedes. By the time the work is delivered, the market conditions have shifted, and the operator is paying for analysis that is calibrated against a business that no longer exists.
A diagnostic that takes 14 days produces a diagnosis within a window that does not allow the work to drift. It also forces the diagnostician to focus on what actually matters, because everything that does not fit into 14 days has to be cut. The cuts are usually the right cuts.
A real diagnostic ends with a decision, not a conclusion.
A conclusion is informational. The operator is left to decide what to do with it. A decision memo is structured as a decision. It identifies the two or three highest-priority initiatives the business should commit to, the resourcing required, the leadership decisions that have to be made, and the outcomes that should be measurable within the first quarter of execution.
The operator reads it and either commits or does not. There is no ambiguity about what comes next.
This is the standard. Built from inside the operation. Time-boxed to 14 days. Ending with a decision.
Anything less is an assessment, and the operator already has enough of those.
- DIAGNOSTIC
The Composition Diagnostic
Most middle market businesses have been assessed before. The assessments produced documents. The documents identified problems. The problems mostly persisted. This is not because the assessors were wrong. It is because an assessment is not a diagnostic, and the two have been conflated for so long that operators no longer expect the distinction to matter.
5 MIN READ - DIAGNOSTIC
Twelve things we have learned about diagnosing middle market businesses
Most performance problems are governance problems wearing operational costumes. The constraint is rarely where the dashboard points. Twelve field notes from current engagements.
1 MIN READ