The Diagnostic You Run Before You Hire Anyone
A consulting shortlist is the second decision. The first one was made in the sentence that described the problem, and it is usually the least evidenced line in the brief.
A consulting brief is usually a purchase order written from a guess.
By the time a company writes a brief, the decision that matters has already been taken. The brief names a scope, a deliverable, a date and a budget line, and all four sit downstream of one sentence somebody wrote about what is wrong. That sentence is the least evidenced part of the document, and it fixes everything after it.
It also arrives carrying authority it has not earned. Once a problem statement is circulated, it stops being a hypothesis and becomes the shared description of the company's situation. Firms respond to it, proposals get compared against it, and the comparison feels rigorous because three vendors are being scored on the same question. Nobody scores the question.
The shortlist is the wrong first move
So the buying process begins at the shortlist, which is the second decision, and treats the first as settled. A company that has not diagnosed itself is not choosing between consultants; it is choosing whose diagnosis to adopt. That is a defensible thing to buy, occasionally the right thing to buy, and expensive to buy by accident.
The correction is not to distrust the firms. It is to arrive holding enough of your own evidence to tell a good reading of the business from a fluent one. That takes a few weeks of internal work and no external fee, and it is the closest thing to a guaranteed return anywhere in the process.
Four questions separate a symptom from a brief.
The internal diagnostic is short. It is four questions, asked in order, and answered on paper rather than in a meeting where the most senior view wins on volume.
- What changed, and when? A number that has always been poor is a design problem. A number that fell in March is an event, and the event has a date.
- What has already been tried? Two years of attempts is a record of what the organisation believes about the cause. If those beliefs were right, the number would have moved.
- Which constraint is fixed, and which is inherited? Most constraints presented as immovable are decisions nobody has revisited since the person who made them left.
- Who can authorise the change? If the answer sits outside the sponsor's remit, the engagement will produce a recommendation and stop there.
Order matters more than depth
None of these are hard, and the temptation is to answer all four at once in a workshop. Asked out of order they collapse back into opinion. The point of the sequence is that each answer narrows the field the next question has to search, and by the fourth the problem has usually moved somewhere nobody expected when the exercise started.
That fourth question is the one most often skipped and the most predictive of how the engagement ends. A brief whose sponsor cannot authorise the change it implies is not a brief. It is a request for ammunition to use in an argument happening elsewhere in the business. Firms will take that work, and it rarely ends well for anyone in the room.
The evidence is already in the building, in documents nobody wrote for this.
A diagnostic does not need a new data-collection exercise. The most useful sources are records the company already keeps for other reasons, which is precisely why they hold up under reading: nobody curated them to make a case.
- The calendar, which shows where attention actually goes — what is protected, what is cancelled first, who is in the room when a trade-off is settled and who is briefed afterwards.
- The budget, which shows what has been committed against reversal: staffed permanently, funded by a project line that expires, or described as important and resourced as optional.
- The last three attempts at this problem, and the assumption each one was built on.
Interviews tell you what people will say
Stakeholder interviews are still worth running, but read them for a narrower purpose. They are a reliable record of what people are willing to say and a weak record of what the organisation does. The finding is usually the gap between the account a company gives of itself and the behaviour it funds.
Disagreement is the most valuable thing to come out of them. Two directors describing the same problem in incompatible terms means the organisation's model of itself has split, and the split tends to run along the line where the real cause is sitting. This is the same reading a good firm performs from the outside, described at more length in the work before the work. Done internally it costs nothing and takes a fortnight.
A named constraint changes what you are buying, not only who you buy it from.
The output of the diagnostic is one paragraph: what is happening, since when, what has been tried, which constraint is binding, and who can move it. It is short enough to be argued with, which is its entire function.
The brief that follows is a different document
Written from that paragraph, a brief stops asking for a deliverable and starts asking for an outcome. The difference shows up in the responses. A firm answering a symptom brief proposes its standard shape of work; a firm answering a named constraint proposes something specific, or declines. Both are useful answers, and only the second brief can produce either of them.
It also changes the price conversation. Scope written from a symptom has to be padded to cover the chance that the symptom is wrong, and the padding stays invisible until the third month. Scope written from a constraint can be narrow, because it knows what it is not doing.
A company that cannot describe its own problem will pay to be told what the problem is, and then pay again to have it solved.
The saving is real and secondary. The larger benefit is that the diagnosis stays in the company. When the engagement ends, the reasoning that produced it belongs to people who still work there, and the next problem gets the same treatment without a purchase order attached.
Running the diagnostic before the shortlist is where the thinking becomes work.
None of this is an argument against hiring anyone. Some constraints need capacity the company does not have, some need a method it has never built, and some need a person with no stake in which answer wins. Those are good reasons and they survive scrutiny.
Where it usually breaks
What does not survive scrutiny is hiring to settle an internal disagreement about the cause. That is the engagement which ships on time, reviews well, and leaves the number exactly where it was. It costs more than its fee, because it teaches the organisation that work of this kind does not change anything, and the next diagnosis — including a correct one — is harder to fund. The wider family of these patterns sits under diagnosis before solution.
The diagnostic is worth running even when the decision to hire has already been made, because it changes what the engagement is for. Where we do this alongside a leadership team it takes a few weeks, produces a paragraph, and often reduces the scope of the consulting work that follows. That is not a difficult trade to explain to anyone holding the budget.