The question behind the question

Someone asks you for a report. You build the report. They glance at it, say thanks, and never open it again.

What they wanted was reassurance that a number was not going the wrong way. The report was their guess at how to get it.

Requests are guesses

When a person asks for something specific, they have usually already done a translation in their head: from what I am worried about to what I imagine would resolve it. That translation is where the information gets lost. They are not experts in what you can do, so their guess is constrained by what they know to ask for.

Your job, before building anything, is to run the translation backwards.

The one question

The most useful thing I have learned to say, in some form:

“Happy to do that. What will you do with it once you have it?”

It is not a challenge. It is an offer to be more useful. Nine times out of ten the answer reveals a shorter path — sometimes a two-line message instead of a week of work.

When not to do this

• When the request comes with real urgency. Ask afterwards.
• When the person has clearly already done this thinking. Repeating it is condescending.
• When the answer genuinely is “I just need the report.” Sometimes it is. Build the report.

The compounding bit

Do this consistently and something shifts. People start bringing you the problem instead of their guess at the solution, because they have learned that is where the value is. That is a far better position to work from — and it is earned one question at a time.