How to Build an Operating Cadence: The Rhythm of Business
Takeaway: Give each recurring meeting one decision or coordination job, connect the outputs across time horizons, and remove meetings that only repeat written status.
An operating cadence is the recurring sequence of check-ins, reviews, and planning sessions that a team uses to run the business. It may include daily, weekly, monthly, quarterly, and annual layers, but frequency is only one design choice.
A working cadence answers five questions:
- What is this meeting for?
- Which information arrives before it?
- Which decisions happen in it?
- Who owns the follow-through?
- Where does the output go next?
Without those answers, a calendar can be full while decisions and priorities still drift.
Start with decisions, not recurring slots
Before adding a meeting, map the work the leadership team needs to do. Separate routine information sharing from decisions, problem-solving, and longer-range planning.
Andrew Grove's High Output Management distinguishes recurring process-oriented meetings from mission-oriented meetings called for a specific decision (High Output Management). That distinction prevents an urgent one-time decision from taking over every weekly meeting.
Patrick Lencioni's Death by Meeting also argues for different meetings with different purposes rather than one recurring session trying to cover everything (The Table Group).
For each current meeting, write a one-sentence purpose. If two meetings have the same purpose, decide whether they serve different audiences or whether one can go.
Choose a starting set of time horizons
Verne Harnish's Mastering the Rockefeller Habits organizes execution around priorities, data, and a rhythm of daily, weekly, monthly, quarterly, and annual meetings (Scaling Up). That model is a useful starting point, not a requirement to create every layer.
Daily or near-daily coordination
A short huddle can help a time-sensitive team surface today's blockers and assignments. Set a time limit and define what moves into a separate conversation. The format can be seated, standing, remote, or asynchronous. The outcome matters more than the posture.
A leadership team with stable work may not need a daily meeting. Use this layer when the cost of waiting until the weekly meeting is material.
Weekly execution
The weekly meeting keeps near-term priorities moving. Review a small set of indicators, identify cross-functional issues, and make the decisions that can't wait for a monthly review.
Move status into a written pre-read. Use live time for exceptions, tradeoffs, and ownership. A leadership-team meeting should end with decisions, owners, and due dates that can be carried into the next week.
Monthly operating review
The monthly layer looks for trends rather than a single week's result. Compare performance with the plan, examine recurring issues, and decide which problem requires a broader course correction.
Functional leaders should know which measures they own and what explanation is expected. Avoid turning the review into a sequence of presentations with no shared decision.
Quarterly planning and review
The quarterly meeting reviews progress, sets or adjusts priorities, and allocates attention for the next period. If the company uses OKRs, the quarter may be the cycle for setting and reviewing them. John Doerr's Measure What Matters describes quarterly OKR use at Intel and Google (What Matters).
Keep current operating issues from consuming the whole session. Bring only the issues that affect the next quarter's priorities, resources, or assumptions.
Annual strategy and planning
The annual layer sets a longer direction and the assumptions behind it. Some teams use an off-site; others work effectively in the office or remotely. Choose the setting that supports the decisions, participation, and budget.
Annual planning shouldn't become a disconnected event. Its decisions need to shape the quarterly priorities and resource plan.
Make information move between the layers
A cadence becomes useful when one meeting's output changes the next layer.
Consider a customer-onboarding problem:
- Weekly: Support reports that three new customers are blocked by the same missing product configuration. The team assigns an immediate owner and records the pattern.
- Monthly: The operating review shows that the same handoff delayed onboarding across several weeks. Leaders decide that the issue needs a process change rather than another case-by-case fix.
- Quarterly: Product, sales, and support propose a shared onboarding objective, assign resources, and agree on the measure they will review.
- Weekly again: The leadership team tracks the approved work and escalates a dependency only when it threatens the quarterly objective.
The example shows why each layer needs a distinct job. The weekly meeting addresses the immediate block. The monthly review identifies a pattern. The quarterly session makes a resource and priority decision.
Design the inputs and outputs
For each recurring meeting, define:
Inputs: metrics, written updates, proposals, risks, or decisions needed. Name the owner and deadline for each input.
Agenda: the small number of items that require the group. Put the decision or question in the heading rather than a topic label such as "onboarding update."
Outputs: decisions, owners, deadlines, open questions, and items moved to another forum.
Record: a decision log or shared system where the team can find the current answer.
Next layer: the review or planning session that needs the output later.
This design keeps the cadence from depending on one person's memory.
Keep the cadence stable enough to trust
Consistency lets people plan their work and prepare. Protect the recurring times where practical, publish the calendar in advance, and set material deadlines around it.
Stability doesn't mean preserving a meeting after its purpose disappears. A canceled weekly session may be reasonable during a quiet period. A quarterly review may move for a company event. Make deliberate changes and communicate what happens to the decisions the meeting would have handled.
Prune the calendar
Review recurring meetings each quarter. Ask:
- Does this meeting still have one clear purpose?
- Are the required people present, and are unnecessary attendees free to leave?
- Which decisions did it make in the last three sessions?
- Can reporting move into writing?
- Does another meeting already do this job?
- What breaks if we remove or reduce the meeting?
Kill, combine, shorten, or redesign sessions that no longer earn the time. Run the experiment for a defined period and check whether work improved or new gaps appeared.
The chief of staff's role
The chief of staff may own the calendar architecture, agendas, pre-reads, facilitation, decisions, and follow-through. Clarify where process ownership ends and executive accountability begins.
The CEO and leadership team still own their decisions and functional outcomes. The cadence owner makes the process usable, identifies drift, and brings unresolved design choices back to the team.
Useful measures include:
- percentage of required inputs submitted on time;
- decisions with a named owner and due date;
- repeated topics that return without progress;
- meeting time used for status rather than decisions; and
- recurring meetings removed or shortened after review.
Choose only measures the team will actually use.
How often should a leadership team meet?
Match frequency to the speed and consequence of the work. Many teams use weekly execution, monthly operating, and quarterly planning layers. Daily and annual sessions depend more on context.
Who owns the cadence?
Often a chief of staff or operations leader owns the process on behalf of the CEO. The leadership team remains accountable for the decisions and follow-through within it.
How do I fix too many meetings?
Write the purpose and recent decisions for each meeting. Move reporting into a pre-read, merge overlapping forums, and remove sessions that no longer have a clear job.
Start with the free Effective 1:1 Template for Operators if recurring one-on-ones are the first layer you want to standardize.
