The Case for Scoping Down: Why UK Small Businesses Often Get More From a Narrower Brief
Photo: Reinhard Kirchner, CC BY-SA 3.0, via Wikimedia Commons
There is a familiar document in British small business life: the consultancy brief that asks for everything. It wants a review of the operating model, a refreshed marketing strategy, some work on the finance function and, if there is time, a look at the website. It is a genuine expression of how an owner feels — that the business is tangled and someone competent should untangle it — and it is almost always a mistake.
My view, formed from watching these engagements succeed and stall in roughly equal number, is that a narrower brief consistently outperforms a wider one. Not because ambition is wrong, but because a wide brief asks several different questions at once, and a consultancy proposal can only answer them all by answering none of them properly.
Why broad briefs fail quietly
A sprawling brief fails politely. The final report arrives, it is competent, it covers everything, and nothing changes. Nobody complains, because the supplier did what was asked.
The failure is structural. When a brief spans four areas, the adviser allocates time across four areas, and the depth possible in each falls accordingly. Reviews and diagnoses are easy to produce and hard to act on, so the document becomes a list of observations that the owner already half-knew. The £25,000 fee has bought reassurance and a set of slides.
There is a second, quieter cost. A wide brief makes it impossible to judge whether the work was any good. If you asked for everything, you cannot say whether you received enough. A narrow brief sharpens the test to something almost binary: was the decision made, was the process running, was the thing delivered?
One decision, one deliverable, one process
The practical move is to reduce the ambition to a single unit of change. Three forms work well.
One decision. Not 'review our pricing' but 'recommend a price structure for our three core services, with a plan to move existing customers to it by the spring'. Same territory, but now there is a question that can be answered and a date by which it matters.
One deliverable. Not 'improve our reporting' but 'produce a monthly management pack we can produce ourselves in two hours by the end of the quarter'. The output is inspectable, and the test of success is whether it exists and runs.
One process. Not 'sort out operations' but 'redesign the quote-to-invoice process so that average time from enquiry to invoice falls by a third'. Measurable, bounded, and useful.
Each version does something the broad brief cannot: it names the change and, in doing so, names what is not being done. That exclusion is the point, not a limitation.
A simple scope-narrowing exercise
Set aside forty-five minutes with a whiteboard, or a sheet of A3 if the whiteboard is being used for other things.
- Write the wide ambition at the top in plain words, as an owner would say it: 'we need to get our growth under control'.
- Below it, list every distinct question the ambition contains. Expect six to ten. This is the honest size of the tangle.
- For each question, write two things: what would change if it were answered, and by when. Anything with no consequence and no date leaves the list.
- Rank what remains by the cost of leaving it alone for another six months. Not by interest, not by tidiness — by consequence.
- Take the top item only. That is your brief. Everything else becomes a numbered follow-on that you may or may not commission later.
The discipline is uncomfortable, because it feels like postponing problems. In practice the top item usually shifts the others: fixing pricing changes the conversation about margins, and redesigning a process often makes a systems decision unnecessary.
Setting boundaries that hold
The brief is only half the work. The boundary has to survive contact with a helpful adviser and an anxious owner.
Write into the engagement what will not be covered. Ask for the exclusions in the proposal to be listed as clearly as the inclusions. Agree how a new question gets handled — usually it goes on a list, not into the current piece of work — and agree who can authorise that list to grow. Without that mechanism, a narrow brief widens within a fortnight, and the benefit disappears while the invoice does not.
It also helps to fix a review point halfway through, not to re-scope but to confirm the original question is still the right one. Sometimes it will not be. That is worth knowing early, and it is a decision in its own right rather than a failure of planning.
Why the smaller brief is easier to price and to judge
Narrow scope does something commercially useful: it makes the price legible. An adviser quoting for a bounded piece of work can estimate with reasonable confidence, which means a fixed fee becomes genuinely fixed rather than a placeholder. Timelines compress and become defensible. Success criteria can be written down before anyone starts, which is the single most reliable protection a client has.
A narrow brief also respects the real constraint on most UK SMEs, which is not the consultancy budget but the owner's own attention. Every engagement consumes management time to brief, review and act on. A wide project demands months of scattered attention; a narrow one asks for a focused fortnight and a decision at the end.
When a wider view is right
There is a counter-argument, and it deserves a hearing. Sometimes the business genuinely does not know where the problem lies, and a broad diagnostic is the honest starting point. That is a legitimate case — but note what it is: a diagnostic, deliberately scoped, with the expectation that it produces a shortlist rather than a transformation. Even then, the deliverable should be one thing: a prioritised set of two or three options, with a recommendation.
Ambition does not have to be spent all at once. A sequence of narrow, well-judged pieces of work tends to accumulate into more change than a single sweeping programme ever does — and it leaves the owner with something better than a report: a record of decisions that were actually made.