Operating reviews work best when they sit inside a cadence, not when one heroic meeting tries to do everything.
The weekly layer should stay close to the work. It catches execution drift: missed commitments, blockers, customer issues, incidents, funnel movement, hiring slippage, support load, product risk. Keep it lightweight. The point is early signal, not executive theater.
The monthly operating review should look across the signal and ask what it means. Are we still on the right plan? Where is variance persistent? Which risks need leadership tradeoffs? Which decisions are stuck because the owner lacks authority?
Quarterly calibration asks a different question: was the plan itself right? Did assumptions hold? Did we allocate resources correctly? Did the cadence surface problems early enough? What needs to change in goals, capacity, sequencing, or standards?
Decision forums sit beside this cadence. Some decisions need a smaller group, deeper context, or a written memo. The operating review should identify those decisions and route them cleanly. It should not turn every issue into a group debate.
The common failure is making one meeting carry all of this. Weekly reviews become miniature QBRs. QBRs become bloated status festivals. Decision forums become vague discussion slots. Everyone feels busy and the company gets slower.
A clean cadence has handoffs. Weekly signal feeds the operating review. The review escalates decisions and updates the decision log. Quarterly calibration changes the plan and the cadence. Decision forums send decisions back so the review record shows what changed.
The cadence is working when people can answer four questions quickly: where is the signal captured, where is meaning processed, where are tradeoffs decided, and where is follow-through checked? If those answers are unclear, the review is only where the confusion shows up.
