Coordination Meeting Cadence¶
Ritual — instantiates Task Interdependence Mapping
Establishes a recurring, dependency-justified forum where the parties to a coupling meet to adjust to each other in real time, rather than discovering the mismatch at handoff.
A Coordination Meeting Cadence is a standing rhythm — a huddle every morning, a sync every Wednesday, a stand-up before each shift — whose whole justification is a specific set of dependencies that need continuous mutual adjustment. Its defining move is temporal repetition: it does not draw the dependency, time it, or contract it, but it creates a reliable recurring moment when the people on both ends of a coupling are in the same conversation and can re-align before their work drifts apart. This is the mechanism for reciprocal and intensive interdependence, where the coupling is too alive for a written handoff to carry it — where what one task should do next depends on what the other just learned. The ritual's value is not the meeting; it is that mismatches surface hourly or daily instead of at the point of failure.
Example¶
A hospital's surgical intensive-care unit runs a fifteen-minute interdisciplinary huddle at 9 a.m. every day, and it exists because the tasks around a critically ill patient are reciprocally coupled: what the pharmacist can dose depends on what the nephrologist decides about dialysis, which depends on the respiratory therapist's read on ventilator weaning, which depends on what the surgeon expects from the wound overnight. None of these can be settled by a handoff form because each one keeps reshaping the others through the day. So the cadence puts all of them at the bedside once a day, each patient walked in turn.
The huddle is where the coupling gets re-synchronized: the nephrologist hears the ventilator plan and moves dialysis to the afternoon; the pharmacist adjusts sedation to match. It is also where each patient's dependency owner is named aloud — "who is chasing the missing culture result?" — and where health signals surface fast: a patient discussed three days running with no progress is a visible flag that a dependency is stuck. When the huddle is skipped, the mismatches don't disappear; they just resurface at 2 a.m. as a page.
How it works¶
The ritual is defined by four choices, all downstream of the dependencies it serves:
- Justify the cadence by the coupling, not the calendar. The frequency is set by how fast the dependencies change — intensive, volatile work earns a daily or per-shift rhythm; stable work does not earn a standing meeting at all.
- Seat the right ends of the edges. Invite exactly the parties to the dependencies in scope, so the room is the coupling, not the org chart.
- Run it as mutual adjustment, not status. The purpose is to let each side change its next move in light of the others' latest state — a status readout is a symptom that the cadence has lost its dependency justification.
- Surface owners and stalls. Name who is on point for each live dependency, and treat any coupling that recurs unresolved as a signal to route it out of the meeting.
This is coordination by mutual adjustment in the classic sense — the mode reserved for exactly the reciprocal interdependence that standardization and plan cannot absorb.[1]
Tuning parameters¶
- Frequency — per-shift, daily, or weekly. Higher frequency catches drift sooner but taxes everyone's attention; match it to the volatility of the coupled work, and retire the slot when the coupling cools.
- Attendance scope — only the parties to the in-scope dependencies versus a broad standing invite. Tight scope keeps the meeting live; broad invites drift it toward status theater.
- Trigger vs. calendar — a fixed recurring slot versus an event-triggered sync fired by a dependency signal. Triggered cadence spends fewer meeting-hours but demands a reliable signal to fire on.
- Time-box — how hard the clock is enforced. A tight box forces mutual adjustment over reporting; a loose one invites the meeting to sprawl into everything.
When it helps, and when it misleads¶
Its strength is that it is the one mechanism that keeps living couplings aligned — the reciprocal and intensive dependencies where the state changes faster than any document can be re-issued. A well-justified cadence turns "we found out at integration" into "we adjusted this morning."
Its failure mode is the default of every recurring meeting: it outlives its justification. The dependencies that once needed a daily sync stabilize, but the slot stays on the calendar and curdles into a status ritual that consumes attention while surfacing nothing — the archetype's coordination-theater failure in its most common form. A classic misuse is copying another team's cadence ("they do daily stand-ups, so should we") with no dependency behind it. The guarding discipline is to tie every standing meeting to the specific dependencies it serves and to kill or thin it the moment those dependencies stabilize.
How it implements the components¶
communication_cadence— it is the rhythm: a recurring, dependency-justified synchronization point sized to how fast the coupled work changes.dependency_health_signal— the recurring forum is where health is read aloud; a coupling that shows up unresolved meeting after meeting is a visible signal that a dependency is failing.dependency_owner_or_contact_path— the standing meeting names, each round, who is on point for each live dependency, giving each coupling a reliable human contact.
It does not route a stuck coupling to higher authority (escalation_path) — that is Escalation Review; and it does not maintain the persistent status surface the meeting glances at (shared_workflow_board) — that is Shared Workflow Board. The cadence is the recurring human sync; those handle out-of-band escalation and always-on display.
Related¶
- Instantiates: Task Interdependence Mapping — this ritual is the standing sync for the archetype's reciprocal and intensive couplings.
- Consumes: Shared Workflow Board — the live status surface the huddle reads from so the meeting spends its minutes on adjustment, not reporting.
- Sibling mechanisms: Escalation Review · Shared Workflow Board · Dependency Mapping Session · Critical Path Analysis · Cross-Functional Workflow Mapping · Workflow Diagram
Editorial Notes¶
Form Classification¶
Form family: Communication, Facilitation & Learning
Rationale: Coordination Meeting Cadence operates as a designed message, facilitated interaction, ritual, or learning activity that changes shared understanding because it establishes a recurring, dependency-justified forum where the parties to a coupling meet to adjust to each other in real time, rather than discovering the mismatch at handoff.
Independent corroboration: The frozen evidence defines Coordination Meeting Cadence as 'Establishes a recurring, dependency-justified forum where the parties to a coupling meet to adjust to each other in real time, rather than discovering the mismatch at handoff', so its operative form is Communication, Facilitation & Learning.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Management practice cohered recurring coordination meetings as a response to reciprocal interdependence requiring frequent mutual adjustment.
Review resolution: Both reviewers identify organizational management as primary. Software teams are an important application of recurring coordination meetings, but the cadence predates and exceeds software practice and need not be treated as a separate origin lineage.
Review outcome: Reconciled after independent review; high confidence.
References¶
[1] James D. Thompson, in Organizations in Action (1967), classified interdependence as pooled, sequential, and reciprocal, and matched each to a coordination mode: standardization for pooled, plan for sequential, and mutual adjustment for reciprocal. A standing coordination meeting is the everyday instantiation of mutual adjustment — reserved, on Thompson's logic, for the tightly coupled work the cheaper modes cannot carry. registry ↩