Start with the question
An internal discussion becomes much more useful when everyone knows what it is meant to resolve. “Should we explore Bitcoin treasury?” is a different meeting from “Who will review our proposed operating process?” A short brief makes that difference explicit.
Begin with one paragraph explaining why the topic is on the agenda. Describe the organisational question in your own words. Leave room for disagreement: the purpose of the brief is to make the discussion clearer, not to predetermine its conclusion.
Identify who needs to contribute
List the people whose work would be affected by the proposal. That might include leadership, finance, operations, technology, and external advisers. Give each participant a specific question to consider before the meeting.
Someone responsible for daily operations may see a handover issue that is absent from a high-level proposal. A finance colleague may need a clearer description of the records the process would produce. Bringing these perspectives together early helps define the actual work.
Separate what you know from what you need to learn
A helpful brief has two short lists: existing information and open questions. Put current processes, internal constraints, and named owners in the first list. Put uncertainties and requests for specialist input in the second.
Avoid treating an assumption as an agreed fact. If a point needs review, assign someone to follow it up and record the outcome. This turns uncertainty into a visible piece of work.
Define the next decision
End the brief with the decision the meeting should enable. It could be agreeing an education session, appointing a working group, or commissioning a more detailed review. Keep that step proportionate to the information available.
After the meeting, update the brief with the decision, its owner, and the questions that remain. The document then becomes a useful starting point for the next conversation.
