A case study of the confluence of various differing social worlds in a natural history museum. The idea of 'Boundary Objects' is invoked to explain how the social world communicate and work together.
Boundary Objects =
- Inhabit several intersecting social worlds and satisfy the information needs of each.
- Plastic enough to adapt local needs and constraints, yet robust enough to retain an identity.
- Weakly structured in common use but strongly structured in individual use.
- Abstract or concrete.
- Different meaning in each social world but common structure, so means of translation.
- Used to create and maintain coherence across social worlds.
So they must be abstract and concrete, specific and general conventionalised and customised and internally heterogeneous in order to fulfil their translation and coherence creating role.
When people collaborate from different social worlds , they frequently have to address objects crafted from elements of many different worlds. Each world has a hand in creating them for the next world, and frequently they have different meanings for each world.
When members of different worlds create boundary objects, their different perceptions are resolved into representations. this does not necessarily mean consensus: still clear traces of viewpoints.
For my research, something that is both abstract and concrete, possibly represented differently by both parties and that can also provide very good source of communication between each party, is the customer.
I need to look at how ethnographic methods can be applied to boundary object study: does it compromise disponibilty to assume that something is a boundary object; Star and Griesemer seem to have a functional view of boundary objects where they are created to fulfill some purpose but can I assume that they grow up independent of intention?
I had originally intended to use the procedural wiki as a boundary object, but this seems to concrete. I think that this is an object that is too robust to be a boundary object, partly because library staff have very little sense of propriety over it (I should be cautious of not jumping the gun here), but also because it is not clear the extent to which a shared artifact that is created by both groups could translate between them: that would seem to questions-beg (if it is created by both of them something must have enabled the collaboration, so what did the initial translating?).
The customer as boundary object seems like a more promising example because it is something that both groups have accessed in the past from entirely distinct viewpoints, and will continue to access in the future . The differing views of the customer (if they exist) may enable interesting triangulation towards deep seated assumptions about role and jurisdiction.
See also:
Star (1989) "The structure of ill-structured solutions: boundary objects and heterogeneous distributed problem solving" in Huhs and Gasser (edit.) Readings in Distributed AI 3 Melo Park CA: Morgan Kaufmann.
No comments:
Post a Comment