The Role of Cadence (Still Essential)

Cadence does not disappear in a flow-based governance model.

Regular, predictable cadence is intentionally preserved because it:

  • Reduces coordination complexity

  • Creates a shared operational rhythm

  • Lowers the cognitive cost of synchronization

  • Provides psychological safety through predictability

In the language of Don Reinertsen, cadence is a complexity-reduction mechanism, not a planning artifact.

Cadence is a powerful mechanism for reducing complexity. By making events predictable, we simplify coordination and decision-making—even in highly variable systems.
— Don Reinertsen, Principles of Product Development Flow (paraphrased)

What changes in a flow-based system is not whether meetings occur, but what determines their content and duration.

What Cadence Provides

Cadence ensures there is always:

  • A standing forum for decision-making

  • A predictable rhythm for alignment

  • A reliable fallback for human coordination

Meetings still occur on cadence, regardless of whether any flow triggers have fired.

What Triggers Control

Flow triggers determine:

  • Whether decisions are required

  • Which topics deserve attention

  • How long the meeting needs to last

If no triggers have fired:

  • The agenda is empty

  • The meeting ends quickly

  • No decisions are forced

If multiple triggers have fired:

  • The agenda is explicit

  • The meeting is decision-focused

  • Time is spent only where risk or opportunity exists

In other words:

Cadence schedules the meeting.
Triggers determine the work of the meeting.

This is the critical distinction.

Calendar-based governance uses cadence to manufacture urgency.
Flow-based governance uses cadence to absorb variability.

Urgency comes from the system—not the schedule.

  • The standup always happens

  • Only aging work gets airtime

  • Scales from Team Kanban/Scrum → ART → Portfolio

Same pattern. Different altitude.

Scroll to Top