Muse for Executives and Chiefs of Staff: The Morning Brief, Decision Memos, and Follow-Up That Doesn't Slip
An executive's working setup for Muse: a morning brief across calendar, inbox, and messages, decision memos that separate what was decided from what was only…
By Professor Muse9 min read
An executive’s day starts with a pile, not a blank page: overnight email, a calendar that shifted while you slept, messages from three different places, and the decisions from yesterday that nobody wrote down. A chief of staff earns their keep by turning that pile into a short brief before the first meeting, and by making sure nothing agreed in a meeting quietly evaporates by Friday.
That is the job Muse can take over in an executive seat, provided the setup respects one boundary. Muse reads, gathers, and drafts, and stops there: decisions, sends, and commitments stay with you. Meta’s rule for Muse is that nothing publishes, sends, or spends without your approval, and that rule is what makes this setup safe to run on a calendar and inbox that carry real commitments. The executive keeps the decisions. Muse keeps the pile sorted.
The shape of the job is already visible in how business owners use Muse. When Meta expanded Muse to small businesses on September 29, 2026, one owner described the daily pattern: an inbox triage with bills flagged and priority email surfaced, plus a day briefing covering calendar, bookings, and reminders, read from her phone, with actions taken only after she tapped approve. An executive setup is the same pattern, scaled up to a leadership calendar: more sources, more meetings, and a written record of what was decided.
The short version
- Connect calendar, inbox, and messages first, read-only, and keep approval required for every send, booking, and share until the briefs have earned your trust.
- Run three jobs: a morning brief before the first meeting, a decision memo after any meeting that ends with commitments, and a Friday follow-up sweep of everything still open.
- Every commitment in a memo needs a source: who said it, where, and in what words. A commitment without a source is a guess wearing a suit.
- Nothing sends without your approval. That is Meta’s rule for Muse, and it is what keeps a delegated inbox from becoming a delegated voice.
The Setup: The Executive Desk
Call the whole arrangement the Executive Desk. I run it for a chief of staff supporting one executive, where the week runs on a fixed rhythm. Each weekday starts with the morning brief. Any meeting that ends with a decision gets a memo the same day. Friday afternoon is the follow-up sweep. Each job is a scheduled routine, and each one lands as a document to read, not as a message sent on your behalf.
The Executive Desk has three jobs, and each one maps to a prompt below.
The morning brief. Muse reads overnight email, messages, and today’s calendar, and writes a brief short enough to read in five minutes: what is on today, what changed overnight, what needs a decision before noon, and what can wait. A brief that takes twenty minutes to read has failed at its only job.
The decision memo. After a meeting, Muse turns the notes or transcript into a one-page memo with three sections: what was decided, what was discussed but not decided, and who owes what by when. That middle section is the whole point. Most follow-up failures come from discussions everyone left believing were decisions.
The follow-up sweep. On Friday, Muse goes back through the week’s memos and open threads and lists every commitment that is still unclosed, with its owner and its due date. The executive reads it, chases two or three items personally, and lets the rest ride to Monday with eyes open.
| Job | Muse does | You do |
|---|---|---|
| Morning brief | Reads overnight email, messages, and today’s calendar; flags what changed and what needs a decision | Reads it before the first meeting, corrects any misread priority |
| Decision memo | Turns notes into decided, discussed, and owed sections with sources | Confirms the decisions, fixes anything overstated, approves any message that goes out |
| Follow-up sweep | Lists unclosed commitments from the week’s memos and threads | Chases the items only you can chase, closes or re-dates the rest |
Before any of this runs, do the permissions pass from our Sentinel permissions guide: approval required for every send, booking, and share, and read-only access everywhere else until the briefs have earned your trust. The same draft-then-human-send rule our founders lesson uses for investor updates applies here to every board note, investor message, and external email. And the privacy rules apply with extra force at this level: board material, compensation details, and anything under NDA stays out of prompts unless you have decided that a given source is in scope.
Our guide to putting Muse on a schedule covers the routine mechanics this desk sits on:
Prompt 1: The Morning Brief
Run this every weekday at least thirty minutes before the first meeting, so there is time to read it and correct it.
Write my morning brief for today, in under 400 words. 1. Today’s calendar in order, with the prep each meeting needs and any travel or back-to-back conflict. 2. Anything that changed overnight: a moved or cancelled meeting, a message that needs me before noon, a thread that escalated. 3. The three messages that most need my attention, each with one line on why it matters and a link or quote to its source. 4. One section called “Needs a decision today” and one called “Can wait.” Do not send, book, or reply to anything. Draft only. I approve and send.
A brief without the “Can wait” section will quietly train you to treat everything as urgent. The section gives you permission to ignore the rest until tomorrow.
Prompt 2: The Decision Memo
Run this after any meeting that ends with commitments, from the notes or transcript, the same day. A memo written on Friday about a Tuesday meeting arrives too late to serve as a record.
Turn these meeting notes into a one-page decision memo with exactly three sections. “Decided”: only items where someone clearly committed to a course of action, each with the name of who decided it and a short quote or source reference. “Discussed, not decided”: topics raised without a commitment, stated plainly as open. “Owed”: each commitment with its owner and due date. If a commitment has no owner or no date, mark it “owner unclear” or “date unclear” instead of filling in a guess. Do not send this memo to anyone. Draft only. I review and send.
That instruction prevents a specific error. Left to itself, an agent will tidy a memo by assigning the most likely owner to an unassigned task, and by Monday that person is being chased for something they never agreed to. An honest gap in a memo is a question for the next meeting. A filled-in guess is a misunderstanding with a name on it.
Prompt 3: The Friday Follow-Up Sweep
Run this every Friday afternoon, against the week’s memos and open threads.
Sweep this week’s decision memos and open email threads. List every commitment that is still unclosed, grouped by owner, each with its due date and a link or quote to its source. Flag anything overdue, anything due next week, and anything whose owner or date was marked unclear. Keep it under 300 words. Do not chase anyone, send reminders, or close any item. Draft only. I decide what gets chased.
A sweep that chases people on your behalf has crossed the line this whole setup is built to hold. The sweep informs; you chase, because a reminder from an executive lands differently from a reminder sent by a system, and the executive should choose which items deserve that weight.
What Can Go Wrong: The Discussion That Became a Decision
Here is the failure mode you will meet first. The decision memo comes back clean and confident: the Tuesday leadership meeting decided to move the product launch to November, with the engineering lead owning the revised timeline. The memo reads well, the sections are tidy, and the launch date is now in writing. The problem is that nobody decided that. In the meeting, someone proposed November, two people nodded at the idea, and the group agreed to discuss it with engineering first. The memo turned a proposal with nods into a decision with an owner.
If that memo had gone out, the engineering lead would have received a commitment they never made, the November date would have started circulating as settled, and the correction would have cost more credibility than the memo ever saved. Approval fatigue lets it through: on a busy afternoon, a memo that reads well gets approved on the strength of its prose, and the one overstated decision rides along with it.
The fix has two parts. First, Prompt 2 already requires a quote or source reference for every item in the “Decided” section, and you hold it to that: a decision without a quote gets moved to “Discussed, not decided” until someone confirms it. Second, before you send any memo, read the “Decided” section the way a skeptical editor would and ask of each item: did someone actually commit, or did the room merely agree the idea sounded good? That check takes two minutes. It is the executive’s version of the rule in our inbox triage lesson: Muse surfaces and drafts, and the human owns the judgment call, every time.
Start With One Job
Do not build the whole Executive Desk this week. Connect the calendar and the inbox read-only, run Prompt 1 tomorrow morning, and read the brief against your actual day: did it flag the right three messages, did it put the right items in “Can wait,” did it invent urgency anywhere? If the brief survives that reading for a week, add the decision memo after your next real meeting, then the Friday sweep.
Muse does what it is good at in an executive seat when you run it that way: the gathering, the first draft, the watching of open threads. You keep what was always yours: the decisions, the voice, the send button. That gives you mornings that start with a brief instead of a pile, meetings that end with a record instead of a feeling, and Fridays where the open items are a list you chose, not a set of surprises waiting for Monday.
