Operating cadence is where Chief of Staff work becomes visible to the whole leadership team. Staff meetings, business reviews, planning sessions, board prep, customer-risk reviews, and executive offsites can either move decisions forward or become recurring theater. The CoS often has the access and mandate to redesign the system.

Cadence design starts with purpose. A meeting should know whether it exists to decide, inspect, learn, allocate, escalate, or align. When the purpose is unclear, the agenda fills with status. People talk because the meeting exists, not because the work requires the room.

The Chief of Staff can improve cadence by clarifying inputs and outputs. What pre-read is required? What decision is expected? Who owns the agenda? What should happen before the meeting? What artifact leaves afterward? Which topics should not be discussed live? These questions make the room more disciplined.

Status theater is the enemy. Executives sit through updates that could have been written, then rush the decision that needed conversation. A good CoS helps invert that pattern. Written context handles the update. Live time handles trade-offs, exceptions, resource decisions, and unresolved tension.

Cadence also needs rhythm. Weekly staff meetings should not try to do quarterly strategy work. Quarterly business reviews should not become project-level inspection. Board prep should not substitute for executive alignment. Each forum needs the right altitude.

AI can help by preparing summaries, detecting repeated agenda items, surfacing decisions from prior meetings, and flagging topics that have appeared multiple times without resolution. It can also draft pre-read packets from scattered materials. This reduces prep burden and shows where the cadence is stuck.

The CoS should avoid becoming the meeting owner for everything. They may design the cadence and hold the system, but functional leaders still need to own their forums. A leadership team that outsources all meeting discipline to the CoS is not building its own operating muscle.

Rituals should be retired when they stop earning their time. Companies often keep meetings because they once solved a real problem. The CoS can ask whether the problem still exists, whether the meeting still solves it, and whether a lighter mechanism would work now.

Follow-through closes the loop. A decision forum without a follow-up system becomes performance. The CoS should connect cadence to the decision log, owner map, and review calendar. Otherwise the same topics return with new slides and the same unresolved issue.

Good cadence reduces executive anxiety. Leaders know where issues belong, teams know how to escalate, and decisions have a predictable path. That predictability lowers the need for backchannels and urgent one-off meetings.

The test is whether recurring forums make decisions easier. If a meeting's main output is awareness, it may not deserve senior time. If it creates decisions, ownership, and follow-through, it is part of the operating system.

A cadence audit should start with the calendar. List the recurring leadership forums and write the purpose beside each one. If the purpose cannot be stated clearly, the meeting is suspect. If two meetings have the same purpose, one of them is probably redundant.

The CoS should also inspect whether the right people are in the room. Too many people turns decision forums into performances. Too few people creates decisions that lack context or buy-in. The room should match the decision, not the org chart.

Meeting quality improves when agenda items are written as decisions or questions. 'Product update' invites passive listening. 'Should we delay launch to fix reliability?' creates a decision. The CoS can force that level of clarity before the meeting begins.

AI can help by reviewing past agendas and notes to find recurring topics. If the same topic returns every week without resolution, the cadence is not working. The issue may need a decision owner, a different forum, or a narrower question.

Rituals need a sunset clause. A weekly review that was useful during a launch may become wasteful after the launch stabilizes. A CoS can normalize retiring rituals without treating the old meeting as a failure.

The goal is not fewer meetings in the abstract. Some companies need more structured cadence, not less. The goal is the right meeting doing the right job at the right frequency.

A strong cadence also defines what happens outside the meeting. Written updates should arrive with enough time to read them. Agenda items should have owners. Decisions should enter the decision log. Follow-up should return in the right forum, not through random pings. The meeting is only one piece of the rhythm.

The CoS should name the cost of each forum. A weekly executive meeting with eight people is expensive even before prep time. That does not mean it should disappear. It means the output should justify the cost. If the meeting saves time elsewhere, makes better decisions, or prevents risk from drifting, it earns its place.

Cadence design should also leave room for exceptions. A company that over-structures everything becomes slow. A company with no structure becomes reactive. The CoS has to tune the system so urgent work has a path without turning every issue into a fire drill.

One simple rule helps: every recurring forum should have a living owner. If nobody owns the meeting's purpose, inputs, and outputs, the meeting will decay. Ownership keeps the ritual connected to the work it is supposed to serve.

Evidence note: this post uses local backlog framing and general team operating-practice context including https://www.atlassian.com/team-playbook/plays/working-agreements.

This is part 6 of 10 in The Chief of Staff Operating Model.