Overview
Scoping is not a framework with a single inventor — it is a foundational discipline of professional services, embedded in consulting firm training, project management methodology (the Project Management Institute's PMBOK Guide devotes significant coverage to scope management), and professional services best practice.
Two books address the consulting-specific version most usefully. Peter Block's Flawless Consulting (1981; third edition 2011, Pfeiffer) focuses on the contracting conversation between consultant and client — arguing that effective consulting begins with a genuine negotiation about both the business problem and the relationship. Paul Friga's The McKinsey Engagement (2009, McGraw-Hill) covers McKinsey's practical approach to structuring an engagement from kick-off through delivery, including explicit guidance on defining work scope.
The core problem scoping addresses is scope creep — the gradual, often imperceptible expansion of an engagement beyond its original intent. It happens in small steps: a client says "while you're at it, can you also look at…" and suddenly the team is doing twice the work with the same time and resources. In a 90-minute session, the analog is time creep: the team spends 40 minutes exploring one branch of the problem and arrives at the recommendation phase with nothing coherent to show.
The formal output of a scoping conversation in commercial consulting is a Statement of Work (SOW) — a written document specifying what the team will deliver, by when, and what is explicitly excluded. In Consulting Club, the Client Brief Template (see Session Kit) performs the same function.
When to Use It
At the very start of every engagement — immediately after, or simultaneously with, problem framing. Also when a client adds a new question mid-engagement: pause, evaluate whether the new question is within scope, and explicitly renegotiate if it isn't. Scope is always a negotiation, not a one-way declaration.
How It Works
A well-scoped engagement answers five questions:
1. Objectives — what is the engagement trying to achieve? Express in terms of outcomes, not activities. Not "we will analyze the competitive landscape" but "you will leave with a clear view of which two market segments offer the best growth opportunity."
2. Deliverables — what specific outputs will the team produce? A good deliverable is concrete, completable, and verifiable: a recommendation, a prioritized list, a decision framework. "Insights" is not a deliverable.
3. Constraints — what are the real boundaries? Time (90 minutes in a session), access (what data and people are available), and assumptions (what does the team take as given vs. test?).
4. Out-of-scope — what will the team explicitly not address? This is underused and underrated. Stating what's out of scope does two things: it prevents the team from wandering, and it manages the client's expectations. "We will not address implementation planning in this session" is not a failure — it's an honest boundary that focuses the work.
5. Success criteria — how will the client know if the engagement succeeded? "You'll have a recommendation you can take to your board" is a success criterion. "We'll do good analysis" is not.
Block argues in Flawless Consulting that the contracting conversation is as important as the technical work — a client who doesn't own the scoping won't own the recommendation. The consultant's job is to negotiate genuinely, not just take orders and start working.
Running It in a Session
During the Client brief, have the Scribe capture a quick scope statement on the board before team work begins. A useful template:
"We are trying to answer: [question]. We will produce: [deliverable]. We will not address: [out-of-scope items]. We'll know we succeeded if: [success criterion]."
Take 90 seconds to read it back to the Client. If the Client says "actually, I also need you to cover X," the Lead Consultant should make a judgment call: is X additive (same analysis, broader coverage) or substitutive (different problem, different approach)? If substitutive, renegotiate the scope explicitly before proceeding — not mid-session.
This is one of the clearest differentiators between teams that deliver coherent recommendations and teams that deliver interesting-but-unfocused presentations. The teams that drift almost always skipped this step.
Common Pitfalls
- Vague objectives — "help us improve" is not an objective; push for something concrete and evaluable, even in a 90-minute session
- No out-of-scope list — if everything is potentially in scope, nothing is; the absence of explicit exclusions is an open invitation to drift
- Scope as contract rather than conversation — real consultants renegotiate scope when they discover the problem is different than expected; treat the scope statement as a working hypothesis, not a binding obligation
- Over-scoping to impress — promising more than the time allows; better to deliver one sharp recommendation than three half-finished ones
- Confusing output with outcome — "a 20-page report" is an output; "a decision you can make with confidence" is an outcome; scope around outcomes whenever possible
References & Further Reading
- Block, Peter. Flawless Consulting: A Guide to Getting Your Expertise Used (1981; third edition 2011, Pfeiffer)
- Friga, Paul N. The McKinsey Engagement (2009, McGraw-Hill)
- Project Management Institute. A Guide to the Project Management Body of Knowledge (PMBOK Guide) — Scope Management chapter
Recommended Books
- Flawless Consulting — Peter Block
- The McKinsey Engagement — Paul Friga
- The Trusted Advisor — Maister, Green & Galford