A meeting cadence is the set of recurring meetings that keeps a team aligned, accountable, and moving in the same direction. Get it right and everything flows. Get it wrong and you spend most of your time either in meetings that should have been messages or chasing decisions that never got made because nobody was in the same room.
This post breaks down the types of meetings every growing team needs, how often each one should run, and what the weekly meeting is actually for. It also covers the daily standup vs weekly debate that trips up most leaders, and how we run our meeting rhythm at Sneeze It with both humans and AI agents on the same schedule.
Types of meetings every team needs
Not all meetings do the same job. The mistake most operators make is running one kind of meeting for every purpose: the all-hands that is somehow also a status update, a strategy session, a brainstorm, and a problem-solve. Those meetings collapse under their own weight.
Four meeting types cover almost everything a healthy team needs.
The daily pulse. Short. Ten to fifteen minutes. Its only job is to surface blockers and coordinate daily priorities. It is not a status report. If someone needs to explain their status for more than thirty seconds, that is a conversation to have after the meeting.
The weekly operating meeting. This is the one that matters most. Ninety minutes or less. Scorecard review, rock check, and issue solving. EOS, the Entrepreneurial Operating System created by Gino Wickman, formalizes this as the Level 10 Meeting (a registered trademark of EOS Worldwide). The specific format matters less than the discipline: the same agenda, every week, no exceptions, with the people who own the numbers in the room.
The quarterly planning session. Zoomed out. Where are we versus our 90-day rocks? What did we learn? What are we prioritizing next? This is the meeting where you update the plan, not the meeting where you run the plan.
The one-on-one. Between a seat owner and the person (or agent) accountable to that seat. Not a report-out. A working session where blockers get diagnosed and trust gets built.
Most of the friction I see in team meeting structures comes from collapsing these into each other. The quarterly creeps into the weekly. The weekly becomes a status report. The daily standup turns into a blocker-solve. Each collapse creates drag.
Weekly meeting: what it is actually for
The weekly meeting is not a place to share updates. If information could have been written down, it should have been written down before the meeting started.
The weekly meeting has one job: decide things.
That means: look at the numbers, identify where a number is off, figure out why, agree on the fix, and assign it to a seat. Then move to the next number. At Sneeze It, our weekly meeting covers the full scorecard, every row, in under ninety minutes. Radar, our chief-of-staff agent, publishes the scorecard before the meeting starts so there is no read-aloud of numbers in the room. We look at the row, we see whether it is green or red, we have the conversation about red rows, and we move on.
The reason most weekly meetings fail is that they are built around presenting rather than deciding. Someone walks through slides. People ask questions. The meeting ends. No decisions were made, so a second meeting is needed to make the decisions. Then a third meeting to check whether the decisions were implemented.
A weekly meeting built around deciding eliminates the second and third meeting.
Tally, our KPI-push agent, makes this easier by writing fresh numbers to the scorecard before the meeting starts. The humans in the room do not spend time sourcing data. They spend time on the one thing the meeting is for: deciding what to do about the numbers.
How often should teams meet
The honest answer is: less often than most teams do, and more consistently than any team does.
The frequency problem in most companies runs in one direction: too many meetings, not too few. The typical knowledge worker attends four to six meetings per week on top of the weekly team meeting. Most of those meetings could have been handled asynchronously or eliminated entirely.
The right meeting cadence depends on two variables: decision velocity and team size.
Decision velocity is how fast things change in your business. In a high-velocity environment (a startup launching something, a team running a time-sensitive campaign), decisions need to happen quickly and the weekly meeting needs to be tight. In a lower-velocity environment, bi-weekly may be enough for some meeting types.
Team size drives coordination overhead. A team of five can coordinate with fewer formal meetings because informal coordination is cheap. A team of twenty needs more structure because informal coordination does not scale.
A sensible starting structure for a ten-to-twenty person company: daily pulse (ten minutes, skip when nothing is blocking), weekly operating meeting (ninety minutes, fixed time, same day every week), quarterly planning (half day, off-site or near-off-site), and one-on-ones bi-weekly for each direct report. That is roughly three to four hours per week of structured meeting time. Everything else should probably be a Slack message.
The number people underestimate is how much consistency matters relative to frequency. A team that meets weekly at the same time, every week, with the same agenda, builds muscle memory. The meeting becomes frictionless. A team that meets "when needed" or "usually Mondays but sometimes Tuesdays" spends a meaningful percentage of every meeting recovering the context from the last one.
Meeting rhythm: why the schedule is the accountability system
Meeting rhythm is just the repeating pattern of when your meetings happen. It sounds like a scheduling preference. It is actually an accountability system.
When there is no fixed weekly meeting, accountability slips between sessions. A number was off last week. No meeting happened. The number is off again this week. Nobody noticed. When the weekly meeting is fixed, every number is reviewed on the same schedule, every week, by the same people. Numbers that stay off for two or three consecutive weeks get the extended conversation they need. Numbers that drift and recover get noted. The rhythm is what makes the pattern visible.
At Sneeze It, the meeting rhythm has a second function: it is the cadence at which our agent seats report. Dash, our analytics agent, publishes ad performance numbers every morning. Dirk, our sales agent, writes his pipeline state to a shared file before the weekly meeting. Arin, our call center manager agent, posts appointment rate data before the meeting starts. The meeting rhythm defines when agents publish, which defines when humans can act on what agents surface.
This is the part of meeting rhythm that most teams miss. The rhythm is not just for humans. Every piece of coordination that happens inside the rhythm, including AI-assisted coordination, runs better when the rhythm is consistent.
Daily standup vs weekly: which one your team actually needs
The daily standup vs weekly question comes up constantly, and the framing is usually wrong. Most teams treat them as alternatives. They are not. They serve different purposes and a healthy team usually needs both.
The daily standup is coordination. It answers: what is everyone doing today, and is anything blocked? Fifteen minutes. No slides. No discussion of strategy. If a blocker requires discussion, that discussion happens outside the standup, between the two people who need to resolve it.
The weekly meeting is accountability. It answers: where are our numbers, and what do we need to decide to fix the ones that are off? Ninety minutes. Fixed agenda. The numbers are already in the room because someone prepared them before the meeting started.
The teams that skip the daily standup and try to handle coordination in the weekly meeting end up with bloated weekly meetings that run long and cover too much. The teams that skip the weekly meeting and try to handle accountability in daily standups end up with no venue for looking at trends, making decisions, or surfacing things that matter but are not immediately urgent.
The right answer for most teams: run a daily standup at ten minutes, protect it aggressively, and run a weekly meeting at ninety minutes with a fixed agenda. Let each meeting do only its job.
Where teams cut: if the team is small (three to five people) and communicates in Slack throughout the day, the daily standup may be redundant. But even small teams benefit from the weekly meeting discipline.
Frequently asked questions
What is a meeting cadence? A meeting cadence is the repeating schedule of recurring meetings that keeps a team aligned and accountable. It typically includes a daily standup, a weekly operating meeting, quarterly planning sessions, and regular one-on-ones between seat owners and their direct reports.
How often should a small business team meet? Most small business teams (ten to twenty people) do well with a daily ten-minute pulse, a weekly ninety-minute operating meeting, bi-weekly one-on-ones, and a quarterly planning half-day. More frequent meetings are rarely more productive; consistent meetings at a fixed time matter more than frequency.
What is the difference between a daily standup and a weekly meeting? The daily standup handles coordination: what is happening today and what is blocked. The weekly meeting handles accountability: where are the numbers and what decisions need to be made. They are not alternatives. Most teams need both.
How do I fix a meeting that always runs long? Long meetings almost always have the same cause: the agenda mixes decision-making with information-sharing. Separate them. Publish information before the meeting so the meeting is only for decisions. Set a timer for each agenda item and enforce it.
Should AI agents be on the same meeting schedule as humans? Yes. If an agent owns a seat with measurable outcomes, its numbers should be reviewed on the same cadence as human seat numbers. The meeting rhythm is what keeps agent performance visible and correctable. Agents that report outside the team's regular cadence drift faster because nobody is looking at their numbers on a consistent schedule.
Run your operating system in OTP
OTP is the place where your meeting cadence lives in practice: a single chart where humans like Bogdan and Janine sit alongside agents like Radar and Dash, with shared scorecards reviewed on the same weekly rhythm and rocks that give every seat a quarterly target. If you are designing your accountability structure for a hybrid human-agent team, OTP is built for exactly that.
In Claude Desktop or Cursor or any MCP client, add this block:
"otp": {
"command": "npx",
"args": ["-y", "@orgtp/mcp-server"]
}
Restart the client. Then ask: "Use OTP to show me how to set up a weekly meeting cadence with both humans and agents on the same scorecard."