Write for the next person

A useful project brief explains the situation, the intended outcome and the boundaries of the work. It should help someone new understand what matters without having to reconstruct the conversation from scattered messages.

Leave room for questions

Separate facts from assumptions. Mark what has already been agreed and what still needs a decision. Where a detail is missing, name the question and the person who can help resolve it. This gives the next discussion a more useful starting point.

A brief is useful when the next person can distinguish the agreement from the questions still open.

Name the reader and the moment

“For our customers” may be too broad to guide a piece of work. A more useful description could name somebody comparing two plans for the first time, or a teammate receiving an approved draft. Explain what that person knows already and what they need to do next. This gives a writer or designer a concrete situation to respond to, without pretending that a short brief replaces further research.

Make the boundary easy to discuss

A brief should show what is outside the current agreement as well as what is inside it. Preparing a launch page might include the copy and an approved layout, while a new illustration remains a separate decision. A clear boundary does not make a request for extra work unwelcome. It makes the effect of that request visible, so the team can discuss timing, ownership and scope before treating it as included.

Use an example to test understanding

A small example can reveal whether two people interpret a sentence in the same way. Ask the next owner to describe the first useful output or the question they would answer before beginning. If their interpretation differs, update the brief rather than relying on a private clarification. The aim is a shared starting point that can survive a handoff, not a perfectly worded document that only its author understands.