Refuse the First Brief

The first brief is almost never the decision. It is a topic, a metric, and a deadline, assembled by someone who 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 four questions

You need four answers before you spend serious time. If you cannot get them in a fifteen-minute conversation, that itself is information: either the choice is still unspecified, or nobody who can specify it will talk to you. In both cases, opening the warehouse is a stall.

1. Who will use this to change an action? Not who is interested. Who can commit, or who will run a rule. Interest is cheap and authority is not.

2. What are they choosing among, including the status quo? If they cannot name two commitments of the same kind, you are not yet on a decision.

3. When does the choice go stale? The meeting time is usually the wrong date. The freeze, the contract window, the promotion start, the quarter-end cash event: those go stale.

4. What would have to be true for them to pick differently? This is the question that tells you what evidence is worth gathering, and the one most likely to reveal that the decision was already made before you were asked.

When not to analyze

Some requests should be declined outright rather than reframed.

When the decision has already been made and the analysis is wanted as cover, the honest move is to say that you will document the rationale rather than produce a study that pretends to be an inquiry.

When the choice cannot be made by anyone in the conversation, the deliverable is a short note identifying who can make it, not six weeks of work addressed to nobody.

When the request is for a demonstration rather than a decision, say so. “Build an agent” is the current form of this, and 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.

Refusing without becoming the problem

The concern is real: the person who keeps saying “that is not well-specified” becomes the person nobody invites.

The technique that works is to refuse by supplying, never by withholding. Do not return the brief with objections. Return it with your best attempt at the choice sentence, filled in with your guesses, and ask them to correct it.

This inverts the social dynamic entirely. You are not blocking; you are proposing, and they are now editing a concrete sentence rather than defending a vague one. Most of the time they will 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 having in about week five.