Meeting cadence for delivery teams: what to keep and what to kill

Delivery teams live in a paradox. They need meetings to coordinate, make decisions, and maintain alignment. They also need uninterrupted time to do the actual work. Most teams resolve this paradox badly — either by having too many meetings (and never getting deep work done) or too few (and losing coordination).

The answer is not fewer meetings or more meetings. It is the right meetings at the right frequency with the right purpose. A well-designed meeting cadence creates rhythm without consuming the team's delivery capacity.

Signs your meeting cadence is broken

• People attend meetings where they have no role and nothing to contribute
• The same topics are discussed in multiple meetings without resolution
• Meetings regularly run over time because the agenda is too full
• Team members block "focus time" on their calendars to protect against meeting creep
• Status updates consume meeting time that should be spent on decisions
• Actions from meetings are not tracked or reviewed

The three layers of meeting cadence

Every delivery team needs three layers of meetings, each serving a different purpose:

Layer 1: Operational (weekly)

Purpose: Keep the work moving. Surface blockers. Make quick decisions.

Format: Short, focused, action-oriented. Fifteen to thirty minutes maximum.

Examples: Weekly team standup, project check-in, sprint planning.

Rule: If it can be resolved asynchronously, it should not be in this meeting.

Layer 2: Governance (fortnightly or monthly)

Purpose: Review the portfolio. Make priority decisions. Allocate resources. Escalate risks.

Format: Structured around decisions, not status. Thirty to forty-five minutes.

Examples: Portfolio review, steering committee, resource allocation meeting.

Rule: Every agenda item should have a decision attached. No decision, no agenda slot.

Layer 3: Strategic (monthly or quarterly)

Purpose: Assess direction. Review whether the portfolio aligns with business goals. Plan the next period.

Format: Longer, more reflective. Sixty to ninety minutes.

Examples: Quarterly planning, strategy review, retrospective.

Rule: This meeting looks forward, not backward. Use it for direction, not status.

How to audit your current cadence

Take your team's calendar and list every recurring meeting. For each one, answer:

1. What decisions does this meeting make?
2. Who needs to be there for those decisions?
3. What would happen if we cancelled it for two weeks?

If a meeting does not make decisions, consider replacing it with an asynchronous update. If half the attendees have no role, reduce the invite list. If nothing would break by skipping it, it might not be necessary.

Designing a cadence for a delivery team of 10–30 people

Here is a practical cadence that works for most delivery teams:

Monday: Weekly team sync (15 min) - What is each person focused on this week? - Any blockers that need help? - Any decisions needed before the next sync?

Wednesday: Project check-ins (30 min per project, as needed) - Only for projects that need coordination - Focus on blockers and decisions, not status - Cancel if there is nothing to discuss

Friday: Portfolio review (30 min, fortnightly) - Review portfolio health dashboard - Discuss exceptions (projects that changed status) - Make decisions about at-risk items - Assign actions with owners and due dates

Monthly: Steering committee (45 min) - Decisions that require senior authority - Resource allocation changes - New project approvals or deferrals

Quarterly: Strategy and planning (90 min) - Review portfolio alignment with business goals - Plan the next quarter's priorities - Retrospective on what worked and what did not

What to kill

The status meeting. If the only purpose is hearing what everyone is working on, replace it with a dashboard or async update. Status meetings are the most common time waste in delivery teams.

The meeting with no agenda. If nobody prepares an agenda, the meeting will drift. Either add structure or cancel it.

The meeting with too many attendees. If more than half the people in the room are observers, they should not be there. Share the minutes instead.

The meeting that never produces actions. If a meeting consistently ends without decisions or actions, it is a discussion forum, not a governance mechanism. Either restructure it or cancel it.

Best practices

Protect maker time. Block at least two half-days per week where no meetings are scheduled. Delivery teams need uninterrupted time to do deep work.

Start with actions from last time. Every recurring meeting should start with a two-minute review of previous actions. This creates accountability and prevents drift.

End with decisions and actions. Every meeting should end with a clear summary: what was decided, who owns what, and when it is due.

Cancel when there is nothing to discuss. A meeting without an agenda should be cancelled, not held out of habit. Respect people's time.

Match frequency to pace. Fast-moving projects may need daily check-ins. Stable projects may only need weekly. Do not apply the same cadence to every project regardless of pace.

How Praxiox helps

