Clients rarely hand you their real problem. They hand you their guess at a solution, dressed as a brief. If you accept it at face value, you deliver exactly what was asked and still disappoint them. This article shows you how to separate the stated request from the underlying problem, how to reframe without seeming to argue, and how to confirm you have found the real issue before any work begins. You will gain a repeatable diagnostic method.
Why the brief is almost never the problem
A brief is the client’s conclusion after private reasoning you did not witness. “We need a new website” is a solution. The problem might be that qualified leads are not converting, or that sales cannot explain the product, or that a board member simply dislikes the old design. Each of those leads to completely different work.
The nature of the gap is not that clients are careless. It is that people compress a messy situation into a concrete ask because concrete asks feel actionable. Your job is to decompress it safely, without making the client feel second-guessed.
Symptom, cause, and desired outcome
Three different things hide inside most briefs. Pull them apart deliberately.
| Layer | Example phrasing | What it really is |
| Proposed solution | “We need a rebrand” | The client’s hypothesis |
| Symptom | “Sales have been flat for a year” | The observable pain |
| Root cause | “Our best segment stopped renewing” | The thing worth fixing |
| Desired outcome | “Renewals back above 85 percent” | The real definition of success |
When you can fill all four rows, you understand the engagement. When you can fill only the first, you are being paid to guess.
How to reframe without friction
The risk in challenging a brief is that the client feels corrected. Avoid this by asking rather than asserting. Two questions do most of the work: “What would have to be true for this to succeed?” and “If we solved this perfectly, what changes in the business?” Both invite the client to reveal the outcome behind the request without you contradicting them.
The five-why in a business setting
Ask why the request matters, then why that matters, and keep going gently. “We need a new website” becomes “because leads are not converting,” which becomes “because visitors do not understand the offer,” which becomes “because the offer itself changed and messaging never caught up.” The real work might be positioning, not web design.
A real scenario
A B2B services firm asked a consultant to run leadership training because “managers are not performing.” The obvious engagement was a training program. Before scoping it, the consultant spent two days interviewing managers and their reports. The pattern was clear: managers understood their jobs but had no authority to make decisions, no clear targets, and conflicting instructions from two executives. Training would have taught skilled people to perform in a system that blocked them. The real problem was decision rights and unclear ownership. The reframed engagement redesigned accountability, and performance improved without a single training session. Had the consultant delivered the requested brief, the money would have been spent and the problem untouched.
Confirming you found the real problem
Do not trust your reframe until the client recognizes it. State the problem back in one sentence and watch the reaction. Genuine recognition looks like relief or a quick “yes, exactly.” Polite agreement without energy usually means you are still on the surface. Ask what evidence would confirm the problem is solved; if they cannot answer, keep digging.
Common mistakes and how to fix them
Mistake: accepting the brief to win the deal. It feels cooperative and often loses trust later. Fix: show value in the diagnosis itself, so reframing looks like expertise, not resistance.
Mistake: reframing too aggressively. Telling a client their brief is wrong triggers defensiveness. Fix: use questions, and let the client arrive at the reframe with you.
Mistake: talking only to the sponsor. The person who wrote the brief often sees one angle. Fix: interview the people who live with the problem daily; they hold the real cause.
Mistake: confirming the problem in your own head only. Fix: state it back and require the client to recognize it before scoping.
Action checklist
- Write the brief down and label it as a proposed solution, not the problem.
- Separate symptom, likely cause, and desired outcome on paper.
- Ask what would have to be true for the request to succeed.
- Interview at least two people who are not the sponsor.
- State the reframed problem in one sentence and confirm recognition before scoping.
Conclusion and next step
The difference between a vendor and a trusted advisor is one habit: refusing to start work until the real problem is on the table. Your next step is simple. On your current brief, write the four layers, symptom, cause, solution, and outcome, and find which rows you cannot yet fill. Those empty rows are your first conversation.
FAQ
What if the client insists their brief is the problem?
Respect it, then ask what success looks like in business terms. If their measure of success can only be reached by addressing something deeper, the reframe surfaces on its own without you arguing. Let their own outcome do the persuading.
How much diagnosis is enough before scoping?
Enough to fill the symptom, cause, and outcome layers with evidence, not assumption. For most engagements a few targeted interviews and one honest metric are sufficient. Stop when the client recognizes the problem statement, not before.
Does reframing risk losing the sale?
It can feel that way, but delivering the wrong solution costs you the relationship and any referral. A sharp diagnosis usually raises your perceived value, because clients rarely experience someone taking the problem seriously before pitching.
How do I reframe when I only have one short meeting?
Use the two anchor questions: what has to be true for this to work, and what changes in the business if we nail it. Even in one conversation these move the discussion from solution to outcome, which is where the real problem lives.
References
Edgar Schein, Humble Inquiry, on asking rather than telling to surface real problems. Thomas Wedell-Wedellsborg, What’s Your Problem?, on reframing before solving.