Discovery Is the Engagement Before the Engagement
The single highest-leverage activity in consulting is the discovery conversation that happens before any work has been priced or scoped. A good discovery surfaces the real problem (which is often not the stated problem), maps the decision-makers, identifies what the client has already tried, and produces a scope the client recognises as theirs. A bad discovery produces an engagement that hits its milestones and still fails because it was scoped to the wrong question.
This guide covers the six frameworks I rotate between depending on the type of client conversation. None of them takes more than 45 minutes to run. All of them produce an artefact the client can react to, which is the test of a useful framework: it leaves something behind.
Framework 1: The Five Whys
The oldest and still the most useful. The client states a problem; you ask "why" five times in increasingly specific ways. The fifth "why" is usually the real problem.
- Stated problem: "We need a new operating model for our delivery team."
- Why 1: "Because the current model is not scaling." → Why is it not scaling?
- Why 2: "Because we cannot recruit fast enough." → Why can you not recruit fast enough?
- Why 3: "Because the roles we are advertising do not match the work we actually do." → Why is the work different from the advertised roles?
- Why 4: "Because we shifted into a different segment last year and the JDs never caught up." → Why have they not been updated?
- Why 5: "Because nobody owns the JD library; HR waits for hiring managers, and hiring managers wait for HR."
The real problem is not the operating model. The real problem is an ownership gap in the role-definition process. The engagement scope shifts from a six-month operating-model design (£300,000) to a three-month role-architecture and ownership intervention (£90,000) that the client is more likely to fund and that actually solves the issue.
Framework 2: The Job To Be Done
Borrowed from product management, but devastatingly useful in consulting. The question: "If this engagement worked, what would you hire it to do?" The answer is rarely a deliverable. It is usually a state — an internal political position protected, a board commitment honoured, a regulatory deadline met, a successor groomed.
Surface the job, and the engagement reshapes. A "strategy refresh" engagement whose real job is "give the CEO political cover for the cost programme already decided" needs a different methodology, a different audience plan, and a different communication strategy than a strategy refresh whose real job is "decide whether to enter the German market."
The discipline is to ask the question explicitly and write the answer down. The client may not say it, but you can say it back to them: "It sounds like what would make this engagement successful for you personally is X. Is that fair?" Their answer to that question is the brief.
Framework 3: The Stakeholder Map
A discovery conversation with only one stakeholder is a discovery half-completed. The stakeholder map identifies, in 20 minutes, who else has a vote on the engagement's success.
- Draw two axes: influence (low to high) and interest (low to high).
- Place the named stakeholders. The client will name 4–6 spontaneously; ask "who else would have an opinion on this?" three times to surface another 3–5.
- For each high-influence stakeholder, ask: what is their current view, what is their preferred outcome, what is the worst case for them.
The artefact that emerges is a stakeholder map you can email after the meeting with the implicit message: "this is what I understood; have I missed anyone?" It almost always provokes additions. Those additions are the people who would have killed the engagement quietly if you had not engaged them.
Framework 4: The "What We've Already Tried" Audit
Clients almost never come to consultants having tried nothing. They come having tried two or three things that did not work, and the unstated subtext is "do something different." A discovery that skips this question proposes the thing the client already tried last year and lost the room.
Two questions, in order:
1. "What have you tried so far?" Allow silence; the answer is rarely the first one offered.
2. "What did you learn from each attempt?" This is the gold. It identifies the patterns the client has already ruled out, the people internally associated with each failed attempt, and the appetite for risk on the next try.
An engagement designed around "this is what we will do differently from what you tried last year" is dramatically more saleable than the same engagement pitched on first principles.
Framework 5: The Decision Architecture
For engagements that exist to support a specific decision, map the decision before scoping the work.
- What decision will be made at the end of this engagement? Not "we will have insight"; "we will decide X."
- Who makes the decision? A specific named person or committee.
- By when does the decision need to be made? External deadlines (board, regulatory, contractual) versus internal preferences.
- What evidence would change that decision-maker's mind? This is the work the engagement actually has to deliver.
- What evidence would NOT change their mind? Equally important. Saves you from over-investing in analysis the decision-maker will discount.
The artefact: a one-page decision brief that names the decision, the decision-maker, the deadline, and the four or five evidence questions whose answers will move the decision. Every analytical workstream in the engagement maps back to one of those evidence questions. Workstreams that do not map back get cut.
Framework 6: The Sponsor's Risk Map
Used at the end of discovery to seal the engagement. The question to the sponsor: "What is the risk to you personally of this engagement going wrong?"
It is an unusual question. Most consultants do not ask it. The answer is always informative — political exposure if a particular conclusion lands the wrong way, career exposure if delivery slips, reputational exposure if a particular stakeholder feels excluded. The sponsor's personal risks shape the cadence, the communication plan, and often the methodology in ways the formal brief never captures.
Once named, the personal risks can be designed around. A sponsor who is exposed politically to one stakeholder gets a private steering committee briefing the day before each formal steering. A sponsor whose career depends on the engagement landing on time gets weekly milestone tracking even if the engagement is genuinely on track. None of this is in the contract; all of it earns the sponsor's loyalty.
Sequencing the Frameworks
You do not run all six in one conversation. The default sequence I use:
- First call (45 minutes): Five Whys + Job To Be Done. Surfaces the real problem and the real success criterion.
- Second call (60 minutes): Stakeholder Map + What-We've-Tried. Maps the political terrain.
- Third call (45 minutes): Decision Architecture + Sponsor's Risk Map. Locks the engagement design.
Three conversations, three to four hours of senior time, and the proposal that follows almost writes itself because the work has been done.
The Discovery Note
After each discovery conversation, send a two-page discovery note within 24 hours. The structure:
1. What I heard you say (3–5 bullets, in their language)
2. The questions that emerged (3–5 bullets, framed as further discovery, not as scope creep)
3. What I am preparing for our next conversation
4. Anything I have assumed that I would like to test
The discovery note is not a deliverable; it is a positioning instrument. It demonstrates that you listen, that you can summarise, and that you are systematic. Clients who have not yet decided whether to buy from you decide based on whether they want to receive more notes like this.
Where to Take This Next
- For converting discovery into a winning proposal, see the anatomy of a winning RFP response.
- For the analytical frameworks that follow discovery, see SWOT analysis for consultants.
- For the contracting step after the engagement is agreed, see contract clauses for consultants.