The Composition Diagnostic
What we look for in the first 14 days, and why most assessments do not produce action.
Most middle market businesses have been assessed before. By a consultant, by a banker, by a private equity firm during diligence, by an internal task force commissioned after a bad quarter. 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. It does.
An assessment describes what is happening. A diagnostic identifies what is causing it, distinguishes it from what is downstream of it, and produces a prioritized sequence of actions that, if executed, would change the trajectory of the business. The first is a document. The second is the beginning of an engagement.
The Composition Diagnostic is the second. It is a 14-day engagement, embedded inside the operation, that produces five deliverables and a decision. It is the entry point to most of our work, and it is structured the way it is because we have learned, across enough engagements, that the discipline of the first 14 days determines whether anything that follows produces results.
Below are the four conditions that distinguish a diagnostic that produces action from an assessment that produces a binder.
1. A diagnostic is built from inside the operation, not from data the operator hands over.
Most assessments are built on data the operator provides. Financials. KPIs. Org charts. Customer reports. The operator hands over what they have, the assessor analyzes it, and the resulting document reflects the operator's existing view of the business, with marginal additions.
This is the structural flaw. The data the operator hands over is a description of how the operator already sees the business. The constraints, the dependencies, and the decision rights that are actually governing performance are usually not visible in that data, because if they were, the operator would have addressed them already.
A real diagnostic is conducted from inside the operation. We sit with the controller for a day to understand why month-end takes nine business days. We walk the floor and count the judgment calls that should be in a spec. We ride along on a sales call to see who actually closes the business. We read the last six months of executive emails, when permitted, to identify the recurring decisions that route through the founder. None of this is available in the data the operator hands over. All of it is available within 14 days if you are willing to be inside the operation rather than across a conference table from it.
The deliverables that come out of this work are different from the ones that come out of a desk-based assessment. The operational baseline reflects what the operation actually does, not what the dashboards say it does. The constraint map identifies the decisions and dependencies that are governing performance, not just the line items that are moving. The work that follows has a chance of producing change because the diagnosis is calibrated against the real operation.
2. A diagnostic is time-boxed because indecision is the most expensive condition in a middle market business.
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, the management team has lost momentum, and the operator is paying for analysis that is calibrated against a business that no longer exists.
The 14-day boundary on the Composition Diagnostic is not a marketing decision. It is an operational discipline. A diagnostic that takes 14 days produces five deliverables and a decision memo within a window that does not allow the work to drift. It also forces the diagnostic team 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.
The faster cycle also reflects how middle market operators actually run their businesses. The decisions that need to be made are not strategic positioning decisions that will play out over five years. They are operational decisions that need to be made this quarter, and the diagnostic exists to inform them. A 90-day strategic review is not an asset to a middle market operator. It is a delay disguised as rigor.
The time-box also disciplines us. We have made the choice to be the firm that produces a diagnosis in 14 days rather than the firm that produces a more comprehensive document in 90. Our experience is that the marginal value of the additional 76 days is low, and the cost in terms of organizational momentum and operator decision speed is high. The 14-day window is a feature, not a constraint.
3. A diagnostic produces a sequenced plan, not a list of recommendations.
The standard consulting deliverable is a list of recommendations, prioritized by impact and effort, with a roadmap that suggests the operator should do everything. The roadmap is a fiction. No middle market business has the bandwidth to execute against more than two or three real initiatives at a time, and the operator knows this, which is why the roadmap usually gets filed and forgotten within six months.
A diagnostic produces a sequenced plan. The sequence matters more than the list, because the order in which work gets done determines whether the work produces compounding results or whether each initiative gets undermined by the conditions that should have been addressed first. Building a customer experience program before fixing the operational variance that is producing the customer experience problem is a sequencing error. So is investing in AI before the back-office tasks have been inventoried. So is implementing a new ERP before the data governance has been established. The recommendations are not wrong. The order is wrong.
The Composition Roadmap, which is the fourth deliverable in the diagnostic, is the sequence. It identifies what should be done first, what depends on what, and what should not be started until specific conditions are met. The operator gets a plan that reflects how change actually happens in a middle market business, which is one initiative at a time, with each initiative building the foundation for the next. This is more useful than a comprehensive list, because it is executable.
4. A diagnostic ends with a decision, not a conclusion.
Most assessments end with a conclusion. The business has these strengths. The business has these weaknesses. Here are the recommendations. The conclusion is informational, and the operator is left to decide what to do with it.
The Composition Diagnostic ends with a Decision Memo. The memo is structured as a decision, not a conclusion. It identifies the two or three highest-priority initiatives the business should commit to in the next 90 days, the resourcing required, the leadership decisions that have to be made for the work to proceed, and the specific outcomes that should be measurable within the first quarter of execution. It is short, direct, and actionable. The operator reads it and either commits or does not. There is no ambiguity about what comes next.
This is also where the credit-against-engagement structure matters. The diagnostic is paid work. If the operator chooses to proceed with QompoS on the work the diagnostic identifies, the diagnostic fee credits against the engagement. This is not a sales discount. It is a structural alignment. We are not incentivized to identify problems we cannot help solve. The operator is not incentivized to engage us on work that does not need doing. The diagnostic produces a real diagnosis, and the work that follows is the work the diagnosis warrants. If no further work is warranted, the diagnostic stands on its own as a deliverable.
The Standard We Hold
We have written this insight because we want operators to know what to expect when they engage us. The 14 days are intense. We will be inside the operation. We will ask questions that other firms have not asked. We will produce deliverables that are direct, specific, and uncomfortable in places, because that is what a real diagnostic produces. We will end with a decision memo, and we will expect a decision.
We do not advise. We compose. The diagnostic is where composition begins.
- 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 - DIAGNOSTIC
What a real diagnostic looks like
An assessment describes what is happening. A diagnostic identifies what is causing it. The two have been conflated for so long that operators no longer expect the distinction to matter. It does.
3 MIN READ