What is meeting cadence?

Meeting cadence is the rhythm and frequency of your recurring meetings: how often they happen (daily, weekly, biweekly, monthly) and how long they last. The right cadence balances alignment needs with deep work time, matching the frequency to how quickly the underlying information changes.

How often should engineering teams meet?

Most engineering teams do well with 4-8 hours of meetings per week: daily or 3x/week standups (15 min), weekly or biweekly 1:1s (30 min), sprint ceremonies per cycle, and a weekly team sync (30 min). The exact cadence depends on team size, project complexity, and how distributed the team is. If your team exceeds 10-12 hours of meetings per week, your cadence likely needs adjustment.

How do you change meeting cadence without creating friction?

Run a time-limited experiment. Pick one meeting, change its frequency for two weeks, and measure the result. Frame it as "let's try this for two weeks" rather than "I'm canceling your meeting." When the experiment shows no negative impact, the change becomes easy to make permanent.

Meeting Cadence: The Right Rhythm for Engineering Teams

Key Takeaways

✓Most engineering teams inherit their meeting cadence from a previous manager and never question it.
✓The right cadence matches the rate of change. Daily standups make sense when work changes daily, but not every team needs them.
✓Engineers need at least two 4-hour uninterrupted blocks per week for deep work. Your cadence should protect that.
✓A simple audit ("what breaks if we skip this?") reveals which meetings are too frequent and which are missing entirely.

Your team has 15 recurring meetings on the calendar. Some happen daily. Some happen weekly. A few happen biweekly. Nobody remembers why any of them are at their current frequency.

That's not a calendar. That's inherited habit.

Meeting cadence, the rhythm and frequency of your recurring meetings, is one of the most impactful things an engineering manager can control. Get it right and your team has enough alignment to move fast without losing half their week to syncs. Get it wrong and you end up with either meeting fatigue from too many meetings or constant miscommunication from too few.

The number of weekly meetings has increased 153% since 2020. The average knowledge worker now spends 57% of their time in meetings, email, and chat, leaving only 43% for focused work.

— Microsoft Work Trend Index

What meeting cadence means (and why most teams get it wrong)

Meeting cadence is simply how often a recurring meeting happens: daily, weekly, biweekly, monthly, or quarterly. But "how often" is only half the question. The other half is "how long" — a daily 15-minute standup and a daily 45-minute "sync" have very different costs.

Most teams get cadence wrong because they set it once and never revisit it. The daily standup made sense when the team was 4 people working on a single project. Now the team is 12, working across three streams, and the standup takes 25 minutes where half the room tunes out.

The weekly team sync was useful when the product was pre-launch and everything changed weekly. Now the product is stable, updates are incremental, and the meeting is mostly people reading status updates they could have posted in Slack.

Cadence should match the rate of change. When things change fast, meet more often. When they stabilize, reduce frequency. But teams rarely make this adjustment. They just keep meeting at whatever frequency was set six months ago.

The meeting cadence framework

Categorize your recurring meetings by their purpose, then assign a default cadence based on how quickly the underlying information changes:

Alignment meetings: standups, team syncs, cross-team check-ins. Purpose: keep everyone moving in the same direction. Default cadence: daily to weekly, depending on team size and pace.

Planning meetings: sprint planning, roadmap reviews, quarterly planning. Purpose: decide what to work on. Default cadence: per sprint cycle (weekly to biweekly). These should match your development cycle, not an arbitrary calendar rhythm.

Feedback meetings: 1:1s, retrospectives, peer reviews. Purpose: improve the team and individuals. Default cadence: weekly to biweekly for 1:1s, per sprint for retros. These need enough frequency to address issues before they compound.

Decision meetings: architecture reviews, go/no-go calls, escalations. Purpose: make a specific decision. Default cadence: as needed. These should not be recurring at all. Schedule them when there's a decision to make, cancel when there isn't.

Information sharing: all-hands, demos, knowledge shares. Purpose: broadcast updates. Default cadence: biweekly to monthly. Finding the optimal meeting frequency for each type is what separates teams that move fast from teams that meet all day. Many of these are better served by async communication, like a recorded video or written update that people consume on their own time.

The key principle: cadence should match the rate of change. If nothing meaningful changes between occurrences, the meeting is too frequent. If people are regularly surprised by changes they didn't know about, it's not frequent enough.

Recommended cadences for engineering meetings

Standup. Daily or 3x/week, 15 min, team of 5-8. Go async if your team is over 8 or people are clearly multitasking. If you're questioning the format entirely, our analysis of whether standups are worth it can help.
1:1. Weekly or biweekly, 30 min. Weekly for new reports, biweekly once trust is built. A dedicated 1:1 meeting template keeps these sessions structured.
Sprint planning. Per sprint start, 60-90 min, team + PM. Move estimation to async pre-work to keep it under 90 min.
Retrospective. Per sprint end, 45-60 min, full team. Collect input async beforehand; use the meeting for discussion only.
Team sync. Weekly, 30 min, team + stakeholders. Cut to biweekly if updates are repetitive.
All-hands. Monthly, 30-45 min, entire org. Consider async written updates with quarterly live Q&A sessions.
Architecture review. Biweekly or monthly, 60 min, senior engineers. Only when there are proposals to review. Skip if the queue is empty.
Demo/showcase. Biweekly, 30 min, team + stakeholders. Celebrate shipped work, keep it energizing.

