Skip to main content
Get your brand new Wikispaces Classroom now
and do "back to school" in style.
Pages and Files
What is KM
Boundary objects (BOs):
BOs are a special group of knowledge objects because they cross community, group & organizational boundaries and help to carry meaning, promote commuication and assist with understanding. They serve as both containers and carriers.
are highly abstract and generalized form of knowledge organization with considerable reification. Classification systems, ontologies, paper forms serve as BOs (where they are used by diverse groups). An prime example of a BO is an ERP order entry process, a shared information space, a product tracking number, RFID tag....
Practice as object:
BOs in organizational memory:
‘Post-Modern’ Professional Work and Mobile Technology Masao Kakihara & Carsten Sørensen, 2002:
Blog post on BOs:
It is around BOs that Communities of Practice (CoPs) often gather. BOs are 'used' by members of different communities in very different ways, although the representation is shared. BOs are an important class of knowledge artifacts, they are associated with process, meaning, alignment and reification. They are center stage in the dynamics of knowledge exchange. When you are identifying & tracking BOs be aware of issues around translation, closure, context, shared meaning. BOs are also know as CISs (common information spaces). Here is an interesting article on the subject (a little theoretical):
Bog post 09/23/04:
Bannon and Bodker 1997? Constructing common information spaces:
Ackerman 1999 Organizational memory: process, boundary objects and trajectories,
Albrechtsen, H & Jacob, E.K. 1998. The dynamics of classification systems as boundary objects for cooperation in the electronic library. Library Trends, 47 2, pp.293-312.
Examples of boundary objects:
BOs in new product development:
A library catalog, databases, libraries, museums, organizational memories:
concept of species, a modal soil profile, or a well known pattern, a stable work process,
a map (of the same area) with different themes, scripts:
an order entry process, travel assistance request form.
Gather the name (this may change from community to community)
Describe and record the roles and responsibilities around the BO
Map the workflow, the path and sequence from node to node
Look for authorities, signoffs, trigger events, deviation procedures.
Check for learning points.
Record your findings in the BO register and on the knowledge map.
help on how to format text
Turn off "Getting Started"