What Belongs in a Weekly, a Monthly, and a Quarterly Review

Most companies build their operating cadence by picking frequencies and filling them with whatever needs discussing that week. A leadership team decides it will meet weekly, review numbers monthly, and plan quarterly, and then each forum inherits whatever the last one did not finish. The quarterly review opens with three carried-over items from last month. The weekly stand-up spends its first twenty minutes on a trend that belongs in the monthly. Nobody designed this; the tiers simply absorbed whatever spilled over, because nobody had defined what each one was actually for.

The frequency was never the design decision that mattered. What separates a weekly review from a quarterly one is not how often the room convenes, it is the class of change each room is built to notice and the class of decision it is allowed to make. Confuse the two and a company ends up with three meetings that all do the same thing at different volumes, rather than three instruments tuned to three different signals.

The tiers differ in resolution, not in frequency

A cadence tier is a claim about how much change has to accumulate before it is worth discussing at that level. A weekly forum should react to a blocker before it costs a week. A quarterly forum should only react to a pattern that has held for a quarter, because anything shorter than that is noise the weekly tier was supposed to have already absorbed.

The weekly forum is the only tier close enough to the work to see a blocker while it is still cheap to remove. Its material is this week's execution: what shipped, what is stuck, what one team is waiting on from another, and which of last week's commitments did not hold. None of that requires history. A blocker is legible on its own, in the room, from the person who hit it.

The mistake that recurs across weekly reviews is importing material that needs a trend to mean anything. A single week of a metric moving is not a signal; it is one data point in a series the weekly forum has no mandate to interpret, because interpreting it correctly requires the several weeks the monthly tier exists to hold. When a weekly meeting debates whether a dip is real, it is doing the monthly tier's job with a third of the evidence, and the debate resolves by personality rather than pattern.

What a weekly forum should carry, and nothing more:

• Blockers that are costing execution right now, named by the person who owns the work.
• Commitments made last week, checked against what actually happened, without re-litigating why.
• Cross-team dependencies that will slip if nobody notices this week.

The weekly tier is disposable by design

Nothing decided at the weekly tier should require a memory longer than a week. If a weekly decision needs to be defended a month later, it was not a weekly-scale decision to begin with, and the forum that made it exceeded its resolution. Below the weekly there is sometimes a daily, and it is the tier most often added without cause; whether a daily is earned turns on the shape of the work rather than on preference.

The monthly review exists because a single week cannot tell a company whether something is a blip or a pattern, and a quarter is too slow to catch a pattern before it compounds. Its material is the aggregate of four or five weeks: a metric's actual trajectory rather than its latest print, a resourcing question that has recurred often enough to stop being anecdotal, a risk that has shown up in three consecutive weekly reviews under three different names.

The monthly tier's job is consolidation, not adjudication of every open item beneath it. A monthly review that walks through each of the past month's weekly issues one at a time is not consolidating anything; it is re-running four weekly meetings back to back and calling the result strategic. The useful monthly review asks a narrower question of each thread: has this recurred enough, across enough weeks, to now be a pattern rather than an incident, and if so, does it require resourcing that only this tier can approve.

This is also the tier where most operating cadences quietly fail, because it is the hardest one to run with discipline. The weekly tier disciplines itself by running out of time. The quarterly tier disciplines itself by being rare enough that people prepare. The monthly tier has neither constraint, which is why it is the forum most likely to expand until it is doing both of its neighbors' jobs badly.

A quarter is the shortest interval in which a strategic bet can produce evidence honest enough to judge it by. Anything decided about strategy on a shorter clock is a reaction to noise the monthly tier should have filtered; anything left undecided past a quarter has usually calcified into a default nobody chose, protected by nothing more than the fact that no forum was ever scheduled to revisit it.

The material that belongs at the quarterly tier is narrow: which bets get funded for the next quarter, which get cut, and which priorities from the current list get demoted because a new pattern from the monthly tier outranks them. This is where kill decisions belong, and where most companies are worst at making them, because a quarterly forum staffed by the people who championed last quarter's bets is structurally reluctant to end them.

The tier that is rare enough to matter is also rare enough to avoid, and avoiding it is how a strategy survives past the quarter that should have ended it.

The failure runs in both directions. Run quarterly-scale decisions at monthly speed and the strategy whiplashes, changing direction faster than any bet can produce real evidence. Leave a decision that needed quarterly review sitting inside a monthly forum that never has the mandate to end anything, and it survives by inertia rather than by merit, indefinitely.

Naming which tier a piece of material belongs to is not a scheduling exercise; it is a decision about which forum is allowed to change its mind about what, and how much evidence that forum is required to have before it does. Most companies never make that assignment explicitly, which is why the same unresolved question can be raised at three different cadences in the same month without anyone noticing it is the same question, asked at the wrong resolution each time.

This is a different diagnosis from the operating cadence question itself, which is the broader claim that the calendar sets the ceiling on how fast a company can notice something and act on it. Getting the tiers right does not change how often the company meets; it changes what each meeting is trusted to decide, which is usually the smaller fix and the one that holds. It is also the piece most cadence redesigns skip, because building a cadence that scales starts from decision rights, and resolution by tier is the part of that inventory most often left implicit.

Naming the tier is the cheapest fix available

This is where the diagnosis happens in consulting engagements: not a new meeting schedule, but an audit of what each existing forum has actually been deciding against what it was built to hold, and a short list of items moved to the tier that can resolve them. It sits inside the wider argument under operating cadence — that the calendar a company runs is either a designed instrument or an inherited accident, and almost nobody has checked which.