Guides / original sample / 2 minute read / By Mira Lane, fictional editor
Start with the next decision.
A record can contain dozens of fields and still leave the next person unsure what to do. In this fictional example, a team begins by writing down the decision a brief needs to support. That question becomes the structure for the information they collect.
Ask what someone needs to know.
Imagine a handoff between an operations lead and a designer. The designer needs to know the company context, the reason for the request and the limits of the available information. A list of every event is less useful than a clear explanation of why these details belong together.
Keep the source beside the field.
When a piece of information changes, a short source note helps the next person understand where it came from. In a real workflow, source notes should distinguish verified facts, observations and assumptions. The sample record here is entirely invented and makes no claims about real companies.
Leave a useful question.
A thoughtful brief does not need to prescribe every answer. It can end with a question that makes the next step clear: what needs to be confirmed, who should review it and which decision follows? That gives the next person context and room to think.
Try it with a sample record.
Choose a fictional account, describe the next decision in one sentence and include only the details that help answer it. This article is original demonstration content, not measured research or professional advice. Replace sample content with verified material when adapting the template.
Back to the journal