Boundary Object
Updated 2026-08-05
INTRODUCTION
English translation pending.
CORE DEFINITION
Introduced by Susan Leigh Star and James Griesemer, a boundary object is an entity such as a map, prototype, or shared document that is plastic enough to adapt to the needs of several communities yet stable enough to maintain a common identity across them. It coordinates work without requiring the groups to agree on interpretation. The core claim is that cooperation does not require shared understanding. The qualification is that the object must remain concrete enough to anchor discussion, or it loses its coordinating function.
SCAFFOLDING EFFECT
Reduce cognitive load
- Use Artifact Creation: Build a concrete shared object that each group can point to and use. - Use Interpretation Tolerance: Allow different groups to read the object differently rather than forcing one meaning. - Use Anchoring Check: Verify the object is specific enough to coordinate work instead of staying abstract.
Anchor fast decisions
Groups with different vocabularies and priorities cannot easily agree on definitions, so coordination fails when it depends on shared meaning. A shared object sidesteps this by providing a common reference point that each group can interpret in its own terms while still tracking the same thing. Because the object carries enough structure to align action without fixing interpretation, it lets cooperation proceed across boundaries that language cannot cross.
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