operating cadence
The recurring rhythm of meetings, reviews, and decision checkpoints that a team or organization uses to coordinate work and make decisions. Typical cadences include daily standups, weekly team syncs, monthly business reviews (MBRs), and quarterly business reviews (QBRs). A well-designed cadence surfaces problems early, aligns the team without over-meeting, and creates predictable decision windows.
When you'd see it: Leadership team design, new manager onboarding, scaling transitions, OKR review structure.
Why it matters: The absence of a cadence creates coordination overhead (random ad-hoc meetings) or coordination gaps (things slip because no one checks). Cadence design is operating system design.
Common mistakes: Building a cadence that optimizes for information sharing but has no decision-making. Meetings that don't produce decisions or actions are ceremony, not coordination.
Study this in BizTech Primer →