How to scope a consulting problem before you start

Most consulting engagements that go wrong do not go wrong because of bad analysis or poor facilitation. They go wrong because the problem was scoped incorrectly at the start. The presenting issue and the actual issue are often different things, and the gap between them is where projects quietly fail.

The presenting problem is rarely the whole problem ¶

When an organisation brings in outside help, they usually arrive with a description of what is wrong. That description is honest and well-intentioned. It is also shaped by what is visible from inside the organisation. The symptoms that have become impossible to ignore, the complaints that have reached a certain volume, the metrics that have moved in the wrong direction.

What is harder to see from inside is the structural or historical reason those symptoms exist. A team that cannot agree on priorities is a visible problem. The unmade decision from eighteen months ago that created the conflicting priorities is the actual problem. Scoping well means finding the second thing, not just accepting the first.

Three questions worth asking before agreeing to anything ¶

First: what would have to be true for this framing to be correct? If the brief says 'our operations are inefficient', what assumptions does that rest on? Are those assumptions tested or inherited? Second: who was not involved in writing this brief, and what do they think the problem is? The people closest to the work often have a different read than the people who commissioned the review. Third: what has already been tried? Understanding the history of attempts to fix a problem tells you a great deal about what the organisation is actually willing to change.

What good scoping produces ¶

A well-scoped engagement has a written problem statement that the client and the consultant have both agreed to. It names the decision or change the work is designed to support. It identifies who needs to be involved and who needs to be kept informed. And it includes an honest note about what the work will not cover. Because scope boundaries matter as much as scope content.

This does not need to be a long document. One page is usually enough. The discipline of writing it is the point.

If you are considering bringing in outside help and want to think through how to frame the problem first, the initial conversation at Smart Willow Works is always free.