Cadence and synchronization are complementary mechanisms for coordinating work in decentralized-control systems. Cadence provides a regular heartbeat that reduces coordination overhead; synchronization aligns cross-functional work at defined integration points. Together, they enable decentralized teams to work independently without diverging. Principle numbers S1-S12 in principles-of-product-development-flow.
Cadence: Reducing Coordination Transaction Costs
Regular cadence converts variable-cost coordination into fixed-cost coordination. Without cadence, each coordination event (a planning meeting, a design review, a release decision) must be scheduled, convened, and structured ad hoc — each instance incurs the full transaction cost of coordination. With regular cadence, the overhead is paid once (establishing the rhythm) and subsequent events run at low marginal cost.
This is a u-curve-optimization argument applied to coordination frequency. Too little cadence means coordination events are rare and expensive; too much cadence means the coordination itself consumes significant throughput. The optimal cadence is the one that minimizes total coordination cost — frequent enough to catch divergence early, infrequent enough to leave time for productive work between synchronization points.
Reinertsen notes that cadence also creates predictable integration points, which reduces the variance of coordination timing. Predictable timing allows teams to plan their work around known synchronization events rather than being interrupted by unpredictable coordination demands.
Synchronization: Aligning Cross-Functional Dependencies
Synchronization is the practice of aligning the timing of interdependent work so that handoffs and integrations occur at defined moments rather than asynchronously. Its economic value is in reducing the holding cost of partially completed work waiting for a dependency.
In product development, cross-functional dependencies — design waiting for market research, engineering waiting for UX specifications, test waiting for implementation — create queues. If these handoffs are uncoordinated, the receiving team may wait idle or switch to other work (increasing context-switching costs). Synchronization reduces these queues by ensuring that dependent work arrives at the same time from multiple sources.
This connects to batch-size-reduction: synchronization enables smaller batches to flow coherently across functional boundaries, because the integration points are known in advance.
Relationship to Decentralized Control
decentralized-control requires a coordination mechanism to prevent decentralized decisions from diverging. Cadence and synchronization provide that mechanism without reimposing centralized authority. Teams make autonomous decisions within each cadence interval; at the synchronization point, they integrate and align. The cadence replaces the hierarchy as the coordination structure.
This is structurally analogous to market mechanisms: prices synchronize decentralized economic decisions without requiring central planning. Regular cadence synchronizes decentralized product development decisions without requiring central approval of each decision.
Connection to Agile Practices
The sprint cadence in Scrum is an instance of this principle — a fixed time box that creates regular integration and review points. Reinertsen's framework provides the economic justification for why fixed cadences are preferable to variable-length iterations: the transaction cost reduction and variance reduction of regular cadence outweigh the flexibility lost by fixing the rhythm.