Coordination Protocol¶
Protocol — instantiates Coupling Calibration
A durable set of rules for how coupled people or teams hand off, approve, and update — naming who owns each coordination point and where a stalled case escalates.
Coordination Protocol governs the dependencies that people carry, not the ones a machine mediates. Where a buffer or a contract test operates on a technical boundary, a coordination protocol addresses a coupling between humans or teams by making the recurring interaction explicit: it names who is accountable for each handoff and it defines where a case goes when the normal flow stalls. Its defining move is assigning accountability and escalation — turning a diffuse "everyone is sort of responsible" into "this role owns this handoff, and this is the path up when it breaks." It is the org-flavored answer to a coupling that lives in meetings, emails, and handoffs rather than in a schema.
Example¶
A departing aircraft has roughly forty minutes on the ground, during which cleaning, catering, fueling, baggage, and boarding all have to converge. When each vendor worked to its own clock, a fuel truck arriving ten minutes late would silently eat the whole margin, the flight would push back late, and every team would blame the others — because no one owned the convergence. The airline institutes a turnaround protocol. A named Turnaround Coordinator owns the sequence for each aircraft; every task has a required start-by point relative to departure; and if any task slips past its start-by, the coordinator triggers a defined escalation — hold the swap, notify the duty manager, or re-sequence the remaining tasks. The dependency that used to be tacit and finger-pointed becomes an owned, rule-governed handoff with an unambiguous answer to "who decides when it goes wrong." Late pushbacks from uncoordinated slippage drop sharply.
How it works¶
- Enumerate the recurring handoffs, approvals, and updates that cross the boundary between the coupled parties.
- Assign an accountable owner to each — a role, not a hope — so every coordination point has a single responsible party.
- Define what counts as an exception and the escalation route it takes: who is notified, who can override, and how far up it goes.
- Publish the rules so the parties coordinate by a shared script rather than by improvisation.
Tuning parameters¶
- Formality — a lightweight checklist versus heavy sign-offs. More formality reduces ambiguity but adds overhead and can smother judgment.
- Ownership concentration — a single coordinator versus shared or rotating ownership. Single is unambiguous but a bottleneck and a single point of failure; shared spreads load but blurs the "one throat to choke."
- Escalation eagerness — how quickly an exception climbs. Eager catches trouble early but cries wolf and erodes the local autonomy the archetype is meant to preserve.
- Decision-rights breadth — how much the owner may decide alone versus must consult. Broad rights are fast but risky; narrow rights are safe but slow.
- Enforcement strength — advisory norm versus mandatory gate. A gate guarantees the step happens but tempts people into side channels when it is inconvenient.
When it helps, and when it misleads¶
Its strength is that it makes human dependencies explicit, accountable, and repeatable. By naming an owner it dissolves the finger-pointing that surrounds shared responsibility, and by defining an escalation path it gives failures a pre-agreed route instead of an ad-hoc scramble at the worst moment.
Its failure mode is ossification. A protocol can be followed to the letter while the real coordination quietly moves to side channels — the "interface theatre" of people, where the official handoff is honored on paper and the actual work happens over a back-channel chat. It can also over-tighten: pile on approvals and coordinators until the protocol itself is the bottleneck, the archetype's over-coupling failure in human form. The classic misuse is adding a sign-off to every handoff after one thing goes wrong, permanently taxing the many for the sake of the rare exception. The guard is to keep tight coordination local, justified, and reviewable, push decision rights close to the work, and prune any step that does not change an outcome — a discipline that maps cleanly onto naming roles with a scheme like RACI so accountability is explicit rather than assumed.[n1]
How it implements the components¶
Coordination Protocol fills the human-accountability side of the archetype — the pair of components that govern a people-carried dependency:
coordination_owner— it names the accountable owner for each handoff, so a dependency has a single responsible role rather than diffuse, shared ownership.exception_escalation_path— it defines what counts as an exception and the route it climbs, so a stalled dependency has a pre-agreed way up and out instead of an improvised scramble.
It governs the human handoff but does not decouple its timing with a buffer (boundary_or_buffer, synchronization_rule — that's Asynchronous Queue or Buffer), nor does it verify that a technical interface still honors its promise (recalibration_monitoring, interface_contract — that's Contract Testing or Integration Monitoring).
Related¶
- Instantiates: Coupling Calibration — it calibrates a dependency carried by people, giving it an owner and an escalation route.
- Sibling mechanisms: Asynchronous Queue or Buffer · Contract Testing or Integration Monitoring · Coupling Review Ritual · Shared-State Reduction · Dependency Inversion · Interface Contract Design · Dependency Mapping Workshop
Editorial Notes¶
Form Classification¶
Form family: Protocol, Workflow & Routine
Rationale: Coordination Protocol operates as a repeatable ordered procedure or handoff sequence that coordinates action because it a durable set of rules for how coupled people or teams hand off, approve, and update — naming who owns each coordination point and where a stalled case escalates.
Independent corroboration: The frozen evidence defines Coordination Protocol as 'A durable set of rules for how coupled people or teams hand off, approve, and update — naming who owns each coordination point and where a stalled case escalates', so its operative form is Protocol, Workflow & Routine.
Review outcome: Independent reviewer agreement; high confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Organization design cohered explicit handoff ownership, update rules, and escalation paths for recurrent dependencies between people or teams.
Review resolution: Both reviewers agree on organizational management. Cybernetic feedback is a useful analogy, but the entry is a human-team agreement about roles, channels, timing, and escalation, so it does not require an additional origin lineage.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
A coordination protocol is the human sibling of an interface contract. Interface Contract Design publishes a stable technical surface so eligible cases engage without renegotiating; a coordination protocol instead assigns accountability and escalation for a dependency that lives among people. They rhyme, but a protocol's load-bearing content is who-owns-it and where-it-escalates, not the declared shape of a payload — which is why they fill different components even when both are called "the way we hand off."
[n1] RACI (Responsible, Accountable, Consulted, Informed) is a standard responsibility-assignment scheme for making coordination roles explicit — in particular ensuring exactly one Accountable party per task, which is the core discipline a coordination protocol enforces. ↩