Praxiox supports meeting cadence by providing structured meeting records linked to projects, with decisions and actions tracked automatically. The portfolio dashboard replaces status meetings by giving the team a live view of project health.

Meeting records capture the output of each cadence layer — operational actions from weekly syncs, governance decisions from portfolio reviews, and strategic direction from quarterly planning. All linked to the projects they affect.

For teams redesigning their meeting cadence, the steering committee guide covers the governance layer in detail. The decisions vs discussions post explores the principle of outcome-oriented meetings.

Putting this into practice

The safest rollout is usually the smallest one that still proves the point. Pick one live team, one workflow, and one review cycle. That gives you a real test without creating extra admin.

Start where the friction is easiest to see. If is scattered across tools today, fix the handoff that causes the most rework first. If the process already exists, make the update step lighter before you expand the scope.

1. Map the current flow and note where information gets copied, delayed, or lost.
2. Remove one manual step and see whether the team can still keep up.
3. Review the result after two cycles and keep only the rules that clearly help.

The goal is not a perfect rollout. It is a process people will actually keep using once the initial push is over.

What the tool needs to do

A good tool for should reduce handoffs, not add another one. The value is not the interface itself. The value is whether people can keep the system current while they do the work.

That usually comes down to a few practical requirements:

• one place for status, owners, and next steps
• one view that leadership can scan quickly
• one record of decisions and actions
• one workflow that does not depend on a manual copy-and-paste step

If those pieces are missing, the process will drift back into spreadsheets, email threads, or slide decks. Simplicity is the real feature.

How to tell it is working

The process is working when the team stops asking where the latest version lives. You see fewer reminders, fewer surprise escalations, and fewer meetings spent re-creating the same status.

Watch for three signs:

• people update it without being chased
• meetings get shorter because the status is already visible
• decisions move faster because the facts are current

The real signal is trust. When people stop keeping their own shadow list and start relying on the shared view, the system has begun to work properly.

The features page shows the kind of setup that makes those signals easier to see. The PMO use case shows the same behaviour at portfolio level.

If those signs do not move, the workflow is still too hard to maintain. The fix is usually to simplify the steps people touch every week, not to add another rule.

Practical next step

If Meeting cadence for delivery teams is supposed to produce decisions, not just discussion, the first move is to make the meeting shorter and sharper. Keep the agenda focused on exceptions, decisions, and follow-through. Anything that can be read from the dashboard should stay out of the live conversation.

A useful governance change does not need a new committee. It needs a cleaner rule for what gets discussed in the room. Put status in the shared system, reserve the meeting for decisions, and make sure every decision produces an owner and a due date.

That usually shortens the meeting immediately, because people stop reading their updates out loud. It also makes the result easier to trust. When the same structure is used week after week, the team knows where decisions live and what gets reviewed next time.

The features page shows how the workflow stays connected to the work. The PMO use case shows how the same structure plays out in a live operating model.

After two cycles, review what people are still doing outside the system. If the answer is “copying status,” “asking for the latest version,” or “keeping a backup spreadsheet,” the process still needs one more simplification pass. If the answer is “nothing,” the change is probably small enough to stick.

Final check

The cadence is probably right when the team can describe it without checking the calendar. Weekly coordination should be short, predictable, and based on the same shared view every time. If the meeting needs extra explanation to justify its existence, it is probably doing too much. Keep the operational layer light, keep the governance layer separate, and let the dashboard handle status.

Frequently asked questions

How many meetings should a delivery team have per week?

Three to five hours of meetings per week is a healthy range for most delivery teams. More than that and delivery time suffers. Less than that and coordination gaps appear.

Should all team members attend all meetings?

No. Each meeting should have the minimum attendees needed to make its decisions. Observers should receive minutes rather than attend.

How do I reduce meeting time without losing coordination?

Replace status meetings with dashboards and async updates. Keep decision meetings but make them shorter and more focused. Cancel meetings that do not have a clear agenda.

What is the right frequency for a portfolio review?

Fortnightly for most delivery teams. Weekly if the portfolio is fast-moving or under stress. Monthly is usually too infrequent for operational governance.

How do I handle urgent issues between scheduled meetings?

Define an escalation path for urgent items — a Slack channel, a quick ad-hoc call, or a direct message to the decision-maker. Not everything needs to wait for the next scheduled meeting.

Should meetings be the same length every time?

No. End meetings early when the agenda is complete. Do not fill time just because the calendar says sixty minutes. Respecting people's time builds trust in the cadence.