Article
How to Refuse a Brief Without Becoming the Obstacle
The first request is almost never the decision. Absorbing it anyway is the most expensive habit in technical work, and the standard objection to pushing back has a specific, practical answer.
The brief arrives as a topic, a metric, and a deadline. “Inventory and service, we need to understand what is happening, can you have something for the S&OP meeting on the eighteenth.”
The person who sent it is genuinely busy and reasonably expects you to work out the rest. Absorbing it is the path of least resistance, and it is the single most expensive habit in technical work, because everything downstream inherits the ambiguity.
The problem is that the obvious alternative, pushing back, has a real social cost. The person who keeps saying “that is not well-specified” becomes the person nobody invites. That concern is legitimate and it deserves a better answer than “be more assertive.”
Refuse by supplying, never by withholding
The technique that works is to not return the brief with objections. Return it with your best attempt at the choice sentence, filled in with your own guesses, and ask them to correct it.
By the April freeze, Priya will choose among keeping the current replenishment rule, a blanket inventory cut, or class-based stocking, in order to reduce working capital without stranding repair jobs. Is that the decision? I have guessed at the alternatives and the date.
This inverts the social dynamic completely. You are not blocking; you are proposing. They are now editing a concrete sentence rather than defending a vague one, which is a far easier thing for a busy person to do. Most of the time they correct two clauses and approve the rest, and the whole exchange costs ten minutes.
It also produces a written artifact of what was agreed, which is worth a great deal in about week five when the scope has drifted and nobody remembers what was asked.
The four answers you need first
Before spending serious time, four things. If you cannot get them in a fifteen-minute conversation, that itself is information: either the choice is unspecified, or nobody who can specify it will talk to you. In both cases, opening the warehouse is a stall.
The first is who will use this to change an action. Not who is interested. Interest is cheap and authority is not, and “the S&OP meeting” is an audience rather than an owner.
The second is what they are choosing among, including the status quo. If nobody can name two commitments of the same kind, you are not yet on a decision.
The third is when the choice goes stale, which is almost never the meeting. The freeze, the contract window, the promotion start, the quarter-end cash event: those go stale. Optimizing toward the meeting finishes the work at exactly the wrong moment.
The fourth is what would have to be true for them to pick differently. This is the question that tells you what evidence is worth gathering, and it is the one most likely to reveal that the decision was already made before you were asked.
When the answer is that you should not analyze at all
Three cases where reframing is not enough.
When the decision has already been made and the analysis is wanted as cover, say that you will document the rationale rather than produce a study that pretends to be an inquiry. This is not insubordination; it is accurate labeling, and it protects you when the study is later cited as independent.
When nobody in the conversation can make the choice, the deliverable is a short note naming who can. That is a genuinely useful output and it takes an afternoon.
When the request is for a demonstration rather than a decision, say so. “Build an agent” is the current form of this. The interesting questions are whose work changes, what the system may do without a human, and what a failure costs. Until those are named, a demonstration is a demo. Demos can be useful. They should not consume a freeze date.
What this buys, concretely
The immediate benefit is that a large fraction of the requested work turns out to be optional, because it could not change the ranking of the alternatives.
The larger benefit is reputational and it accrues slowly. A person who reliably returns a sharper version of the question becomes the person requests get routed to early, while there is still time to shape them. That is a considerably better position than being the person who reliably delivers thorough decks, and it is available to anyone willing to spend fifteen minutes before spending six weeks.
Method applied in this article
- Refuse the First BriefThe practice of returning an underspecified request rather than absorbing it into analysis.
- Name the ChoiceA single sentence naming who will choose among which alternatives, by when, and to what end.
- Problem, Decision, OutcomeThe separation of what is wrong, what we are choosing among, and what we want to be true afterward.
What Would Change the Ranking
One note every other Tuesday.
One piece of the method, one worked example from real operations, and one thing to try before you open a notebook. No news, no roundups, no launch announcements.
Read next
- Forty-Seven Slides and the Rule Did Not ChangeThe most common outcome of competent technical work is a meeting that agrees the work was thorough and an operating process that continues exactly as before. The cause is not effort, and more effort will not fix it.
- Your Model Is Not the AnswerModel quality is an intermediate artifact, and presenting it as the deliverable is the central structural error in applied data science. The remedy is not clearer communication. It is a different definition of finished.