There’s a standard set of review rhythms that every company over a certain size ends up with. Two of them are easy to recognize: a weekly review where the team looks at the current week’s work, and a quarterly review where leadership sets or resets direction. In between sits a monthly operational review, where the company looks at the shape of the last few weeks and decides what to change before the next quarter.
Most companies past 100 people have the weekly and the quarterly, and have somehow misplaced the monthly. The weekly is an operational habit that nobody has to be convinced of, because it’s how the work gets scheduled. The quarterly is a strategic event that nobody skips, because the board or the leadership team has put it on the calendar. The monthly sits in the gap between them, owned by nobody by default, and it’s the rhythm that gets quietly dropped when the calendar fills up.
The cost of dropping the monthly doesn’t show up in the month it happens. It shows up at the end of the quarter, when the leadership sits down to review the last three months and discovers that the last three months blurred into one long present. The weekly cadence kept the work moving, but the weekly cadence doesn’t carry enough altitude to notice that two teams have drifted toward the same problem, or that a metric has been sliding for six weeks in a way that’s invisible at the weekly level. The quarterly is the moment those patterns get noticed, which is eight weeks too late to do anything about them in the quarter they belong to.
The three rhythms each do a specific job, and the jobs don’t substitute for each other. The weekly deals in execution and the quarterly in direction. The monthly is about the shape in between, which is where the signal sits that the weekly is too close to read and the quarterly is too far to catch in time. Without the monthly, the weekly keeps running on inertia and the quarterly does emergency surgery on problems that should have been caught earlier.
The reason the monthly gets dropped is that it’s the rhythm with the weakest forcing function. The weekly forces itself because the work has to be scheduled, and the quarterly forces itself because the board meeting is on the calendar. The monthly has nothing external pushing it, which means it has to be pushed by the leadership’s own discipline. Most leadership teams will honor the rhythms that have external forcing and let the internal one slide, because nothing immediately bad happens when they do.
Bringing the monthly back comes down to deciding what that meeting reads. Adding another meeting to the calendar does nothing on its own, and a monthly operational review that looks at the same things the weekly looks at, only in aggregate, is a waste. The monthly should read what the weekly can’t: trends in metrics that move slowly, patterns across customer signals, the health of handoffs between teams, the state of initiatives that were supposed to be tracking toward a quarterly outcome. The agenda is different from the weekly because the altitude is different, and if the altitude isn’t different the meeting won’t be worth holding.
One working shape for the monthly is an hour that the leadership team spends on trend reads and signals that sit between teams, with the specific brief of finding what isn’t visible in any single week. Each leader comes with a paragraph on what their area has looked like across the month rather than this week’s numbers. The group’s job is to look at those reads together and spot the thing that isn’t in any single paragraph, which is usually where the quarter is going off course.
When the monthly starts running, the quarterly changes shape. A quarterly that’s preceded by three monthlies becomes a review of decisions already in motion. The same meeting without the monthlies becomes a scramble to contain problems that have been accumulating. The leadership walks in knowing what the quarter did, because they read the quarter a month at a time while it was happening.
Put the monthly on the calendar the way the board meeting is on the calendar, with the same insistence that it happens even when the week is busy. The company without it will keep solving at the weekly altitude and reacting at the quarterly one, and will keep being surprised by patterns that were visible four weeks earlier to anyone who looked.