Start with the result

A request often arrives as a collection of activities: redesign the page, prepare the deck, refresh the campaign. Before deciding what to make, describe the result the work needs to support. Who is it for? What is difficult for them today? What would a useful change look like? A short answer gives the next conversation a clearer purpose.

Make constraints visible

Record the practical limits beside the ambition. Existing commitments, available time, required approvals and dependencies all affect what can happen next. These details should help a team choose a realistic first step, rather than becoming a long document that nobody revisits. Separate an established constraint from an assumption that still needs to be checked.

Choose the next useful action

Finish the intake with one owner and one specific action. Sometimes that action is a small piece of research rather than a production task. Say what needs to be learned, where the answer will be recorded and when the brief will be reviewed.

Turn an activity into a useful question

Consider a request to redesign a sign-up page. The first useful question might be whether readers understand what happens after they submit the form. That is different from assuming the page needs more visual detail. A small review of the current explanation could answer the question before the team commits to a larger redesign. Record what the review is intended to establish, so its result can change the next step.

Give a constraint a source

A deadline is more useful when the team knows what creates it. An event date may be fixed, while the amount of material expected for that event could still be discussed. Name the source of the commitment and the part that remains flexible. This helps the next owner propose an achievable first version instead of treating every detail of the initial request as equally settled.

Return to the brief when the situation changes

If an important assumption changes, update the brief before treating the old scope as current. A different audience or an approval requirement may alter what a useful result looks like. Keep a short note of the change and the decision it affects. The brief should remain a shared starting point, rather than a document that becomes accurate only when somebody remembers to explain it.