Back to the journalTHINKING / ORIGINAL ARTICLE

A better brief starts
with a better question.

Give the next conversation a clearer place to begin.

Illustrative editorial still life of project notes arranged into a clear stack

A project often starts with an energetic conversation. Someone has spotted a problem, another person has an idea, and the team can already see several ways forward. Then the notes grow. A message becomes a thread. A thread becomes a task. The original question becomes harder to find.

The purpose of a brief is to preserve the useful thinking while giving the next person a manageable starting point. That means making choices about what belongs in the brief, what should stay attached as a source and what still needs to be decided.

Start with the question.

Before listing requirements, write down the decision the team needs to make. A question creates a useful boundary around the conversation. “How should we redesign onboarding?” is broad. “What does a new team need to understand before inviting its first colleague?” gives you something more specific to explore.

The question does not have to be perfect. It should be clear enough that another person can explain why the work matters. If the team disagrees about the question, that is valuable information. Resolve that disagreement before turning the notes into a long list of tasks.

A good brief helps someone understand what needs a decision, not just what needs doing.

Keep the evidence in reach.

A concise summary can make a busy conversation easier to read. It can also remove the detail that explains why an idea appeared in the first place. Keep the source material close enough for someone to check the interpretation.

That might mean linking to an interview note, a product screenshot or a short description of the problem. Label each source clearly. A reader should be able to tell whether a statement comes from observation, a team preference or a hypothesis that still needs testing.

  • Summarise the useful pattern rather than every sentence.
  • Keep links to the original context alongside the summary.
  • Use plain language that someone outside the meeting can follow.
  • Leave uncertain details visible instead of making the summary sound more confident.

Give assumptions a name.

Teams make assumptions because they need to move. The problem is not that assumptions exist; it is that they can start to look like agreed facts. A short, explicit assumptions section makes the difference visible.

For example, an onboarding brief might assume that the person creating a workspace can invite colleagues. That could be true for a small team and false for a larger organisation. Writing the assumption down makes it possible to ask the right question before building the wrong interaction.

Do not turn every unknown into an urgent research project. Ask which uncertainty could change the direction of the work. Give that question an owner and a clear way to review what you learn.

End with one agreed next step.

A useful brief should leave the reader with a clear sense of what happens next. Name an action, an owner and a review point. Keep the original question nearby so the next task does not lose its purpose.

The next step might be a small prototype, a review with the support team or a decision about scope. It does not need to solve the entire problem. It needs to reduce the most important uncertainty and create a useful place for the conversation to continue.

When the work changes, update the brief. A brief is a working agreement, not a document that becomes correct simply because someone has written it. Its value comes from keeping the team’s thinking legible as the project moves.

Explore the workflow