The Operating Cadence
Why weekly beats monthly. The case for the weekly rhythm.
This whole series assumes a weekly cadence, and this piece is where I defend the assumption — in both directions. Monthly is too slow for the problems a real business has. Daily is too fast for the trust a real leadership team needs. The week is the natural unit of leadership accountability, and the honest version of that argument starts with what life actually looks like without the rhythm — because it isn't a tidy monthly review.
Life before the cadence: Slack chaos
When people weigh "weekly vs. monthly," they imagine choosing between two orderly rhythms. That's not the real choice. Before we implemented a framework, our company didn't run on a monthly cadence — it ran on chaos. A problem would arise, and there might be a meeting about it, or there might not. There might be one meeting, or two, with some of the players in the room and not others. Slack threads everywhere. Pockets of people who knew about an issue while others had no idea it existed. And through all of it, very little actual leadership-team problem-solving — just a lot of motion. It was super inefficient, and it was dysfunctional, until EOS gave us the discipline of the weekly meeting, the QBRs, and annual planning.
That's what the weekly cadence actually replaces for most companies. Not a calm monthly review — a reactive scramble where information lives in fragments and whether the right people ever get in a room together is a matter of luck. The first thing the weekly rhythm buys you isn't speed. It's the guarantee that the whole leadership team learns about a problem at the same time, in the same room, with a place to put it.
Knowing sooner is the whole game
Once the rhythm exists, the argument for weekly over monthly is almost embarrassingly simple: everyone knows sooner. The churn signal forming in the scorecard. The large account that might not renew. The app speed slowing down. The sales pipeline quietly getting smaller. Run the weekly meeting right, and every one of those surfaces inside seven days of becoming visible in the numbers — with the whole team looking at it and an issues list to catch it. On a monthly rhythm, each one gets up to thirty days of free compounding before anyone is forced to look.
The honest caveat, which I've made elsewhere in this series: not every number is a weekly number. Month-end financials read weekly are noise dressed up as precision, and they belong on a monthly or quarterly review. The weekly cadence isn't a claim that everything moves in seven-day increments. It's a claim that the numbers that run the business — the ones that can go red and cost you — deserve thirteen looks a quarter, not three.
"Too many meetings" — the objection, inverted
The pushback I hear most when coaching teams on this is some version of "we already have too many meetings." My answer to a founder is simple: the L10 will replace many, if not all, of the others. It's not an addition to your meeting load — it's a consolidation of it. All the ad hoc problem meetings, the one-off syncs, the two-meetings-about-the-same-issue-with-different-people — that's the Slack chaos I described above, and it's a far bigger tax on the calendar than one structured ninety minutes. With everyone in the room, on a standing agenda, it's just way more efficient. The weekly meeting isn't the meeting problem. It's the meeting solution.
The week is the unit of trust
Defending weekly against monthly is the easy half. The other direction matters too: why not more frequency? Daily standups at the leadership level always felt to me like an excuse to create some fake urgency around the business — and worse, they send a signal: we're going to talk every day so I can make sure you do what you say. There's a level of mistrust baked into a daily check-in among senior leaders. As I said in the failures piece, standups have their place where a high level of coordination is genuinely needed — a product feature launch, an engineering problem. But for a leadership team executing, they don't work.
At this level, senior leaders should be given the time to execute — a week — against their goals, and be held accountable at that level. That's the real logic of the rhythm: monthly is too slow to catch problems, daily is too short to trust people, and the week is the interval where a senior leader can do meaningful work and stand in front of the team to account for it. The cadence is an accountability system and a trust system at the same time, and the week is where the two meet.
People sometimes ask whether the weekly rhythm is a stage thing — right for a company our size, outgrown later. My opinion after sixteen years: weekly is right at every stage. The size of the company changes what's on the scorecard and who's in the room. It doesn't change the fact that a leadership team that isn't making decisions together every week isn't really operating the business — it's reacting to it.
Read next
More on the operating cadence.
Know sooner. Act sooner.
Upbeat puts the weekly signal in front of your leadership team automatically — churn forming, pipeline shrinking, a renewal at risk — synced from Stripe, HubSpot, QuickBooks, and Linear, so nobody finds out a month late.
Become a design partner →