A weekly marketing meeting is useful when it resolves decisions and blockers; routine status belongs in the shared note before the call.
A weekly marketing meeting should create decisions and ownership, not repeat information people could have read beforehand. This template gives a small team a 35-minute rhythm for reviewing signals, resolving blockers, and agreeing on the next useful work.
Copy the structure into the team’s normal document or project system. Keep one running record so decisions and unfinished actions stay visible from week to week.
Prepare asynchronously before the meeting
Ask each owner to update the shared note by a fixed deadline. The update should be short enough to scan and specific enough to act on.
- What shipped since the last meeting?
- What changed in the relevant signal or customer response?
- What is blocked and what decision would unblock it?
- What commitment is at risk this week?
- Which item does not need meeting time?
Link to the source dashboard, campaign brief, draft, or customer evidence instead of copying a large report into the agenda.
The 35-minute agenda
| Time | Section | Required outcome |
|---|---|---|
| 0–5 min | Commitments and changes | Confirm what shipped and what materially changed |
| 5–12 min | Audience and performance signals | Name one signal that needs interpretation or action |
| 12–22 min | Open decisions | Decide, assign more evidence, or explicitly defer |
| 22–29 min | Work in progress and blockers | Remove a blocker or change the plan |
| 29–35 min | Owners and next review | Record actions, owners, due dates, and review points |
1. Commitments and changes
Review last week’s actions without narrating every task. Mark each item done, changed, carried forward, or cancelled. If the same item moves forward repeatedly, discuss the decision or dependency behind it rather than changing the date again.
2. Audience and performance signals
Choose a small set of signals connected to current work: qualified enquiries, replies, activation, retained subscribers, assisted conversions, search demand, content completion, or customer questions. Compare against an appropriate baseline and say when the sample is too small.
A dashboard movement is not automatically an agenda item. Bring it to the meeting when it could change a decision, priority, message, or experiment.
3. Open decisions
Write each decision as a question with an owner and a deadline. Include the options, relevant constraint, and evidence already available.
“Should we move the launch?” is clearer when the note includes the customer commitment, unfinished dependency, available alternatives, and latest safe decision date.
End the discussion with one of three states: decided, evidence assigned, or deferred until a named date. Do not leave an important discussion recorded only as “we will think about it.”
4. Work in progress and blockers
Focus on work that crosses owners or systems. Identify the missing input, approval, access, or decision. Then assign the smallest next action that can change the state of the work.
Move detailed production reviews into a separate working session with only the people needed. Protect the weekly meeting from becoming a live editing room.
5. Owners and next review
Read back every action before the meeting ends. Each action needs one directly responsible owner, a due date, and the place where completion will be visible. Add a review date for experiments and decisions whose result cannot be known immediately.
Copyable meeting note
WEEK OF: FACILITATOR: NOTE OWNER: SHIPPED / CHANGED - Item — owner — evidence or link SIGNALS THAT MAY CHANGE A DECISION - Signal — context — question OPEN DECISIONS - Question — options — constraint — decision owner — deadline BLOCKERS - Blocked outcome — missing input — unblock owner ACTIONS - Action — one owner — due date — completion location DECISION LOG - Date — decision — reason — review date
Rotate the operating roles
- Facilitator: protects the agenda and makes the decision state explicit.
- Note owner: records decisions and actions in the shared system.
- Decision owner: makes or escalates a specific decision.
- Action owner: owns one outcome, not a group assignment.
Rotating facilitator and note ownership can keep the process from depending on one person, while decision accountability remains with the relevant owner.
What to remove from the meeting
Remove status recitals, dashboard tours, brainstorming without a brief, and work that needs a different group. Cancel the meeting when there are no decisions, blockers, or cross-team actions to resolve. The document can still carry the asynchronous update.
Review the meeting after four weeks
Check whether actions are completed, repeated blockers are decreasing, decisions are easier to find, and the meeting stays within its time budget. Change the agenda when the work changes. A useful operating rhythm should make coordination lighter, not become another ritual the team has to feed.
