How to Build an Operating Cadence: The Rhythm of Business
Takeaway: An operating cadence is the fixed rhythm of meetings and reviews that keeps a leadership team aligned, and building one well means matching each meeting to a distinct job, spacing them by time horizon, and holding the schedule steady enough that people can plan their work around it.
Every company runs on a rhythm, whether anyone designed it or not. Meetings appear, reviews get scheduled, planning happens in fits and starts, and the whole thing either supports the work or gets in its way. The operating cadence is that rhythm made deliberate. It's the recurring schedule of check-ins, reviews, and planning sessions that keeps a leadership team pointed in the same direction between the big strategic moments.
The chief of staff usually owns this cadence. You're the person who decides what meets weekly versus quarterly, protects the calendar from drift, and makes sure each session actually does its job. Get it right and the business runs on rails. Get it wrong and you have either a leadership team flying blind between quarterly planning sessions or one drowning in redundant meetings. This is a guide to building it on purpose.
What an Operating Cadence Actually Is
An operating cadence, sometimes called the rhythm of business, is a layered set of recurring events, each tied to a time horizon. The shortest cycles handle the day-to-day, and the longest handle strategy. When they fit together, information and decisions flow up and down at the right speed.
The most widely used version of this idea comes from Verne Harnish's Mastering the Rockefeller Habits, which organizes execution around three themes: priorities, data, and rhythm. Harnish argues that a healthy company needs an effective rhythm of daily, weekly, monthly, quarterly, and annual meetings to keep the team aligned and accountable, each layer reinforcing the priorities and the plan (Gazelles / Scaling Up). The specifics matter less than the principle: different decisions need different frequencies, and stacking them intentionally is what produces alignment.
Match Each Meeting to a Distinct Job
The most common cadence failure is meetings that blur together, so that the weekly and the monthly cover the same ground and neither does it well. The fix is to give each layer a clear and separate purpose.
Andy Grove made this distinction sharp in High Output Management. He separates process-oriented meetings, which run on a regular cadence to share information and keep the operation running, from mission-oriented meetings, which are ad hoc and exist to make a specific decision. His process meetings come in recognizable forms: the one-on-one, the staff meeting where a manager meets all direct reports, and the operation review where people who don't usually work together come together (High Output Management). Each has a defined job, and knowing the job tells you how to run it.
Patrick Lencioni pushes the same logic in Death by Meeting: the answer to bad meetings isn't fewer meetings, it's different meetings for different purposes, each with its own cadence and rules (The Table Group). Before you place anything on the calendar, be able to say in one sentence what that meeting is for.
A Practical Cadence to Start From
Here is a workable default for a leadership team. Adapt the frequencies to your company's pace, but keep the principle that each layer has a distinct job.
Daily or near-daily: the standup
A short, standing huddle for the most time-sensitive teams, focused on what is happening today and what is blocked. Ten to fifteen minutes, no sitting, no problem-solving in the room. Its only job is to surface blockers fast so they get handled offline. Not every leadership team needs a daily, but fast-moving ones benefit from a very short one.
Weekly: the tactical meeting
The workhorse of the cadence. This is where the leadership team reviews the handful of numbers that show whether the week is on track, confirms the near-term priorities are moving, and resolves the cross-functional issues that need a group decision now. Keep it tactical. Save strategy for a slower session, or urgent noise will crowd out long-term thinking every single week.
Monthly: the operating or business review
A step back from the week to look at trends rather than snapshots. How are the monthly numbers tracking against plan? Which priorities are ahead or behind? What needs a course correction that's bigger than a weekly fix but smaller than a strategic pivot? This is Grove's operation review in practice, where functional leaders show their work to peers and the wider team.
Quarterly: planning and review
The strategic layer. Set or reset the priorities for the coming quarter, review progress against goals, and make the larger decisions that shape the next few months. If your company runs on OKRs, the quarter is the natural unit for setting and grading them. John Doerr's Measure What Matters documents how Intel and later Google used a quarterly objectives-and-key-results cycle to keep large organizations focused on a small number of measurable goals (What Matters). The quarterly session is also the moment to look far enough ahead that the day-to-day can't .
Annual: strategy and planning
The longest horizon. Set the year's direction, the annual plan, and the goals that the quarters will ladder up to. This usually calls for an off-site and a slower pace, because the decisions are the most consequential and the least reversible.
Design Principles That Keep a Cadence Healthy
The schedule is only half the work. These principles keep it from decaying into calendar clutter.
Protect the strategic layers from the tactical. The natural gravity of any leadership team is toward the urgent. Left alone, the quarterly session fills with this-week firefighting. Guard the longer-horizon meetings so they stay about the longer horizon.
Keep the schedule stable. A cadence works because people can plan around it. If the weekly meeting moves every week and the quarterly review slips a month, the rhythm stops being something people trust. Stability is part of the value.
Make inputs flow between layers. The quarterly plan should set the priorities the weekly meeting tracks. The weekly issues that keep recurring should surface in the monthly review. When the layers feed each other, the cadence becomes a nervous system rather than a stack of unrelated calendar events.
Move reporting out of live time. Status belongs in a written pre-read or a shared dashboard, not read aloud in the room. Reserve meeting time for the decisions and debates that actually need the group present.
Prune regularly. Cadences accumulate meetings the way drawers accumulate clutter. Every quarter, ask which recurring meetings still earn their place. Kill or merge the ones that don't .
The Chief of Staff's Role in the Cadence
You're the keeper of the rhythm. In practice that means owning the calendar architecture, writing or curating the agendas, collecting the pre-reads, facilitating the sessions, and capturing the decisions and follow-ups. It also means being the person who notices when the cadence has drifted, when a meeting has lost its purpose, or when a new layer is needed because the business has grown.
Done well, this is quiet, high-leverage work. Nobody thanks you for a cadence that runs smoothly, in the same way nobody thanks a heartbeat. But when the rhythm holds, the leadership team spends its energy on the work instead of on figuring out when and where to talk about the work.
FAQ
What is the difference between an operating cadence and a meeting schedule? A meeting schedule is just a list of when things happen. An operating cadence is a designed system where each meeting has a distinct job, the frequencies match the time horizons of the decisions, and the layers feed each other. Any company has a meeting schedule; a deliberate operating cadence is the difference between rhythm and noise.
How often should a leadership team meet? A common and workable default is a short daily or near-daily standup for fast-moving teams, a weekly tactical meeting, a monthly operating review, a quarterly planning session, and an annual strategy off-site. Adjust the frequencies to your pace, but keep each layer distinct so they don't collapse into one another.
Who owns the operating cadence? Usually the chief of staff or the head of operations, working on behalf of the CEO. The owner sets the calendar architecture, protects the schedule from drift, curates agendas and pre-reads, and makes sure each meeting keeps doing its job. The CEO owns the outcomes; the cadence owner owns the process.
How do I fix a cadence that has too many meetings? Audit every recurring meeting against a one-sentence purpose. Merge the ones that overlap, kill the ones that no longer have a clear job, and move pure status reporting into written pre-reads or dashboards. Do this on a regular schedule, because cadences accumulate clutter naturally and need periodic pruning.
How do I build an operating cadence or rhythm of business? Start by giving every recurring meeting one clear job, then space the layers by time horizon: a short daily or near-daily standup for fast teams, a weekly tactical meeting, a monthly operating review, a quarterly planning session, and an annual strategy off-site. Keep the schedule stable so people can plan around it, let each layer feed the next, and prune anything that no longer earns its place. Harnish's Rockefeller Habits is the canonical version of this layered rhythm (Scaling Up).
If you want a starting structure, our Operating Cadence Blueprint lays out the daily, weekly, monthly, and quarterly meetings with a purpose statement, sample agenda, and pre-read prompt for each layer. Join The Brief to download it and get future operator playbooks as they publish.
