What a Chief of Staff Does for a Release Team

A song can take months to become a record. Then it has to leave the room. It needs a date, artwork, credits and splits (who gets credit for what, and each person's share of the song), a pitch, and delivery to the distributor's spec.

The course's Music track argues that good records get hurt here, in the handoffs, the moments when work passes from one person or file to the next:

• The wrong bounce (exported mix) gets uploaded.
• The session bassist never makes it into the credits.
• The release date moves, but the old one survives in three posts and a pre-save link (a link fans use to save the track before release day).

The film puts it this way: a release has a take sheet too, and most artists keep it in their heads.

In this course you'll set up an AI chief of staff to help keep that sheet out of anyone's head. It reads what's happening, prepares the work and flags problems. You and the artist still decide and send. First, though, you need to know what a chief of staff actually does.

A chief of staff works for one person, called the principal, and makes that person as effective as possible. McKinsey studied the role through forums with more than 200 chiefs of staff, and its research describes six kinds of standing work:

1. Information flow. Prepares and filters what reaches the principal.
2. Air traffic control. McKinsey senior partner Andrew Goodman's phrase for managing the flow of the principal's work and actions.
3. Meeting prep and the record. Makes sure the principal walks in prepared, and keeps a record of what was agreed.
4. Peripheral vision. Acts as the principal's eyes and ears so there are no surprises. That includes bad news, which other people tend to hold back.
5. Priorities. One chief of staff in McKinsey's forum held the principal to five or six priorities. Another kept a now / soon / never list, so that things set aside were written down rather than forgotten.
6. Follow-through. Tracks what was agreed until it's done.

Notice what's missing from the list: making the principal's decisions. Every duty either prepares a decision or makes sure it gets carried out.

On a music team, the principal is usually the artist or the manager. For a small team running its own releases, the chief of staff's duties become concrete:

• The release calendar, from master delivery to release date.
• Credits and splits confirmations, chased until a signed split sheet confirms them. A split sheet is the document where contributors agree their roles and shares.
• Session and tour prep: call times, addresses, contacts, open issues.
• Manager inbox triage: bookings, sync offers (placing a song in film, TV or ads), feature requests and press.
• Distributor and pitching deadlines, which other people set and which don't move for you.
• The artist approvals log: a record of what the artist approved (mix, artwork, sync, feature), when and with what conditions.

Example: in a single's release week, the manager's inbox gets a festival offer, a blog interview request and a producer asking about the credit line. Sorting those three is information flow. Deciding to answer the producer before the credits deadline is air traffic control. Writing down that the artist approved the artwork on Tuesday is keeping the record.

The chief of staff earns its place by catching handoff damage while it's still private. Take the three failures from step one:

• The wrong bounce. The approvals log says which master the artist approved. If a new file shows up called "master_v3_final", it gets logged as a new version and flagged. It doesn't replace the approved one.
• The missing bassist. Follow-through compares session notes with the credits. Anyone named in a session but missing from the split sheet goes to the manager as an open item, with a name next to it.
• The stale date. When the release moves a week, peripheral vision means listing every place the old date still appears: draft posts, the pre-save link, the press release. Each one goes to its owner.

In every case, the chief of staff finds and routes the problem. It doesn't fix it in public. The manager changes the link and the artist confirms the credits. As the track puts it, a later file doesn't win just because it arrived later. A person decides which version stands.

McKinsey is just as clear about the limits of the role:

• It doesn't decide for the principal. Decision rights, meaning who decides what, should be agreed up front and revisited as the role changes.
• It doesn't blur whose voice it is. People answer a chief of staff because of borrowed "halo authority" from the boss. A good one makes clear when it's speaking for itself and when it's speaking for the principal.
• It doesn't isolate the principal. Guarding the artist's time is part of the job. Walling the artist off from the band, the producer or the team is not.
• It doesn't make itself the story. One chief of staff told McKinsey the job is to make the principal look good, not yourself.

In music, these limits carry extra weight. The artist's ear, consent and approval are the final word on which master is the song, whose voice is on it, and when it's ready to go. A chief of staff, human or AI, prepares that call and never makes it.

Now apply this to your own work. You'll need your email, your calendar and your release tracker or spreadsheet open.

1. Pick one week, ideally a busy week for the current release.
2. List every admin item from email, calendar and your tracker. Examples: "chase drummer for split sheet", "reply to festival booking", "confirm studio call time", "check distributor delivery deadline", "get artist sign-off on artwork".
3. Write the owner next to each item, meaning the person who has to act.
4. Sort each item under one duty: information flow, air traffic control, meeting prep and the record, peripheral vision, priorities, or follow-through.
5. Mark anything that needs a decision from the artist or manager with "DECIDE". A chief of staff, human or AI, prepares those items but doesn't decide them.

Keep the list. You'll use it in the next lesson to decide what an AI may do alone, what it must ask about, and what it must never do.

Checkpoint: every item has an owner and a duty. If an item fits no duty, it may be creative work, such as listening to a mix. Put it on a separate list, because that work stays with people.