Skip to content

Liaison or Architecture Forum

Boundary-spanning role or standing forum — instantiates Organization–Artifact Topology Alignment

A standing person or cross-team body that carries the coordination a missing communication channel would otherwise drop, keeping a seam that must stay coupled talking on a regular cadence.

Sometimes the right fix for a mismatched seam is not to move a boundary but to staff the channel that should cross it. Liaison or Architecture Forum is that fix made durable: a named liaison, or a small standing forum of the teams on either side of a boundary, whose job is to carry the coordination the org chart fails to provide. Its defining move is to institutionalize a communication edge — turning coordination that would otherwise depend on two people happening to bump into each other into a role with a mandate and a recurring meeting. It does not redraw the topology; it adds the missing line to it, and keeps that line alive through a regular cadence so the seam does not silently drift back apart.

Example

At a car manufacturer, the infotainment software team and the vehicle-platform team own components that must interlock — the touchscreen has to speak to the low-level vehicle bus — yet they sit in different engineering directorates on different release rhythms, and every integration milestone turns into a scramble. Rather than merge the teams or rewrite the interface, the program stands up an architecture forum: two named architects, one from each side, who meet every second week, hold the shared understanding of how the boundary is supposed to work, and are the first call when either side plans a change that could cross it. The forum doesn't own any code and doesn't decide the architecture by fiat; it carries the conversation that the reporting structure drops. Within a couple of release cycles the milestone scrambles fade, because the coordination now happens continuously in the forum instead of erupting all at once at integration.

How it works

The distinctive move is to make a boundary's coordination someone's standing job, not an accident:

  • Name the span. Assign a specific person or a small paired forum to a specific seam, with an explicit mandate to coordinate across it — not a vague "work together."
  • Hold the shared model. The liaison or forum keeps the living understanding of how the boundary is meant to behave, so neither side has to reconstruct it from scratch when it plans a change.
  • Run a cadence. Meet on a fixed rhythm and review whether the seam is drifting — new couplings creeping in, agreements going stale — so coordination is continuous rather than crisis-driven.

Tuning parameters

  • Person vs. forum — a single liaison is cheap and fast but a bottleneck and a bus-factor risk; a standing forum is more robust but heavier and slower to convene.
  • Cadence frequency — how often the forum meets. Too rare and drift accumulates between sessions; too frequent and it becomes a standing tax that outlives the need.
  • Mandate strength — advisory (surfaces issues) versus empowered (can hold a change until the seam is addressed). Stronger mandate coordinates harder but starts to shade into a governance board.
  • Span breadth — one seam per liaison versus one forum covering several related boundaries. Broader spans economize on meetings but dilute attention.
  • Sunset condition — whether the role is permanent or scheduled to dissolve once the boundary is refactored away or stabilizes into a clean contract.

When it helps, and when it misleads

Its strength is that it fixes a mismatch without the cost and risk of moving a boundary — when a seam genuinely must stay coupled, the cheapest honest answer is to staff the crossing. Organizational research on boundary-spanning roles finds that a few well-placed translators carry a disproportionate share of the information that actually crosses between two groups; the liaison institutionalizes that role instead of leaving it to luck.[1]

It misleads when it becomes a permanent bandage over a boundary that should have been refactored — the forum quietly absorbs the pain of a bad seam and removes the pressure to fix it. A single liaison can also become the only person who understands the boundary, re-creating the very bottleneck it was meant to relieve. And a forum with a creeping mandate drifts into a decision-making body that slows everyone down. The discipline is to pair the forum with an explicit view of whether the seam should persist, to give it a sunset condition, and to watch that it never becomes the sole holder of knowledge that ought to be written down.

How it implements the components

The forum realizes the human-process face of the archetype — the standing bridge and its rhythm, not the artifacts it coordinates over:

  • boundary_spanning_role_or_forum — it is this component: a named role or standing body assigned to carry coordination across a specific seam.
  • drift_review_cadence — the fixed rhythm on which the forum re-examines the seam, so a boundary that must stay coupled does not silently drift back apart.

It does not freeze the boundary into a versioned artifact — that explicit contract is Cross-Team Interface Contract — nor does it measure the coordination overhead that justifies its existence; that reading belongs to the Coordination-Overhead Dashboard and Platform Team Bottleneck Test.

References

[1] Organizational research on boundary-spanning roles (e.g. Tushman) finds that a small number of individuals who translate across two groups carry a disproportionate share of the information that crosses between them. A liaison or forum makes that role a deliberate assignment rather than an accident of who knows whom. ↩