Muse for Meetings, End to End: Pre-Meeting Briefs, Clean Notes, and Follow-Ups That Land
A meetings setup for Muse: a short brief before every meeting, clean notes that separate decisions from open questions, and a weekly sweep that keeps action items from going quiet, with Muse drafting and you sending.
By Professor Muse11 min read
The call ending does not finish a meeting. A meeting is finished when everyone who was there can say what was decided, who is doing what by when, and what is still open. Most meetings fail that test because the record after it was a transcript nobody reads, or nothing at all. The discussion was rarely the problem. By Friday the team books another call to reconstruct the outcome of the first one.
This lesson sets up the whole loop, before, during, and after. Muse reads the calendar invite and the background material and writes a short brief before the meeting, turns raw notes into a clean record after it, and sweeps the open action items once a week so nothing goes quiet. You make the decisions in the room and send every follow-up; Muse drafts, sorts, and chases. It never assigns work to someone who did not agree to it, and it never turns an open question into a decision.
Research supports the value of that short shared record. In a peer-reviewed study based on 3,290 survey responses, Cutler and colleagues found that sending a post-meeting summary was among the factors correlated with perceived meeting effectiveness and inclusiveness. It was an observational study in one large technology company, so it does not prove that any summary will improve a meeting, and it does not prove that a longer summary is better. A separate study by Kauffeld and Lehmann-Willenbrock, looking at 92 regular team meetings, found that problem-solving interaction and action planning were associated with meeting satisfaction and productivity. Both point the same way: the meeting earns its keep when the record after it is clear about what was decided and who owns what.
The short version
- Run three jobs around every meeting: a brief before it, a clean record after it, and a weekly sweep of open action items.
- Every action item needs one owner, a due date or review condition, and a stated outcome. An item missing any of those is not an action yet.
- Muse drafts every follow-up and you send it. Muse never assigns an owner from a guess, and it never writes a decision the room did not make.
- The failure mode to watch for is an invented owner or a decision that was only an option. The fix is a rule that leaves unclear items marked unclear.
The Setup: The Thursday Ops Review
Call the whole arrangement the Thursday Ops Review. It is a weekly 45-minute cross-functional meeting I run every Thursday at 10am, with product, support, and operations in the room, and it covers three standing topics: what shipped, what is stuck, and what needs a decision this week. The same three jobs apply to any recurring meeting you run, but naming one real meeting keeps the prompts below concrete.
Before the meeting, Muse writes a one-page brief from the calendar invite, last week’s record, and the documents linked in the invite. During the meeting, I take rough notes in a shared doc, names and half-sentences, nothing polished. After the meeting, Muse turns those notes into the record: decisions, action items, and open questions, each in its own list. Once a week, on Monday morning, Muse sweeps every open action item from the last four weeks and returns a chase list: what is done, what is overdue, and what has no owner.
The standing instructions from our memory guide keep the shape consistent: every action item gets one owner, one due date or review condition, and one stated outcome; anything unclear stays marked unclear; nothing gets sent without me reading it first. Store those rules once, and every brief and record comes back in the same shape. The Monday sweep runs as a scheduled routine, the same shape as a Friday expense review, with one extra rule: if there are no notes for a meeting, Muse says so and waits, instead of reconstructing the meeting from the calendar invite alone.
The Thursday Ops Review uses the same discipline as the executive version of the job:
Prompt 1: The Pre-Meeting Brief
Run this the evening before, or the morning of, from the calendar invite and the linked material. A brief written from memory is a guess about what the meeting is for. A brief written from the invite and last week’s record is a page you can walk in with.
Write a one-page brief for the meeting below. Use only the invite, the linked documents, and last week’s record. Return: (1) the purpose of the meeting in one sentence, (2) the decisions that need to be made, with who owns each decision, (3) background from last week’s record that is still open, and (4) any material I should have read, with the one fact from each document that matters for the decision. If a decision has no owner in the invite or the record, say so. Do not invent an owner, a decision, or a deadline.
Meeting: [paste the calendar invite, with time, attendees, and agenda]. Last week’s record: [paste last week’s decisions and open items]. Documents: [paste or link the material attached to the invite].
Read the brief the way you would read a map before driving: check the decisions list first. If the brief lists three decisions and you know only one of them is real, fix the list before the meeting. A brief with a wrong decision on it is worse than no brief, because the room spends twenty minutes on a question nobody needed to answer.
If the meeting has no agenda in the invite, the brief will say so. A meeting with no stated purpose and no decision to make is a candidate for an async update instead of a call. The brief makes that visible before you spend the hour.
Prompt 2: Turn Raw Notes Into the Record
Run this within the hour after the meeting, from the rough notes you took. Treat the notes as source material; the record is the conclusion, and it has three lists and nothing else.
Turn the notes below into the meeting record. Return three lists: (1) Decisions, written as complete statements with their scope and any condition, (2) Action items, each with one owner, a due date or review condition, and the expected outcome, and (3) Open questions, each with who will find the answer and by when. Rules: only include an action item if the notes name an owner; if the notes do not name one, put the item under Open questions as unowned. Do not turn a discussion point into a decision. Do not turn a suggestion into an action. If the notes are ambiguous about a decision, mark it as unclear and quote the relevant line. End with a one-paragraph follow-up draft addressed to the attendees, using the same three lists.
Notes: [paste your rough notes, or a transcript if the meeting was recorded].
The follow-up draft is a draft, so read it, correct the record, and send it yourself. Our failure modes guide explains why that reading step stays mandatory: a fluent record still needs verification, and a decision that reads cleanly but was never made will be quoted back to you next week as if it were agreed.
| Job | When | What it answers |
|---|---|---|
| Pre-meeting brief | Evening before, or morning of | What is this meeting for, and what decisions need an owner |
| Notes to record | Within the hour after the meeting | What was decided, who owns what by when, and what is still open |
| Action-item sweep | Monday morning, weekly | Which items are done, overdue, or unowned across the last four weeks |
Prompt 3: The Monday Action-Item Sweep
Run this once a week, from the records of the last four weeks. The sweep is where the meeting loop either holds or quietly fails. An action item that nobody checks is a promise the team made to itself and then forgot, and the next meeting becomes a rerun of the last one.
Sweep the action items in the meeting records below, covering the last four weeks. Return: (1) items completed since the last sweep, (2) items overdue, with the owner and the original due date, (3) items due this week, with the owner and the date, and (4) items with no owner, no date, or no stated outcome, listed as unowned or unclear. Do not close an item unless the record says it is done. Do not reassign an item to a different owner. Do not add new items. End with a short chase list: one line per overdue or unowned item, naming the owner or the missing piece.
Records: [paste the last four weeks of meeting records, or the action-item lists from each].
Work the chase list the way you would work a queue: one message per overdue item, to its owner, asking for a status or a new date. Do not send the whole sweep to the whole team. A sweep sent to everyone is a broadcast, and broadcasts get read by nobody. A one-line message to one owner gets an answer.
If the sweep keeps returning the same unowned items week after week, that is a signal about the meeting, not about Muse. An item that nobody will own after three weeks is either not real work or work that belongs to a decision nobody has made. Take it back to the meeting and either give it an owner or delete it. A record with five honest open questions is more useful than a record with fifteen action items, ten of which nobody owns.
What Can Go Wrong: The Invented Owner
Here is the failure mode you will meet first. The record comes back clean, well organized, with every action item assigned to a name and a date. A week later you ask someone about their item and they tell you they never agreed to it. The cause is one line in the notes: “we should look into the onboarding delay.” Muse read a suggestion as a commitment, attached the name of the person who raised it, and gave it a deadline from the general discussion. The record looked finished, so it got less checking than rough notes would have, and a person got assigned work in a document they never saw.
The fix has two parts. First, hold Prompt 2 to its own rule: an item without a named owner goes under Open questions as unowned, and stays there until a human assigns it. Second, add one standing rule to the setup: before you send any follow-up, read the action list out loud against the notes, owner by owner. If you cannot point to the line where that person agreed, the item is not an action yet, and it goes back to Open questions. A record that survives that reading is a record the team can trust. A record that does not survive it is a draft, and it goes back for correction before anyone is chased for work they never took on.
The same discipline applies to decisions. A decision written as a complete statement, with its scope and its condition, can be quoted next week. A decision written as “discussed the launch date” cannot, because it records a topic, not a choice. If the notes do not support a complete statement, mark it unclear and quote the line, and let the next meeting settle it.
Start With One Meeting
Do not build the whole Thursday Ops Review this week. Pick your next recurring meeting and run Prompt 1 on it the evening before, from the invite and the last record you have. Walk in with the brief, take rough notes, then run Prompt 2 within the hour, read the record against your notes owner by owner, and send the follow-up yourself. Next Monday, run Prompt 3 on the records you have so far, even if that is only one meeting, and chase one overdue item.
Run it that way and Muse does what it is good at around meetings: the reading, the sorting, the short brief, the clean record, the weekly sweep. You keep what was always yours: what the meeting is for, who agreed to what, and what gets sent. That gives you meetings that end with a record people can trust, action items with a name and a date on each one, and a Monday sweep that catches the quiet failures before they become a rerun of last week’s meeting. The discipline that holds it together is the owner rule, checked every time.
The meeting research cited here is summarized in Flowtrace's guide to meeting follow-up best practices: Cutler and colleagues' peer-reviewed study of 3,290 survey responses, in which sending a post-meeting summary was among the factors correlated with perceived meeting effectiveness and inclusiveness, and Kauffeld and Lehmann-Willenbrock's study of 92 regular team meetings, in which problem-solving interaction and action planning were associated with meeting satisfaction and productivity. Both are observational findings, not proof that any particular summary improves a meeting.
