Base120 · Perspective
Boundary Object Selection
Choose representations that bridge multiple perspectives while remaining meaningful to each
When to use
"Use when multiple communities with different frames need to collaborate. Choose representations (diagrams, documents, prototypes) that are meaningful to each community while remaining flexible enough to be interpreted differently by each."
Example
"A system architecture diagram serves as a boundary object — engineers see component interactions, product managers see feature dependencies, executives see cost centers. The diagram is the same object; each community reads what it needs from it."
Common misuse
"Choosing a representation that is precise for one community and meaningless to others. A 200-page technical spec is a boundary object only for engineers; for everyone else it is a wall."