Weekly / Monthly / Quarterly Reviews
The cadence that keeps the plan honest.
Workflow
Step 1Status Collection
ObjectiveGather the state.
InputData, teams
OutputStatus view
Key activities
Collect status, metrics, issues
Decision points
What is the state?
Tools: DashboardsRoles: Leadership
Success: Collected
Quality gate: Go: complete. Loop back: stale.
Why it matters
- Without a cadence, course-correction is reactive. The rhythm is what turns a plan into a living system.
Best practices
- Weekly: issues + actions. Monthly: trends + decisions. Quarterly: results + strategy.
- Prepare data before the meeting, not during.
- End every review with decisions and owners.
- Capture learnings — the review is also the learning loop.
Common mistakes
- Reviews that are status updates, not decisions.
- No preparation — an hour to read the data aloud.
- No follow-through on action items.
Key questions
- What changed this week that needs a decision now?
- What did we learn that changes the plan?
Agents that drive this
Planning CycleDiagnostic
Tools we use · alternates in [ ]
Metabase[ Looker Studio, Power BI, Grafana ]Notion[ Confluence, Obsidian ]Slack[ Teams, Discord ]