The ask is the end of an argument

Someone calls with the problem already solved. They want a new CRM. They want the roadmap re-cut. They want the team reorganised. The request arrives fully formed and slightly impatient, in the tone of a decision that has already been taken and now needs a supplier.

The fastest way to look useful is to agree and start building it. There is real pressure to do that, and it does not come only from the client. A firm that asks questions in week one is a firm that has not started, and somebody is usually counting.

What I have learned to notice instead is that the request is a conclusion, and I have not seen the reasoning. The ask is the last line of an argument the client has been having with themselves for months, mostly in meetings I was not in. By the time it reaches me it has been through several rounds of internal negotiation, lost its qualifications, and hardened into a sentence short enough to put in an email.

What gets dropped on the way

Arguments shed things as they travel. Somebody raised an objection in March that could not be answered, so the group moved past it. Somebody proposed a smaller version that was rejected for reasons that made sense at the time. Somebody with the clearest view of the problem was not in the room, or was, and said nothing.

None of that survives into the request. What arrives is the residue: the one option nobody could find an argument against, which is a different thing from the best one.

The discarded parts are the useful information. An option that was rejected tells you what the organisation believes about itself. An objection that went unanswered tells you where the plan will come apart, because unanswered objections do not stop being true; they wait. When a programme fails eighteen months in, the reason is very often something that was said out loud early and could not be dealt with, so the group agreed to proceed and stopped mentioning it.

Unanswered objections do not stop being true; they wait.

So the question I am actually asking is not what do you need. It is what did you consider and put down, and why. That question is harder to ask, because it implies the decision might be reopened, and by the time somebody is calling a consultant the decision is usually load-bearing. Somebody has told a board. A budget has a name on it.

"We need a new CRM" is rarely about the CRM. It is more often that the sales team does not trust the numbers, so they keep their own spreadsheets, so leadership cannot see the pipeline, so every forecast is a negotiation. A new system might help. Or the tool was never the problem, and a better one will inherit the same distrust by the second week. You cannot tell which from the request, and the request is what you are given.

What asking actually costs

The version of this you read most often has the consultant arriving with questions, the room falling quiet, and the real problem revealing itself to general relief. That is not usually what it is like.

Reopening a settled argument costs the client something. It puts back on the table a thing they had finished carrying. Sometimes there is relief, because somebody had been waiting for permission to say it. Sometimes there is irritation, and the irritation is not unreasonable: they resolved this already, at some expense, and here is an outsider unresolving it in week one.

Nor can you ask indefinitely. There is a point past which questions stop being diligence and start looking like an inability to commit, and a client is right to notice. I do not think there is a rule for where that point sits. What I do is ask until the answers stop surprising me, and then stop, which sometimes means stopping before I am comfortable.

Why it is worth it anyway

Because the alternative is building against a conclusion whose reasoning I never saw, and inheriting every objection that was quietly parked in order to get the decision made.

A request is a piece of evidence about the organisation that produced it. Read that way it is far more useful than as a statement of need. The CRM replacement tells you what people believe about the numbers. The reorganisation tells you which conversation is being avoided. The re-cut roadmap tells you what was promised, to whom, and how badly.

Take the ask literally and you get a specification. Read it as the end of an argument and you get the argument, which is where the work actually is.