A three-person marketing team showed me their calendar. Six recurring meetings. A Monday standup, a Wednesday content sync, a Thursday campaign check-in, a Friday wrap, a monthly review, and a fortnightly one-to-one with the founder that had become a status report.
Everyone was quietly annoyed and nobody wanted to say so, because cancelling a meeting feels like saying the work in it does not matter.
The number was not the problem. Five of the six were doing the same thing: telling people what happened. Only one of them decided anything.
The test a meeting has to pass
One question sorts every recurring meeting on your calendar.
What decision does this meeting make that cannot be made anywhere else?
If you can name the decision, keep the meeting. If the honest answer is that it keeps everyone informed, you are paying salary hours for a newsletter. Information moves fine in writing. Decisions are where people in a room, arguing for twenty minutes, genuinely beat a document.
The cheapest way to test this is to cancel a meeting for a month and see who complains. Most of the time nobody does. When someone does complain, they will tell you exactly what the meeting was for, which is useful either way.
Do the arithmetic once, because it changes how the calendar feels. A 45-minute meeting with five people is nearly four hours of team time. Weekly, that is roughly sixteen hours a month, which on a small team is a meaningful share of everything that gets produced.
Kill the status meeting first
The round-the-table update is the most expensive habit on a small team, and it survives because it feels responsible.
Here is what actually happens in one. Five people each speak for six minutes. Every person listens to four updates that do not affect them, waiting for their turn, half-preparing what they will say. The one update that mattered to you took ninety seconds and could have been a message.
Replace it with a written update on a fixed day. Three lines per person: what moved, what is blocked, what needs a decision. Slack, Notion, a shared doc, whatever people already open. It takes each person four minutes to write and two minutes to read everyone else's.
Then keep a short live meeting for the blocked items only. Untangling a dependency between two people takes three minutes of conversation and forty messages, so that part stays synchronous.
The objection is always that people will not read the written update. Some will not. The same people were not listening in the meeting either, and now at least it is visible.
The weekly: what is stuck and what changes
Thirty minutes. Everyone doing the work. Two questions only.
- What is stuck, and who can unstick it? Waiting on a founder approval, a client asset, a developer, a budget sign-off. Name the blocker and name the person who removes it.
- What needs a decision this week? Choices somebody has been sitting on because they were not sure who owns them.
Progress reporting stays out. If the campaign is on track, that belongs in whatever tool tracks the work. The weekly is for the things that will not fix themselves.
When this meeting runs long, the cause is almost always one person using it to report rather than to ask. Say so directly the second time it happens. The alternative is that everyone else quietly decides the meeting is a waste and starts multitasking through it.
End with the list of decisions made and who owns each. Two lines in the same channel as the written updates. That record is what stops the same decision being re-made three weeks later.
The monthly: read the numbers together
This is the meeting most small teams either skip or turn into a presentation, and both failures cost the same thing.
The format that works: circulate the report at least a day before, so nobody is reading it live. Then spend the hour on three questions. What continues. What stops. What gets more resource.
Stopping is the hard one. Every marketing team has a channel or a programme that nobody believes in and nobody has killed, because killing it means admitting the last six months were wasted. Put the stop decision on the agenda by name and it gets made. Leave it implicit and it never does.
Keep the report short and consistent. Whatever you decided the team is accountable for, in the same shape every month, so trends are visible. If you built the dashboard in Looker Studio or you are pulling it from HubSpot, the tool matters much less than the report not changing shape every month.
Open with a question rather than a slide. "Which number surprised you" gets you into the actual conversation in ninety seconds. If people arrive without having read the report, run the first five minutes in silence while everyone reads. That is uncomfortable exactly once.
The quarterly: change the plan on purpose
The quarterly session exists so the plan can change in one place instead of drifting every week.
Half a day. Marketing, sales leadership, and the founder. This is the only meeting where priorities are allowed to move, budget shifts, and things get cancelled. Everywhere else, the answer to a new idea is that it goes on the list for the quarterly.
That rule is the whole value. Without it, every interesting thing anyone reads becomes this week's priority, and a small team can absorb about two of those before nothing finishes. The quarterly gives you a legitimate place to say yes to an idea and no to doing it right now.
It should end with one page: what the next quarter is for, the two or three things that get resourced, and the list of what the team is explicitly not doing. That second list is the one people refer back to.
Sales has to be in the room. A marketing plan set without the people who take the leads produces the handoff arguments covered in the sales and marketing handoff audit, three months later and with more feeling.
The one-to-one is not a status report
The meeting that quietly rots on most small teams is the recurring one-to-one, because it drifts into a verbal progress update. The manager already knows what the person is working on. Both people know this. Neither says it.
Keep it and change what it is for. A one-to-one is where you talk about the person: what they want to be better at, what is frustrating them, whether the role still fits, what they need that they have not asked for. Every minute spent on project status in that meeting is a minute not spent on the only conversation that cannot happen anywhere else.
Twenty-five minutes every two weeks is enough for most people. Let the person set the agenda. If they arrive with nothing, ask what has been annoying them, which almost always produces something useful.
Running a review a founder will actually attend
Founders stop attending meetings where they are an audience. They keep attending meetings where their absence blocks something.
So build the monthly around a decision the founder has to make. Budget reallocation, a stop decision, a hire, a pricing question. If the meeting can run perfectly well without them, they will eventually work that out and the invite will start getting declined.
Start with what they care about, which is almost always pipeline and spend. A founder who sits through twenty minutes of channel metrics before hearing about pipeline has already opened their laptop. Lead with the two numbers that connect marketing to revenue, then go into the detail behind them.
Keep it to 45 minutes and end early when you can. Send the material in advance. Follow up with three lines: what was decided, who owns it, when it is due.
And accept the trade honestly. A founder who attends one well-run monthly and one quarterly is more useful than one who half-attends six meetings a month while answering email.
The takeaway
Three meetings. A 30-minute weekly on blockers and decisions. A monthly on the numbers that ends in continue, stop, or fund. A quarterly where the plan is allowed to change.
Everything else is a status update, and status updates belong in writing. Cancel one meeting this week and see who notices. That answer is worth more than any calendar advice.