Meeting Cadence Meaning: How Often Teams Meet

A new manager opens the calendar she inherited and counts eleven recurring meetings. Four of them nobody can explain. Two were created for a project that shipped in March. One exists because a director asked for visibility two years ago and never asked for it to stop.

That calendar is what a meeting cadence looks like when nobody has examined it in a while. The meeting cadence meaning most people reach for is simple — how often a recurring meeting happens — but the useful definition is wider than one invite. Cadence is the rhythm across the whole set, and whether those frequencies reinforce each other or compete.

Nearly all meeting advice is about one meeting. Run a better standup. Write a sharper agenda. None of it touches the question underneath: should this exist at this frequency?

What meeting cadence means, and why ops docs keep using the phrase

Cadence is borrowed from music and cycling: a repeating beat you settle into without counting. Applied to a team, it's the pattern of standing sessions — which exist, how often each fires, how they sit against the work.

The word turns up in job descriptions because it names a responsibility with no other name. "Own the leadership meeting cadence" is sharper than "schedule meetings." It means deciding which conversations repeat, defending the ones that earn it, and retiring the rest — usually with no authority over the calendar.

One distinction saves a lot of confusion. Cadence answers how often; an agenda answers what happens once you're there. A team can have an immaculate agenda and a cadence so wrong the agenda is beside the point — a weekly status meeting about a project that moves monthly.

Four inputs that should set the rhythm, and one that shouldn't

When people ask what is meeting cadence supposed to be for a team their size, size is almost never the variable that matters. Four other things are.

How fast decisions need to land. The dominant input, and the most ignored. If a blocked person can wait three days without anything breaking, weekly is fine. If three days costs you a release, you need a faster loop — or you need to push decision rights down. Cadence is often a workaround for permissions.

How coupled the work is. Two engineers editing the same service need each other far more often than two reps working separate territories. Coupling is physical: shared files, shared customers, handoffs both ways. Teams whose work runs genuinely in parallel can meet monthly and lose nothing.

How distributed the group is. Time-zone spread doesn't just make scheduling awkward, it changes which cadence is honest. A team across nine hours running a daily live sync is running a daily sync for headquarters and a daily imposition on everyone else.

How much changes between sessions. If the honest answer to "what's new" is "not much," the interval is too short. Easy to test, and the one people avoid testing, because habits dislike being measured.

Then the input that shouldn't set cadence and often does: how anxious the most senior person is. Meetings created to reassure a leader cost real money, and they're nearly impossible to cancel because their purpose was never written on the invite.

Do the arithmetic once. Attendees times duration times occurrences per year is what makes a recurring meeting real. Eight people, 45 minutes, weekly comes to roughly 312 person-hours a year — about two months of somebody's working life. Put that figure in the invite description and watch how fast someone volunteers to shorten it.

Meeting cadence examples, with ranges instead of rules

Any table claiming the correct frequency for a meeting type is lying slightly. What's useful is the range teams land in, and what pushes them toward one end.

Each row has a literature. The daily version gets our guide to running a standup meeting, the manager conversation the one-on-one meeting template, the company-wide session the all hands meeting guide and its question-led cousin the town hall meeting format. Skip-levels get our skip-level meetings guide; the leadership session gets how to run an effective staff meeting. What makes one instance worth attending is settled beforehand, which is what a meeting agenda template is for.

Cadence inflation: meetings that outlive their reason

Recurring meetings are created by one person and cancelled by nobody. That asymmetry is the whole disease. Creation takes thirty seconds and costs nothing. Cancellation requires someone to say out loud that a thing colleagues attend isn't worth attending.

Microsoft's June 2025 Work Trend Index special report, built on aggregated Microsoft 365 telemetry, shows what that produces at scale. Half of all meetings fall between 9 and 11 in the morning and 1 and 3 in the afternoon — the two windows where concentration peaks. Meetings after 8 p.m. were up 16% year over year, nearly a third now span multiple time zones, and 57% are ad hoc, held with no calendar invite at all.

That last figure reframes the problem. The ad hoc layer sits on top of the recurring layer, and only one of the two ever gets reviewed. Cut a fifth of your standing invites and the week can still feel identical, because the space you freed filled with unscheduled calls.

Inflation has reliable signatures. Attendance drifts toward optional without anyone declaring it so. A side conversation forms to make the real decisions. And the length never changes, because calendar defaults are a form of policy.

Put an expiry date on every recurring invite you create. Six weeks, twelve, one quarter — the number hardly matters. What matters is that renewal becomes a decision somebody makes out loud instead of the default state of the universe. A meeting that survives that conversation has a defender.

The quieter failure, where the meeting moves into Slack

The opposite problem gets less attention because it never appears on a calendar. Cadence starvation is a team meeting too rarely for how coupled its work is, compensating with message volume.

It looks like this. The same question asked in three channels in a week. A Tuesday decision relitigated Friday by someone who wasn't in the thread. Retros full of "I didn't know that was happening."

The economics are unintuitive. Under-meeting feels cheap because the cost lands as rework rather than blocked calendar time, and rework never appears as a line item. A team that cut its weekly sync and now spends six hours untangling misunderstandings moved that hour somewhere nobody measures.

Auditing a calendar you inherited

