“We built exactly what they asked for - and then discovered it wasn’t what they actually needed.” The request was clear. The work was good. The problem was the question.
You assume the requester already knows the real problem. They wrote it down; they were specific, so you answer the question you were given rather than checking whether it’s the right one. But the real question is often unstated - and frequently unknown even to the person asking.
The first question is rarely the one that needs answering. Solve it perfectly, and you can still solve the wrong problem. The requester usually isn’t wrong - they’re answering the wrong question. This is a quick check that surfaces the difference before you build anything.
Example: the request is “build us a dashboard showing weekly sales by region.” You reply: “so we’d build a page with a regional sales chart, updated every Monday - you’d open it each week and read the numbers.” The requester pauses: “actually, I don’t want to read it weekly. I want to know when a region drops.” The real question wasn’t a dashboard. It was an alert.
You play back what you would actually build. Not a summary of the request - the thing itself. “If we did exactly what you asked, here’s what we’d build…” Then describe it concretely enough that the requester can picture it.
The gap does the work - the difference between what was asked and what’s needed. Hearing their own request turned into a real, specific thing is what makes the requester say “wait - that’s not quite what I need.” They can’t see the wrong answer in the abstract; they can see it the moment it’s described back to them.
You restate the question and confirm it. Write the real question in one sentence and read it back. You’re done when the requester says: “yes - that’s what I actually needed.”
Solo or with the requester ✓ About 10–15 minutes - a short conversation, not a workshop.
The time required is indicative and will depend on how far the stated request sits from the real need.
The short facilitation guide takes about 5 minutes to read. It is a downloadable PDF on this page.
Use it on any request you’re about to act on - especially a clear, well-written one.
Use it whenever:
You’ve done it well when: the requester says “yes - that’s what I actually needed,” and the restated question is different from the one you were handed.
People can’t understand a request in the abstract - but they can instantly recognise a wrong answer once they see it. Playing back the concrete thing you would build turns an abstract ask into something the requester can picture, and the mismatch becomes obvious to them, not just to you. That also solves the sensitive part: you’re not challenging their judgement or pushing back on the request. You’re showing them what their words would produce and letting them correct it. The real question usually surfaces in their reaction.
A real request you’re about to act on. A specific ask - a brief, a ticket, a feature request - that you haven’t started building yet.
The requester (5–10 minutes). The person who made the request needs to hear the play-back and react to it. This doesn’t work by email alone.
The willingness to describe, not summarise. The play-back must be concrete - the actual thing you’d build, described so they can picture it. A summary of their request reveals nothing.
Output
You leave with:
Important rules
Keep it short. This is a ten-minute check, not a discovery workshop. If the real need turns out to be genuinely unknown, that’s a different tool.
Planning to facilitate this activity? Access the resources below to get started.