Boundary Object
Updated 2026-08-17
INTRODUCTION
English translation pending.
CORE DEFINITION
A boundary object is an information carrier adaptable enough to serve different social worlds, such as a map, a fill-in form, or a standard library. Developers, designers, and product managers may each understand it differently, yet it holds the continuity of their collaboration. It needs no single perfect shared definition; it only has to stay concrete enough that everyone can point at it and keep working.
SCAFFOLDING EFFECT
Reduce cognitive load
- Anchor the cross-team talk: point at the shared artifact instead of arguing in abstractions. - Tolerate local readings: let each team use it in its own way without forcing one definition. - Keep the work moving: settle for an object that supports the work, not for total agreement.
Anchor fast decisions
The object is shared across communities while its meaning stays plastic, which combines enough stability to coordinate with enough flexibility for each group to keep its own view. That combination is precisely what collaboration across different languages requires.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Boundary_objectverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS