What the Brief Takes for Granted: A Board-Level Audit of Consultancy Problem-Setting

The problem statement is the most consequential page in a consultancy proposal. It determines what data are gathered, which options are considered, who is interviewed and how success will be judged. Yet boards often scrutinise fees, timelines and team credentials while accepting the problem frame as a neutral description of reality. It is not neutral. A diagnosis is an argument: it selects facts, links them causally and ranks some issues above others. Before a UK firm buys that argument, it should audit the assumptions on which it rests.

The diagnosis is a claim about cause

A consultant's problem definition typically contains three kinds of claim. There are observations, such as a falling margin or a slow approval process. There are causal claims, such as the assertion that slow approvals are driving the margin decline. And there are priority claims, such as the judgement that this issue matters more than pricing, procurement or customer retention. Boards should ask which of these claims are evidence-backed and which are working hypotheses dressed as findings.

This is not a counsel of suspicion. Specialist advisers bring pattern recognition that internal teams may lack. But pattern recognition is not proof. The board's task is to establish whether the problem has been defined with enough rigour that a substantial engagement is justified.

Premise inventory: what is being treated as fixed?

Every diagnosis treats some things as fixed and others as variable. A proposal may assume that customer demand will remain broadly stable, that the firm's cost base is structurally uncompetitive, or that a particular regulatory constraint cannot be changed. Some of these assumptions will be sound. Others will be inherited from the brief, repeated from an earlier strategy document, or simply untested.

A useful first step is a premise inventory. The board should ask the consultant to list the five or six assumptions on which the problem definition depends. For each one, three questions follow: Is this an external constraint or a self-imposed one? What evidence supports it? What would change if it were false?

This can be kept to a single page. A simple assumption register, with columns for the premise, its type, the evidence offered, the confidence level and the proposed test, is often enough to expose whether the diagnosis rests on analysis or convention.

Separate observation from inference

Consultancy reports frequently blend what was seen with what it is taken to mean. A customer interview programme may reveal that clients value speed of response. That is an observation. The inference that the firm should therefore restructure its account management model is a separate claim. The inference may be correct, but it requires its own support.

Boards should ask for the evidence hierarchy. Which findings come from primary data? Which come from the consultant's prior engagements? Which are sector analogies? None of these is invalid, but they carry different weight. A diagnosis built mainly on analogy should be labelled as such, and the board should consider whether the firm's circumstances are similar enough for the analogy to hold.

The counterfactual test

The most efficient test of an assumption is to invert it. If the opposite were true, would the recommended scope still make sense? If the answer is no, the assumption is load-bearing and deserves close examination. If the answer is yes, the board can reasonably ask why the assumption features so prominently in the diagnosis.

A related question is what evidence would cause the consultant to revise the problem definition. A diagnosis that cannot be falsified is not a diagnosis; it is a position. Boards should expect advisers to identify the signals that would prompt a change of direction, and to say how those signals will be monitored during the engagement.

Check the constraints against reality

UK firms in 2026 operate under real constraints: labour availability in specialist roles, energy and property costs, access to growth capital, regulatory obligations and, for many, the practical limits of management bandwidth. A diagnosis that treats a self-imposed constraint as an external one can produce a recommendation the firm cannot implement. A diagnosis that treats an external constraint as self-imposed can produce a plan that ignores the limits within which the firm must operate.

The board should therefore ask the consultant to distinguish between constraints that are genuinely immovable within the engagement window and those that are simply inconvenient. Where a constraint is asserted, the board should ask who verified it and on what basis.

Retain authority over the question

The board does not need to become the consultant. It does need to retain authority over the question being answered. That means resisting the drift from a broad concern into a narrow scope before the problem has been properly framed. It also means reserving the right to reframe the engagement if the assumptions do not hold.

A practical way to do this is to make the assumption audit a condition of the engagement. The consultant should be asked to present the diagnosis and its underlying premises to the board or a committee before the main work begins. The board should then record which assumptions it accepts, which it requires to be tested and which it rejects. That record becomes a governance asset: it gives the board a basis for reviewing progress and a reference point if the engagement later loses its way.

An audit agenda for the next board meeting

Six questions are usually enough to begin. What is the problem statement, and what is it not? Which premises are treated as fixed, and what evidence supports them? Which claims are observation, which are inference and which are analogy? What would have to be true for the diagnosis to be wrong? Which constraints are external and which are self-imposed? And what would cause the consultant to revise the problem definition?

The answers will not always be comfortable. But a board that asks them before committing budget is doing what governance requires: testing the argument before buying the answer. The alternative is to fund a solution to a problem that was never properly defined, and to discover the gap only when the final report arrives.