An artifact, model, or representation used by multiple communities of practice to coordinate work across domains while allowing different groups to interpret or use it according to their local needs.

Principle

A boundary object supports coordination when it combines sufficient stability to be recognizable across communities with sufficient plasticity to be interpreted in domain‑specific ways; its coordinating function depends on shared reference points and negotiated uses rather than on a single unified meaning.

Demonstration

Illustrative Scenario — Situation: A product family is developed by mechanical, software and validation teams. Recognition: each team needs a common reference to reason about interfaces. Action: teams adopt a shared interface diagram annotated with domain‑specific notes and versioned in a common repository. Consequence: teams coordinate implementation choices while maintaining locally relevant interpretations of the diagram.

Misapplication

Assuming any shared document is a boundary object. The semantic error is treating mere sharing as sufficient; without stability (versioning, agreed identifiers) and local interpretive practices, the artifact will produce confusion rather than coordination.

Consequence

When appropriately designed, boundary objects enable loose coupling and coordinated change across domains while preserving local autonomy; misdesigned or unmanaged boundary objects propagate hidden assumptions, cause mismatched expectations, and produce latent integration faults.

Reversal

Where exact interoperability and unambiguous semantics are mandatory (for example, an automated protocol validated by formal methods), the ambiguity tolerated by boundary objects is harmful and must be replaced by formal, rigorous specifications.

Boundary

Clearly within: a versioned interface diagram stored in a shared repository and annotated by each discipline. Boundary case: a spreadsheet shared by email without version control — it may serve as a boundary object only if supplemented by interpretation practices. Clearly outside: personal notes or private drafts not meant for multi‑community use.

Semantic Tension

Flexibility ↔ Rigor — boundary objects trade ambiguity that enables multiple readings for the coordination value of a stable reference.

Synthesis

A boundary object is a deliberately ambiguous yet stable coordination artifact: its power lies in enabling different communities to work from a common reference while allowing domain‑specific meaning, not in enforcing a single interpretation.