How to Run a Marketing Team Meeting That Isn't a Waste of an Hour
Marketing meetings have a bad reputation because most of them earn it. People confuse "we talked about marketing" with "we made decisions about marketing." Those are different activities. One of them needs a room full of people. The other one usually needs three. An effective marketing team meeting structure fixes this by forcing you to separate the two, and most teams never do.
"A good meeting means everyone gets a turn to update the group"
This is the most common setup I see. Status round robin. Everyone says what they did last week. The kernel of truth is real: people do need visibility into what their teammates are working on. But a meeting is the most expensive way to deliver that information. If six people sit in a room for 60 minutes, that's six person-hours spent so one person could mention a Facebook ad test. Status updates belong in a shared doc or a Slack channel, not a live meeting. People can read five times faster than someone can talk.
"Longer meetings mean we're being thorough"
I used to believe this. On the $2.2B infrastructure project I ran marketing for, I inherited a weekly meeting that ran 90 minutes. It felt thorough because it was exhausting. But thoroughness isn't time spent, it's decisions made per minute. When I timed it, we made maybe four real decisions in that 90 minutes. The rest was context-setting, tangents, and people thinking out loud in front of eight colleagues. Long meetings usually mean unclear purpose, not rigor.
"If we skip the meeting, things will slip through the cracks"
This is the fear that keeps bad meetings alive. The truth is the opposite happens more often. Things slip through the cracks because the meeting is so unfocused that the one decision that actually mattered got twelve minutes squeezed between a status update and someone's question about the intranet. A tight, well-run meeting catches more, not less, because attention isn't being rationed across junk.
What actually matters instead
The fix is simple: a meeting should only contain things that require real-time discussion between specific people. Everything else gets moved out. Here's the exact agenda format I use now, and it's the one that cut my weekly marketing meeting from 60 minutes to 25.
- Pre-read, not live read (0 minutes in the meeting): Status, metrics, and campaign updates go into a shared doc 24 hours before the meeting. Everyone reads it before they show up. If someone hasn't read it, that's on them, not the group.
- Numbers check (3 minutes): One person, usually me, states the three metrics that matter that week. CAC, conversion rate, pipeline, whatever is live. No discussion yet. Just the facts on the table.
- Decisions needed (15 minutes): This is the meeting. A running list of open decisions, each with an owner. We go item by item. If a decision doesn't need the full group, it gets pulled and handled offline between the two relevant people.
- Blockers (5 minutes): Anyone stuck says so. We assign a name to unstick them. We do not solve it live unless it takes under two minutes.
- Next week's one priority (2 minutes): One sentence. What's the single most important thing the team is pushing on. Not five things. One.
That's 25 minutes. When I ran a DTC brand from $100K to $3M+ in revenue, this exact structure replaced an hour-long Monday meeting that half the team dreaded. Nobody dreads 25 minutes with a clear decisions list.
The math behind why this matters: if you have six people in a weekly hour-long meeting, that's six hours of company time every week, 312 hours a year. Cut it to 25 minutes and you get back roughly 3.5 hours a week, or 182 hours a year, which is more than four full work weeks of time handed back to the team. That's not a soft win. That's a person's entire month.
The most common mistake
The mistake almost everyone makes is treating the agenda as a formality instead of a filter. They'll write "Agenda: Updates, Discussion, Next Steps" and call it done. That's not an agenda, that's a container. A real agenda names the specific decisions that need to get made and who needs to be in the room for each one. If you can't name a decision, that topic doesn't belong in the meeting. Send it in writing instead.
I also see leaders invite too many people out of politeness. Someone might need the information from the meeting without needing to be in the discussion. Send them the notes. Protect the room for people who are actually deciding something.
Take this and try it next week. Before your next meeting, write down every item on your usual agenda and ask one question of each: does this require live discussion between specific people, or can it be read? Cut everything that fails that test. Time what's left. You'll probably land somewhere between 20 and 30 minutes, and your team will actually leave with clear next steps instead of a vague sense that time passed.