Most marketing weeks are designed in the meeting that reviews them. That is too late. The weekly is where a practice either holds the work or performs the appearance of holding it. You can tell which in the first twelve minutes.
A readout meeting is a costume. Slides of what shipped. Vanity numbers. A tour of the dashboard. Nobody kills anything. Nobody reschedules. The people who already did the work listen to a description of the work. Then they return to the queue.
An operating meeting is shorter and ruder. What is locked this week. What is slipping. What will not ship, and who had the authority to say so. Where paid is covering a hole. Where email will collide with a product launch. Where legal is still sitting on a proof that should have been a template months ago.
The inputs are not a deck. They are a calendar, a kill list, a claims list, and a single page of numbers the VP already believes. Placement. Time-to-launch. Unsub. Assisted revenue. Cycle time. Duplicate sends. If a metric needs a TED talk, it does not belong in the weekly.
Who is in the room matters more than the agenda template. The people who can change the week: channel owners, a legal path that is a person not a portal, product if product is allowed to mint journeys. Agencies, if present, do not own the agenda. They enter the calendar. That is the entire relationship, written down.
Three agencies and no calendar is a common American enterprise picture. Brand, digital, a regional shop. Each with a status call. None with the week. The internal team becomes a routing layer. The weekly, if it exists, is a peace conference. Peace conferences do not ship.
A practice sitting inside the function changes the meeting because the principal is in the work. There is no account manager translating. The person who wrote the send plan is the person who can kill a send. That is the whole difference between a retainer and a status subscription.
Time-box it. Forty-five minutes is plenty if the artefacts exist before the call. If they do not, the meeting becomes production, and production meetings expand until they eat the week they were meant to run. The artefact is the point. The meeting is a forcing function for the artefact.
Incident language belongs here, not in a war room you invent after the screenshot. What we say when a store posts off-brand. What we say when a journey misfires. Who speaks. Who does not. Rehearsed once, used rarely, cheaper than reputation work after the fact.
Finance can attend a monthly. They should not attend the weekly unless the weekly has already failed. The weekly is for operators. The monthly is for the commercial view. Mixing them produces a meeting that is too polite to kill work and too granular to set a number.
Remote, hybrid, Casper-registered, New York-sat — none of that is the design. The design is decision rights. Who can stop a send. Who can add a send. Who cannot. Write it. The weekly then becomes a review of decisions, not a negotiation of taste.
Handover of a practice includes handover of the meeting. If the team cannot run the weekly without the principal, the seat was theatre. By the time the mission ends, the calendar, the kill list, and the numbers page should survive an absence. That is independence. It is also the only honest definition of knowledge transfer.
If you want to start, send the last four weekly agendas — or admit there are none — plus the names of who can change the week. The first month of a mission is often just installing that room. It feels too small to be strategy. It is the entire strategy.
MBX will not sell you a meeting framework with a trademark. It will sit in your weekly until the week is real, then leave the artefacts. That is the work. Everything else is a slide about the work.
A word on tools in the room. The meeting should not be a tour of Salesforce Marketing Cloud, Braze, or the social suite. If the only way to know the week is to click through five UIs, you do not have a week. You have logins. Export the calendar. Put the numbers on one page. Then the platforms can stay where they belong: underneath the decisions, not as the agenda.
If the company is in several time zones, the weekly still exists. It does not become a Slack channel with a thumbs-up. Asynchronous updates can prepare the room. They cannot replace the moment when someone has to say no. That moment is the product. Design for it. The practice will not invent a second meeting to compensate for a room that will not decide.
Camille Edith Baudouin, MBX Consulting