When leaders debate "weekly versus monthly" for their operating rhythm, they picture a choice between two orderly cadences — a crisp weekly meeting or a dignified monthly review. That's not the actual choice, because almost nobody runs a real monthly rhythm. I know because I ran a company without a cadence for years before adopting one, and what we had wasn't monthly anything. It was chaos with a calendar.
What "monthly" actually looks like
Here's the uncadenced company from the inside. A problem surfaces. Maybe there's a meeting about it — maybe two, with different partial casts, reaching different partial conclusions. Threads multiply in chat. Some of the leadership team knows about the issue; some has no idea it exists. Whether the right people ever end up in a room together is a matter of luck and hallway timing. There's plenty of motion and very little actual leadership-team problem-solving. That was my company before we adopted a weekly discipline, and it's the honest baseline for most 20–200 person companies "on a monthly rhythm": the monthly meeting exists, and the other twenty-nine days run on improvisation.
So the first thing a weekly cadence buys you isn't speed. It's a guarantee: the whole leadership team learns about a problem at the same time, in the same room, with a ranked issues list to put it on. No pockets of knowledge. No duplicate meetings. No luck required.
Thirteen looks a quarter, not three
Once a real rhythm exists in both versions, the weekly argument gets almost embarrassingly simple: everyone knows sooner. The key account that's gone quiet. The hiring pipeline that's thinning. The project that slipped a week — then another. The cash position tightening earlier than planned. On a weekly cadence, each of those surfaces within seven days of showing up in the numbers, in front of the whole team. On a monthly cadence, each one gets up to thirty days of free compounding before anyone is forced to look at it together. A quarter gives you thirteen chances to catch a drift or three. That gap — not the meeting itself — is the product.
The honest caveat: not every number is a weekly number. Month-end financials read weekly are noise wearing the costume of precision; they belong in a monthly or quarterly review, and pretending otherwise is how scorecards lose credibility. The weekly claim isn't that everything moves in seven-day increments. It's that the numbers that can quietly cost you — the ones on a real scorecard — deserve thirteen looks, not three. (Reading those thirteen looks without chasing every wobble is its own skill.)
"We have too many meetings" — correct, and backwards
The most common objection to a standing weekly is meeting load, and the objection has it inverted. Count what the weekly replaces: the ad hoc problem meetings, the one-off syncs, the two-meetings-about-the-same-issue with different halves of the team, the thread that becomes a call that becomes another call. That's the chaos tax, and it's far heavier than one structured hour. A disciplined weekly review isn't an addition to the meeting load — it's the consolidation of it. Everything that used to summon a surprise meeting now has a standing time, a standing room, and a standing agenda. The weekly meeting isn't the meeting problem. It's the meeting solution.
Why not daily? Because the week is the unit of trust
Defending weekly against monthly is the easy half. The other boundary matters just as much: why not more frequency? Daily standups have a real place where tight coordination is genuinely needed — a launch week, an incident, a hard engineering push. But as a standing rhythm for a leadership team, a daily check-in carries a message nobody says out loud: we'll talk every day so I can make sure you're doing what you said. That's mistrust with a calendar invite.
Senior leaders need enough runway to actually execute — and then a moment where they stand in front of their peers and account for it. A day is too short to do meaningful work. A month is too long to let a problem run. A week is the interval where real execution and real accountability can coexist: long enough to trust someone with, short enough to catch what's drifting. That's the deeper logic of the cadence — it's an accountability system and a trust system at the same time, and the week is where the two meet.
Does this expire as you grow?
A question I get: is the weekly rhythm a stage thing — right for a 30-person company, outgrown at 300? After sixteen years of running one, my answer is no. Scale changes what's on the scorecard and who's in the room. It doesn't change the underlying fact: a leadership team that isn't looking at its numbers and making decisions together every week isn't operating the business. It's reacting to it, with a lag. If your leadership team can genuinely go two weeks without needing to decide anything together, the cadence isn't what's off.