Meeting Cadence defines deliberate, level‑specific interaction frequencies and nested cycles for effective communication.
Core Question: When and how often do we need which interactions?
Cadence is a deliberate design decision, not convention or imitation. The rhythm is chosen because it fits your specific system's needs — not because "that's how others do it" or "that's how it's always been." Copying another organization's cadence is like wearing someone else's shoes: they might look fine, but they won't fit.
Different Flight Levels need different frequencies. Higher levels interact less often but with longer duration and more strategic focus. Lower levels interact frequently with short, operational focus. Together they form nested cycles: daily standups feed into weekly refinements, weekly demos feed into monthly delivery planning, monthly results inform quarterly strategy reviews. A well-designed cadence creates predictability, muscle memory, and sustainability.
Details
The Rhythm Serves the Work
Cadence makes sure the right people talk about the right thing at the right time, reliably rather than by chance. The rhythm is not a rulebook of fixed frequencies and durations, but a deliberate choice: how often do which people need to align on which topic for work to flow? Higher Flight Levels tend to meet less often, longer, and more strategically, lower levels more often, shorter, and more operationally. That is an orientation, not a schema.
Nested Cycles
The tempos interlock. A daily surfaces a recurring blocker → the weekly refinement clarifies the underlying issue → monthly planning adjusts priorities → the quarterly review evaluates whether the strategy needs to change. This creates a continuous flow of information across all levels.
Cadence Is Just One Trigger
Time is one way to trigger an interaction, events are the other. Cadence creates reliability and rhythm, but it misses urgent situations that can't wait for the next slot. Combining both triggers gives you a system that is stable and responsive (see Pattern Interaction Triggers).
Practical Examples
FL2 Monthly Cadence:
- Week 1: Sync Wed + Retro Fri
- Week 2: Sync Wed + Refinement Fri
- Week 3: Sync Wed + Refinement Fri
- Week 4: Sync Wed + Delivery Planning Fri
- Plus: Improvement Workshop every 3 months
Smells — When to Look Closer
- Copying cadence from other organizations without adapting to your own needs — their rhythm serves their system, not yours
- Same frequency for all Flight Levels — FL3 doesn't need daily standups, FL1 doesn't need quarterly-only reviews
- Over-cadencing: too many meetings, no time for actual work — the rhythm should serve the work, not consume it
- No deliberate cadence at all: ad-hoc meetings create chaos and information gaps
Related Patterns
- Meeting Container defines what happens in each cadence slot
- Interactions Network shows how cadenced meetings connect to each other
- Categories helps check whether the cadence covers all needed time horizons
- Interaction Triggers is the event-based way to trigger an interaction; cadence is its time-based counterpart
Your play!
If you want to use this in your worksystems-design sessions, here is all the material you need.
More about this
These patterns are part of the Flight Levels thinking and design model. If you want to learn more, take the Kick start path to Flight Levels Now!