How to create an operating cadence for your company
An operating cadence is the rhythm of meetings, reviews and planning that runs the company. How to design the stack from daily to annual for a company of twenty to three hundred people, and make it stick.

An operating cadence is the fixed rhythm of meetings, reviews and planning sessions through which a company runs itself: short daily or weekly check-ins for execution, monthly reviews for performance, quarterly sessions for priorities and an annual cycle for strategy. To create one, define each level's purpose, attendees, duration and outputs, connect the levels so that each one feeds the next, put the dates in the calendar for the whole year, and protect them for at least ninety days, until the rhythm becomes habit.
Most companies have meetings. Fewer have a cadence. The difference is that in a cadence every meeting has a job, the right people are in it, and what it produces goes somewhere. Without that, leadership time fills up with status updates, decisions are made in corridors and the founder becomes the routing system for everything.
What an operating cadence is, and what it is not
A cadence is not a meeting schedule. It is the management system expressed in time. It answers when the company looks at its numbers, when it decides priorities, when it checks commitments and when it steps back to think about direction. Robert Kaplan and David Norton, writing in Harvard Business Review about the management system, described this as a closed loop that links strategy to operations through a planned sequence of reviews. The idea is simple. Running it consistently is the hard part.
It is also not more meetings. A well-designed cadence usually replaces a scattering of ad hoc meetings, update calls and one-off escalations with fewer, better-prepared sessions. Leslie Perlow and colleagues, in their Harvard Business Review work on meeting overload, make the point that the problem is rarely meetings as such, but meetings without a clear purpose that crowd out focused work.
The cadence stack
Five levels cover almost every company. Not every team needs every level, but the leadership team needs all of them.
| Level | Purpose | Attendees | Duration | Outputs |
|---|---|---|---|---|
| Daily | Unblock today's work and spot problems early | Operational teams with their shift or project lead | 10 to 15 minutes, standing | Blockers raised, each with an owner |
| Weekly | Review the scorecard, track priorities, solve the most important issues | Leadership team, and each team with its lead | 60 to 90 minutes | Decisions, actions with owners and dates, issues escalated |
| Monthly | Review performance against plan and progress on initiatives | Leadership team, finance, initiative owners | Two to three hours | Variances explained, corrective actions, forecast updated |
| Quarterly | Close the quarter, set the next 90-day plan, re-sequence the roadmap | Leadership team, sometimes the next layer of managers | Half a day to a full day | Next quarter's priorities and OKRs, roadmap changes |
| Annual | Revisit strategy, set the year's objectives, budget and roadmap | Leadership team, with the board or investors where relevant | One to two days, often off-site | Strategy refreshed, annual plan, budget, roadmap |
How each level feeds the next
The value of a cadence is in the connections. Each level works with what the level below produces, and sends decisions back down.
- Daily to weekly. Issues that a team cannot solve within a day go to the weekly meeting, with an owner and a short description, rather than as a corridor conversation.
- Weekly to monthly. The weekly meeting tracks the scorecard and the priorities for the quarter. Patterns that persist for three or four weeks become topics for the monthly business review.
- Monthly to quarterly. The monthly review shows which initiatives are behind and why. That becomes the input for the quarterly business review, where priorities are reset.
- Quarterly to annual. Four quarterly reviews give the leadership team an honest record of what the strategy actually produced, which is the starting point for the annual cycle.
Decisions flow the other way. The annual plan defines the priorities for each quarter, the quarter defines what the weekly meeting tracks, and the weekly meeting defines what teams work on.
A meeting that produces nothing the next meeting uses is a conversation, not a routine.
Designing it for a company of twenty to three hundred people
The stack is the same at every size. What changes is how many layers it runs through and how formal it needs to be.
| Size | What the cadence looks like | The usual gap |
|---|---|---|
| 20 to 60 people | One leadership meeting a week, a monthly numbers review and a quarterly planning day. Teams run their own short check-ins. | The founder runs everything informally, so nothing survives a busy month |
| 60 to 150 people | The weekly leadership meeting is separate from team meetings. Monthly reviews include initiative owners. Quarterly planning involves the next layer of managers. | Middle managers have no routine of their own and fill the gap with escalations |
| 150 to 300 people | Each function runs its own weekly and monthly routines, aligned to the company calendar. A COO or chief of staff owns the cadence. | Levels drift out of sync, so functions review different numbers on different dates |
In every case, start with the leadership team. A cadence imposed on teams while the leadership team still meets ad hoc does not hold. The weekly leadership meeting is usually the first routine to fix, and our weekly leadership meeting agenda gives you a structure to begin with.
Example: a cadence calendar
The calendar below is fictional and purely illustrative, for a company of around a hundred and twenty people with a leadership team of six.
| When | Routine | Who | Notes |
|---|---|---|---|
| Every working day, 9:00 | Team check-ins | Each operational team | Fifteen minutes, run by the team lead |
| Monday, 10:00 to 11:30 | Weekly leadership meeting | CEO and five directors | Scorecard, quarterly priorities, the three most important issues |
| Tuesday | Functional team meetings | Each director with their team | Monday's decisions passed on to teams |
| Second Thursday of the month | Monthly business review | Leadership team, finance, initiative owners | Closed numbers from the previous month |
| Last two weeks of each quarter | Quarterly planning | Leadership team, then managers | One planning day, one session to cascade |
| October and November | Annual planning | Leadership team and board | Strategy off-site in October, budget in November |
Two details make the difference. The monthly review sits on a fixed day after the accounts close, so the numbers are final when the meeting starts. And team meetings happen the day after the leadership meeting, so decisions reach teams within twenty-four hours rather than drifting.
Behaviours and facilitation
Designing a cadence takes a few days. The behaviours take months. Most cadences fail not because the meetings are badly designed, but because they are badly run.
- Start and end on time. Late starts tell everyone the meeting is optional.
- Prepare before, not during. Numbers and updates are shared in advance, so the meeting is spent on discussion and decisions.
- One facilitator, and not always the CEO. Delegating facilitation lets the CEO take part instead of chairing everything.
- Close every item with an owner and a date. An item that ends with a vague intention to look into it will come back next week unchanged.
- Review last week's commitments first. Checking actions at the start of every meeting is the simplest accountability mechanism there is.
- Protect the dates. Moving the monthly review once for a client meeting is understandable. Doing it every month dismantles the cadence.
Embedding it: the first 90 days
| Weeks | Focus | What good looks like |
|---|---|---|
| 1 to 2 | Design the stack, agree purposes and attendees, put a full year of dates in the calendar | Every member of the leadership team has accepted the recurring meetings |
| 3 to 6 | Run the weekly leadership meeting and the first monthly review in the new format | Meetings start on time, and actions are recorded and reviewed |
| 7 to 10 | Extend to teams: functional weekly meetings, and daily check-ins where useful | Decisions from the leadership meeting reach teams within a day |
| 11 to 13 | Run the first quarterly review, then adjust the cadence itself | Next quarter's priorities are set in the room, not afterwards |
At the end of the first quarter, review the cadence itself. Some meetings will be too long, some attendees unnecessary, some outputs unused. Adjust it once, deliberately, then leave it alone for another quarter. Changing it every few weeks is another way of not having one.
Signs your operating cadence is broken
- The same issues appear on the agenda week after week.
- Leadership meetings are mostly status updates, and the real decisions happen afterwards in smaller groups.
- Different directors bring different numbers to the same meeting.
- The quarterly plan is written in January and not mentioned again until April.
- Meetings are cancelled or moved when things get busy, which is exactly when they are needed.
- Everything important still goes through the founder.
Fixing this is what our Leadership Operating System work does: designing the cadence with the leadership team, facilitating the first cycles and handing it over once it runs on its own. The cadence sits inside a wider business operating system, alongside priorities, KPIs and accountability.
Next step
If your leadership team spends its time in meetings but the company still feels hard to steer, start by looking at the cadence you actually have. Book an Operating Assessment and we will map your current routines against what the business needs.
Sources and references
References for the concepts and rules discussed. The models and implementation recommendations in this article are our practical application.

Co-founder — Leadership, People & Change
Ana Reis
Works with leadership teams until new ways of managing are used every week, not just agreed in a workshop.
More from Ana