When to increase frequency: New team, new project, high ambiguity, team members in very different time zones who need more intentional overlap, post-incident when coordination is critical.

When to decrease frequency: Stable product, experienced team, repetitive updates, attendees multitasking during the meeting, same topics recurring with no new information. Whatever frequency you choose, a meeting agenda template keeps each session focused.

If your team has more than 10 hours of meetings per week, your cadence is almost certainly wrong. Engineering teams doing complex work need at least two 4-hour uninterrupted blocks per week. Use the meeting cost calculator to see what your current cadence actually costs.

How to audit your current cadence

This exercise takes 30 minutes and can save your team hours every week.

Step 1: List all recurring meetings. Open your team's calendars and write down every recurring meeting: name, frequency, duration, and number of attendees. Calculate the total weekly hours.

Step 2: For each meeting, ask "what breaks if we skip this?" Be honest. If the answer is "nothing would break," the meeting is too frequent or unnecessary. If the answer is "it would be annoying but we'd figure it out," reduce the frequency. If the answer is "we'd lose critical alignment," keep it.

Step 3: Check for overlapping purposes. Do you have both a daily standup and a weekly team sync that cover the same topics? Do you have a sprint retro and a separate "team health" meeting? Consolidate meetings with overlapping purposes. If meetings overlap because ownership is unclear, a RACI matrix can resolve the confusion.

Step 4: Apply the too many meetings framework. For each meeting that survives Steps 2 and 3, evaluate: should it stay sync, go async, get shortened, or be reduced in frequency?

Step 5: Experiment for two weeks. Change the cadence. Tell the team why. After two weeks, check: did alignment suffer? Did anything break? Adjust based on results, not assumptions.

Signs your cadence is wrong

Too many meetings

People routinely multitask (camera off, typing sounds, delayed responses)
Attendees skip without consequence, and nobody notices
The same topics come up across multiple meetings in the same week
Engineers complain they "can't get anything done" between meetings
Your team spends more than 12 hours per week in meetings

Too few meetings

Misalignment surfaces late, in code reviews, demos, or customer escalations
Decisions get delayed because people can't find time to discuss
Team members feel isolated or out of the loop
Surprises in sprint reviews ("I didn't know we were building it that way")
Important context lives in one person's head and never gets shared

The sweet spot

Your cadence is right when engineers have 4-6 hours of meetings per week (not 15-20), clustered on specific days rather than scattered across every day. A no-meeting day is a strong signal your cadence is healthy. It means you've compressed alignment into fewer, more focused sessions.

Cluster your recurring meetings on 2-3 days per week. This protects the remaining days for deep work. Tuesday-Thursday as meeting days and Monday-Wednesday-Friday as focus days is a popular pattern for engineering teams.

Set the cadence, then measure it

Setting the right cadence isn't a one-time exercise. Teams grow, projects change, and the cadence that worked six months ago might be dragging you down today.

The best teams treat meeting cadence like any other process: set it, measure it, and improve it regularly. Track weekly meeting hours per person as a team metric. When the number creeps above 10, it's time for another audit.

Kill One Meeting makes this automatic. It connects to your Google Calendar, collects anonymous ratings from your team on every recurring meeting, and surfaces the ones your team rates lowest, so you can see exactly which meetings need a cadence change. One meeting per month, fixed or killed. Free for 30 days.

Because the right meeting cadence isn't about having fewer meetings. It's about having the right meetings at the right frequency, and nothing more.

Frequently asked questions

What is meeting cadence?: Meeting cadence is the rhythm and frequency of your recurring meetings: how often they happen (daily, weekly, biweekly, monthly) and how long they last. The right cadence balances alignment needs with deep work time, matching the frequency to how quickly the underlying information changes.
How often should engineering teams meet?: Most engineering teams do well with 4-8 hours of meetings per week: daily or 3x/week standups (15 min), weekly or biweekly 1:1s (30 min), sprint ceremonies per cycle, and a weekly team sync (30 min). The exact cadence depends on team size, project complexity, and how distributed the team is. If your team exceeds 10-12 hours of meetings per week, your cadence likely needs adjustment.
How do you change meeting cadence without creating friction?: Run a time-limited experiment. Pick one meeting, change its frequency for two weeks, and measure the result. Frame it as "let's try this for two weeks" rather than "I'm canceling your meeting." When the experiment shows no negative impact, the change becomes easy to make permanent.