Turn Any Meeting Into a Briefing Someone Can Act On
Meetings produce notes nobody reads and decisions nobody remembers
A one-hour meeting generates decisions, risks, commitments, and . By the end of the week, most of that information has scattered into individual memories. The notes, if anyone took them, sit in a shared document that nobody reopens.
A briefing is what the notes should have been. It is a short document organized around action: what was decided, what changed, what risks surfaced, and what each person committed to doing next. A briefing takes two minutes to read and tells the reader exactly what they need to do or know.
The morning brief you built in the opening chapter is one type of briefing. This chapter teaches the general : turning any meeting, project update, or status check into a briefing that someone can act on without rereading the raw material.
Three briefing types serve three different moments
Briefings are not all the same. The information you need before a meeting is different from what you need after. The structure changes to match the moment.
Prep and recap pair naturally. The prep briefing tells you what to focus on. The recap briefing records what happened. Together, they create a meeting record that is useful both before and after the event.
The briefing hierarchy puts decisions and actions first, background last
A common mistake is writing a briefing that reads like a chronological transcript: first we discussed this, then someone said that, then we moved on. That structure buries the most important information inside a timeline.
The briefing hierarchy inverts the timeline. It leads with what matters most and pushes background to the end:
- Decisions (30 seconds): what was decided, by whom, and what it means.
- Action items (30 seconds): who committed to doing what, by when.
- Risks (30 seconds): concerns that surfaced and have not been resolved.
- (optional): background that explains the decisions, for readers who were not in the room.
A reader who has 60 seconds reads the decisions and action items. A reader who has two minutes reads the full briefing. A reader who missed the meeting reads the section. The hierarchy serves all three without wasting anyone's time.
Prep briefings surface what you need to know before you walk in
The prep briefing reads your calendar event, pulls from , and assembles what you need to know: who is in the room, what was discussed last time, what action items are open, and what decisions are expected.
Notice that the prep briefing includes a risk. 'Maria has not seen the revised timeline yet' is information the assistant found by checking when Maria last attended and what changed since then. This kind of contextual flag is what makes a prep briefing more useful than reading the agenda alone.
Recap briefings capture what happened before you forget
After the meeting, you have about thirty minutes before the details start fading. The recap briefing should be generated during that window.
If you took notes (even rough ones), paste them. If the meeting was recorded and transcribed, paste the transcript. If you remember the key points, tell the assistant what happened. The briefing template structures whatever input you provide into the standard hierarchy: decisions, action items, risks, .