Shared Coordination Board¶

Coordination tool — instantiates Distributed Coordination Architecture

A single shared surface where every actor reads the same live picture — outcome, state, commitments, dependencies, capacity, exceptions — each field owned, dated, and confidence-tagged.

A Shared Coordination Board is the common operating picture of a coordination architecture: one surface every actor reads, and updates, so that independently controlled parties act on the same facts. Its defining move is making state mutually visible with discipline — each field carries an owner, a freshness stamp, a confidence level, and an access rule — so the board is a trustworthy shared situation model rather than a bulletin wall. It answers one question well: what is true right now that all of us need to see? It is not a router that pushes changes to you, and not a ledger that remembers every commitment's history; it is the live, at-a-glance surface where the current state of the joint effort is legible to everyone at once.

Example¶

A container terminal runs on a dozen parties who each own a different system — vessel planners, stevedores, crane operators, the yard, trucking, customs. The board pulls the coordination-relevant fields onto one surface: berth assignments, crane up/down status, yard capacity, which containers are on hold or released, and the current exceptions (a refrigerated box losing power on row 12). Every field has an owner and a timestamp. When a crane fails, its status flips on the board and everyone downstream sees it and replans — trucks reroute to open lanes instead of queuing at a dead one — without a phone tree carrying the same news twelve times. The whole yard, for once, is reading a single picture.

How it works¶

Show only decision-relevant fields. The board's standard is that every field supports a named choice, safeguard, or dependency; everything else is noise that ages into distrust.
Attach ownership and freshness to each field — who is authoritative for it, when it was last true, and how confident that value is — so readers know what they can lean on.
Surface exceptions and changed commitments prominently, because a changed promise or a raised flag matters more to coordination than steady raw state.
Be a shared read/write surface, not a firehose. It is pulled and glanced at, not pushed; it holds the state, not the delivery of every event.

Tuning parameters¶

Field scope — how many fields are shared. Too few leaves actors blind; too many overloads the surface and lets it go stale, which is worse than blindness.
Freshness model — real-time, periodic, or manual updates. Fresher is more trustworthy but demands instrumentation and risks flooding the board with churn.
Ownership granularity — one accountable owner per field versus shared ownership. Clear single ownership is what keeps a field believable.
Access and visibility — who may see or edit each field, honoring privacy and confidentiality boundaries between parties.
Signal salience — how loudly exceptions and stale fields announce themselves versus blending into the steady state.

When it helps, and when it misleads¶

Its strength is that it kills the everyone-has-a-different-picture failure and makes stale or contradictory state visible instead of silently diverging across a dozen systems. Its central failure mode is the board nobody updates, which becomes confidently wrong — a field showing green long after it went red is more dangerous than an empty cell. Its classic misuse is treating the board as an authority: it reveals a conflict between two parties' commitments but cannot resolve it, and mistaking visibility for resolution leaves the conflict to fester in plain sight. A related trap is padding it with activity fields — message counts, attendance — that can rise precisely as real coordination decays. The discipline that guards against this is to make every field earn its place with a named decision and to enforce owner-plus-freshness, so the board stays a picture people trust enough to act on.^[1]

How it implements the components¶

A Shared Coordination Board fills the shared-visibility components — the parts a common surface can own:

shared_state_and_situation_model — the board is the minimum shared situation model: authoritative fields with ownership, freshness, provenance, uncertainty, and access, each tied to a decision.
information_and_signal_policy — it operationalizes the display side of the signal policy: which signals are surfaced, to whom, at what confidence, and how prominently exceptions announce themselves.

It does not push events to subscribers or guarantee their delivery (that is the Event-Driven Coordination Channel), keep the durable, addressable history of commitments and dependencies (that is the Commitment and Dependency Register), or resolve the conflicts it makes visible (that is the Exception and Escalation Protocol and the Coordination Decision Rights and Autonomy Matrix).

Instantiates: Distributed Coordination Architecture — the board is the shared situational surface the rest of the architecture reads from.
Consumes: draws commitment and dependency values from the Commitment and Dependency Register and change events from the Event-Driven Coordination Channel, and renders them as one legible picture.
Sibling mechanisms: Exception and Escalation Protocol · Synchronization Checkpoint · Event-Driven Coordination Channel · Commitment and Dependency Register · Interface Control Document or Service Contract · Coordination Health Review

Notes¶

A board and an event channel are complements, not substitutes. The board is the pull — the at-a-glance state you consult when you choose to look; the channel is the push — the delivery that reaches an actor whose decision cannot wait for them to glance. Relying on the board alone means a critical change sits unseen until someone happens to check.

References¶

[1] A common operating picture (COP) — one shared display of the situation that every party reads from — is a standard concept in military and emergency-management coordination. Its defining discipline is the same one above: a COP is only as useful as its fields are current and owned, which is why a stale board is treated as a hazard rather than a convenience. ↩