Most conversations about reporting are about content: what to measure, which KPIs matter, what the dashboard should show. Far fewer are about timing — and timing is where a surprising amount of operational dysfunction lives.
A metric has a natural speed. Some things move daily. Some move over a quarter. When your review rhythm doesn't match the speed of the thing you're reviewing, the review stops being useful in one of two ways.
Reviewing too slowly
A metric that moves weekly, reviewed monthly, means you find out about a problem three weeks after you could have acted on it. By then the cause is unclear and the conversation becomes archaeology — reconstructing what happened rather than deciding what to do.
The clearest example is anything connected to a pipeline or a funnel. Conversion rates shift week to week. A monthly review tells you the month was bad. A weekly one tells you which week it broke, which is almost always enough to find out why.
Reviewing too quickly
The opposite failure is less obvious but just as costly. Metrics that move slowly — retention cohorts, average contract value, team productivity — produce mostly noise when reviewed weekly.
The damage here is reactive decision-making. People respond to the noise. A bad week triggers a change in approach, which hasn't had time to show results before the next bad week triggers another change. Nothing gets a fair test.
How to set the cadence
A simple rule: review a metric at the fastest interval at which the number can meaningfully change, and no faster.
If a number can't plausibly move in a week, don't look at it weekly — or at least don't make decisions on it weekly. If a number can swing significantly in a week and you only see it monthly, you've chosen to be late.
Three questions make this concrete for any metric you track: how fast can this realistically change? What would we actually do differently if it moved? How long does an action on this take to show up in the number?
That last one is the one people skip. If a change takes six weeks to show results, reviewing weekly means five reviews where the honest answer is "too early to say" — and the risk that someone acts anyway.
What good looks like in practice
Most companies end up with something like three layers.
A short weekly review of the handful of numbers that move fast and drive immediate action — pipeline, delivery, anything with a service level attached. Fifteen minutes, same people, same format.
A monthly review of performance against the plan, where the conversation is about variance and what's being done about it.
A quarterly review of the slow numbers — retention, unit economics, structural health — where the point is to spot direction, not react to movement.
The real symptom
If your management meetings feel both too frequent and not frequent enough, that's usually not a meeting problem. It's a cadence mismatch: you're discussing slow metrics too often and fast ones too rarely, in the same room, at the same time.
Separating them by speed usually does more for decision quality than adding any new metric.