Weekly: control execution and exceptions
The weekly cadence monitors leading indicators, delivery milestones, customer exceptions, operational risks, and cross-functional commitments. It should resolve near-term tradeoffs and escalate blockers while there is still time to change the result.
Use a compact scorecard and action log. Avoid reopening strategy unless new evidence breaks a core assumption.
Monthly: explain business performance
The monthly review connects financial and customer outcomes to operational drivers. It examines cohort trends, plan variance, resource use, forecast implications, and whether current initiatives are producing evidence.
Monthly decisions may include reallocating budget, changing a process, stopping an initiative, revising the forecast, or commissioning deeper analysis.
- Outcome, driver, and guardrail trends
- Budget and forecast variance
- Customer and market learning
- Initiative evidence and resource tradeoffs
Quarterly: choose priorities and allocation
Quarterly planning revisits strategy, assumptions, targets, capacity, and major bets. It should make explicit what the organization will stop, continue, start, and fund. A quarterly forum that only rolls forward last quarter’s projects is not planning.
Use scenarios and capacity constraints. Tie every priority to an owner, intended outcome, leading evidence, guardrails, and review forum.
Connect the system
Use a shared metric dictionary, decision log, initiative portfolio, and owner model across all cadences. Weekly evidence should roll into monthly interpretation; monthly learning should inform quarterly allocation.
Define escalation rules so urgent risk moves faster than the calendar. At the same time, protect teams from duplicate forums that ask for the same information in different slides.