Weekly
- 1:1s with each direct report
- One team sync focused on decisions, not status
- Async written update from the team lead
Monthly
- Operating review against goals and metrics
- Skip-levels with a rotating subset of the team
- One learning ritual: demo, tech talk, or postmortem read-out
Quarterly
- Planning + goal-setting
- Career growth conversations
- Retrospective on the operating rhythm itself
Common pitfalls
- — Adding meetings without deleting any. Every add needs a delete.
- — Making status the point of the weekly sync. Status is async; the sync is for decisions.
- — Skipping the quarterly review — that's how accidental rhythms creep back in.