An audit is worth two hours a quarter, and most of the value sits in steps three and four.

1. Pull eight weeks of history, not next week's view. Eight weeks catches the fortnightly and monthly meetings a single week hides. Include ad hoc calls.
2. List every recurring meeting with attendee count, duration and frequency. Multiply into person-hours per quarter and sort descending. The top five hold the conversation.
3. Find the decision trail. Name the last three decisions each meeting produced and where they're written down. This separates meetings doing work from meetings performing it.
4. Ask people one at a time, never in the room. Group settings guarantee polite agreement — nobody criticises a colleague's meeting with its owner listening. Privately, people are startlingly direct.
5. Sort into four piles. Keep, halve, merge, stop. Anything you can't place is a keep-for-now with a review date.

Step three is the one people skip and the one that changes the outcome. If the last three decisions live in someone's memory rather than a document, the meeting has a record problem rather than a cadence problem, and cutting its frequency will make things worse. An AI meeting assistant that transcribes the session and lists commitments with owners attached turns that step into a lookup — Laxis does it across Zoom, Google Meet and Teams, 300 minutes a month free. A tool tells you what happened; it has no view on whether it deserved to.

Killing or merging a meeting without political damage

Never delete without naming the destination. "We're cancelling the Thursday sync" sounds like a loss. "The Thursday sync becomes a written update every Wednesday at 4, and we'll book thirty minutes the first time something needs arguing about" sounds like a plan — and forces you to work out where the output goes.

Give the win to whoever created it. If the meeting belongs to a director, the proposal should carry their fingerprints. Meetings get created by someone solving a real problem, and the graceful exit is saying the problem got solved.

Halve before you kill. Fortnightly is a legitimate destination for a weekly meeting and a much easier proposal to accept. If nothing breaks in six weeks, somebody else makes the case for stopping.

Merge along the seams of the work, not the org chart. Two thirty-minute meetings with six overlapping attendees are usually one forty-minute meeting where the dependencies become visible.

Write down what you expect to break. Before pausing a meeting, predict the failure in a sentence: "two people will duplicate work on the migration." Check in three weeks. A prediction that comes true tells you which slice was load-bearing — better than restoring the whole hour out of nerves.

Where async genuinely substitutes, and where it relocates the problem

Async replaces a meeting cleanly when three things are true at once: the content is stable enough to read, nobody has to negotiate, and there's a deadline on responding. Status distribution, written reviews and decision docs with a comment window clear that bar.

It fails in four familiar places. Real disagreement, where a thread lets everyone entrench and gives no way to read a room. New problems, where the fumbling is the value. Anything where silence reads as agreement. And relationship work, which is most of what a one-on-one is for.

The usual failure isn't that async doesn't work. It's that the replacement arrives without a closing time, becomes a queue that never empties, and within a month the team has both the written ritual and a meeting about it. What most teams reach is a written update with a hard reply-by time, plus a short live slot that fires only when something needs arguing about. Record and summarise that slot — most meeting assistants do this now, and Laxis does it in 100+ languages, with live side-by-side translation from Premium up — and you never run it twice.

What a healthy rhythm feels like from the inside

Here's the awkward part about getting cadence right: you can't feel it. A well-tuned calendar produces the absence of a sensation — no Monday dread, no meeting where three people are visibly waiting for it to end. Nobody thanks you for an absence, which is why it drifts back.

So cadence isn't something you set. It's something you keep re-setting, at roughly the rate your work changes shape. Teams that book ninety minutes a quarter for exactly this conversation have, in the nicest possible irony, added one meeting and removed several.

Frequently asked questions

What does meeting cadence mean?

Meeting cadence means how often a recurring meeting happens, and how those frequencies fit together across a whole team - daily, weekly, fortnightly, monthly, quarterly. The phrase covers the entire set of standing invites rather than any single one, which is why ops documents use it as shorthand for a team's operating rhythm.

What is a good meeting cadence for a team?

There is no universal answer, but most delivery teams settle near a short daily or three-times-weekly sync, one 45 to 60 minute working session each week, a manager one-on-one every week or two, and a quarterly session for direction. Tightly coupled work pushes every one of those numbers up.

How often should one-on-one meetings happen?

Weekly for new hires, anyone in a new role, and anyone whose work is changing quickly. Every two weeks is usually enough for an experienced person on steady work. Monthly is too rare to catch a problem while it is still small. The test is whether either person starts saving things up.

What is cadence inflation?

Cadence inflation is what happens when meetings get created faster than they get retired, so a calendar keeps a rhythm long after the reason for it ended. You can spot it in recurring invites nobody can explain, shrinking blocks of unbroken time, and attendance that quietly turns optional.

How do you audit your team's meeting cadence?

Export eight weeks of calendar data, list every recurring meeting with its attendee count and length, and multiply those into hours per quarter. Then ask one question of each: what did it decide, and where is that written down? Anything with no decision trail across three sessions is a candidate to stop.

When should a recurring meeting be replaced with an async update?

Swap to async when the meeting mostly distributes information, the content is stable enough to read, and nobody needs to negotiate. Keep it live when there is genuine disagreement, when the topic is new and badly defined, or when silence would be mistaken for agreement. Always set a reply-by time.