What a Chief of Staff Does, and What It Doesn't

A chief of staff is the person who makes a leader as effective as possible. In the business world that leader is called the principal. For you, the principal is you, the creator.

McKinsey has run forums with more than 200 chiefs of staff over five years, and in a 2024 podcast senior partner Andrew Goodman described what the job involves. Depending on the organization and the relationship, it can be mostly admin or mostly strategy. The standing work, meaning the work that repeats every week, looks like this:

• Information flow: filtering what reaches the principal.
• Air traffic control: Goodman's own phrase for managing the flow of work and activities.
• Meeting prep and the record: making sure the principal walks in prepared, and writing down what was agreed.
• Peripheral vision: being the principal's eyes and ears so nothing comes as a surprise.
• Calendar against the cycle: planning time around the business's big recurring moments.
• Priorities: one chief of staff in McKinsey's forum kept the principal to five or six.
• Follow-through: tracking what was promised until it's done.

Before you open any AI tool, this course starts with the job itself. An AI chief of staff is only useful when you know which job you're handing it.

You probably already do every one of these duties, just at night and in between filming. Here's how they line up with a typical creator's admin:

• Information flow is your business inbox: paid offers, PR and gifting, collab requests, press, fan mail and scams, all mixed together.
• Air traffic control is your content calendar: what's being filmed, edited and posted, and when.
• Meeting prep and the record cover brand calls. You go in knowing the deal history and come out with notes on who agreed to what.
• Peripheral vision means spotting the brand approval that went quiet a week before a go-live date.
• Calendar against the cycle means planning around launch dates, seasonal campaigns and sponsor reporting windows.
• Follow-through is your deal tracker: deliverables, disclosure checks and sponsor reports, plus hand-offs to your editor or manager.

Take a hiking creator with a boots sponsor, a part-time editor and a manager who handles brand questions. Their week includes a brand call, three deliverables, a report due on the 30th and an edit coming back from the editor. Every one of those maps to a duty. If you run a one-person channel, every role is yours, so later lessons have you write them down.

The limits of the role matter as much as the duties. McKinsey's guidance says a good chief of staff:

• Doesn't decide for the principal. Scope and decision rights get agreed up front and revisited as the job changes.
• Doesn't blur whose voice it is. It's always clear whether it's speaking for itself or for the boss.
• Doesn't isolate the principal. Guarding your time is part of the job, but you shouldn't end up cut off from the people who matter.
• Doesn't play politics or make itself the story. One chief of staff put it this way: the job is to make the principal look good, not yourself.

In a creator business, these limits look like this. The assistant can lay out three brand offers side by side, but you pick one. It can write a reply, but the reply stays a draft until you send it. It can filter fan mail, but it shouldn't quietly bury messages you'd want to see.

The McKinsey list also includes a never column, for things that came up but won't be done. They're written down so they aren't forgotten. You'll build your own never list in the next lesson.

McKinsey points out that people answer a chief of staff's calls because of a borrowed halo authority. The chief of staff carries the boss's weight, which is exactly why it has to be careful about when it's speaking for the boss.

For a creator, the halo is complete. A brand manager or a fan reading an email from your business account doesn't think "their assistant wrote this." They think you said it. Suppose a reply goes out saying "Happy to deliver two Reels by the 14th." The brand now believes you've committed to a date and a deliverable. Or suppose a fan gets a friendly reply that sounds slightly off. That fan has now heard a voice that isn't quite yours, under your name.

That's why this course draws the boundary where it does. An AI chief of staff can prepare a reply, but sending it is speaking for you. Agreeing to a date, price or deliverable is speaking for you. So is accepting a meeting invite, because the brand gets a notice from your calendar.

Every lesson in this course runs on one rule: the agent prepares; the creator decides and sends. Here, an agent is an AI assistant that works on a standing job rather than answering a single question.

Here's how one brand email moves through that rule:

1. A brand emails your business inbox with an offer.
2. The agent sorts it as a paid offer and pulls out the brand, deliverables, dates and fee, with a note of which email each fact came from.
3. The agent drafts a reply asking for the brief, budget, usage rights and timeline. Wherever the reply would commit you to a date or price, it leaves a placeholder.
4. You read it, decide whether you're interested, and edit it.
5. You send it yourself.

Current tools are built to hold this line. OpenAI says asking a dot (its always-on agent) for a draft does not authorize it to send that draft. Anthropic says Claude Duet asks before it sends a message, makes a payment, signs a document or deletes anything. Later lessons show you how to set these approvals on whichever tool you choose.

Now practice the skill you'll use every day: telling preparation apart from speaking for you.

Ask two questions about any action:

1. Will someone outside see it or receive it? That includes a brand, a fan, your editor, or a calendar invite going to attendees.
2. Does it commit you to something? That could be a date, a fee, a deliverable, a meeting, an opinion or a decision.

If the answer to either is yes, the action is speaking for you, and it waits for your explicit approval on the exact text. If both answers are no, it's preparation, and the agent can do it on its own: reading, sorting, summarizing, drafting, and listing what's due.

One thing that looks harmless isn't. If an agent writes a decision into your records as confirmed, it has made the call for you. The safe version records it as proposed, and only you mark it confirmed. You'll set that up in the decision log lesson.

Try the situations on the right. Match each one to the right move.

The line for this whole track is stay the author. Hand over the legwork, and keep three things:

• The facts. If a last shuttle leaves at 5:30, you're the one who checked it, and you're the one who corrects it if the timetable changes.
• The word. Your voice, your commitments to sponsors, and your replies to brands and fans.
• The last look. Nothing goes out without your approval.

Instagram's Adam Mosseri said creators keep their taste, judgment and commentary even as the tools change. Adobe's 2026 creator survey points the same way, though Adobe sells creative AI, so treat it as a vendor survey.

Try it now. Paste this into the assistant you already use, then fill in your own week:

Here is my creator admin from last week: [list emails, calls,
calendar changes, deliverables, reports, hand-offs to my editor or
manager]. Sort each item under one of these chief-of-staff duties:
information flow, air traffic control, meeting prep and the record,
peripheral vision, calendar against the cycle, priorities,
follow-through. Then mark each item PREPARE (an assistant could get
it ready) or SPEAK (it goes out under my name or commits me).
Do not draft or send anything.

Checkpoint: every item has a duty and a mark. If an item seems to fit two duties, choose the one closest to the outcome you care about. Keep this list, because you'll sort it in the next lesson.