CSCW's object is cooperative work, not group software

The field was named before anyone agreed what the name referred to. Computer-supported cooperative work acquired its acronym in the mid-1980s (Grudin, 1994), and its founders soon asked what the acronym named. Bannon and Schmidt (1989) framed the difficulty as a search for a context: the field's identity, they argued, was being settled prematurely by the tools it happened to build.

The answer they gave is this unit's thesis, and it opens a sequence of ten. A system is judged not by whether a group uses it but by whether the work holds together. The work of holding it together is part of the object. The founding move of CSCW was to make cooperative work, and the articulation work that sustains it, the unit of analysis. That move decides what counts as a failure, what a study observes, and who may say what a system is for. The second unit asks why a system built on it collapses.

The field named itself before it agreed what it studied

Bannon and Schmidt (1989) wrote before the field had a journal. They borrowed the shape of a play title to ask who the four characters were and what context they stood in. Their target was scope rather than terminology: a field that takes its questions from the groupware it has built keeps rediscovering the problems groupware happens to have. Grudin's history (1994) supplies the composition that made that likely. The field drew from product development and research rather than group psychology. Grudin names the tension between a small-group approach and a systems approach. The founding question, on this account, was not what groups are but what cooperative work requires.

Articulation work was the object the field had been missing

Schmidt and Bannon (1992) gave the field the object it had been missing. They argued that CSCW should be concerned with the support requirements of cooperative work arrangements rather than with computer support for groups. The small-group conception marginalises the problems that decide whether systems work at scale. Their name for the missing object is articulation work, the coordinating work that holds a distributed arrangement together.

The UTOPIA project ran from 1981 to 1985 with the Nordic Graphic Workers' Union. Five union members worked beside researchers on page make-up and image processing for newspapers. They treated the graphic workers as designers rather than as people to observe. The method followed the object: mock-ups in place of specifications and cardboard simulations of screen tools the workers handled before any code existed (Greenbaum and Kyng, 1991). The case shows what taking articulation work seriously looks like, and its limit: UTOPIA changed a project, not a market, and the deskilling tools it answered were already shipping.

If the object is a tool, evaluation asks whether the tool was used. If the object is an arrangement of work, evaluation asks whether the work holds together, for whom and at what cost. Articulation work becomes visible when it fails, as in a handover nobody owns. Schmidt and Bannon are arguing a definition rather than reporting a study, and their definition is what this unit tests.

Why the tool framing fails on incentives and on exceptions

Grudin (1988) listed the recurring reasons CSCW applications fail. At the centre sits a mismatch between the person who does the work and the person who benefits. He added the difficulty of evaluating an interface whose effects fall on an organisation rather than a user. Failure, on this reading, is a property of the social arrangement rather than of the software alone.

Ellis, Gibbs and Rein (1991) make the contrast sharp. Surveying groupware systems, they organised them by the time and place of interaction and argued the technology must fit the group's coordination pattern. Theirs is a taxonomy of software, classifying what has been built rather than what cooperative work requires, which is the premature settling Bannon and Schmidt warned against. Yet their own deployment experience points past it, since, on their own account, it is difficult to separate the technical issues from the social concerns.

The object is sociotechnical, and it is also political

If cooperative work is the object, the object is not kindly. Kling and Scacchi (1982) argued that computing is best understood as a web of social and technical arrangements. What an information system does therefore depends on the organisational context that builds and uses it. Kling (1991) pressed the point into the field's own vocabulary. He argued that computer-supported work is at once a coordination and a control arrangement. Treating it as purely cooperative hides the interests a system serves. The object therefore includes power: a system that supports articulation work also distributes it.

Procedure cannot carry the work

Suchman (1987) used a photocopier help system to show that plans do not determine action; they are resources people use and repair in situ. The mismatch between the plan a system encodes and the action people take is why a procedure-following interface breaks. That mismatch is internal to the design rather than a defect in the user.

Hughes, Randall and Shapiro (1992) tested the next step, whether a rich account of work can be carried into design at all. Working from an ethnographic study of air traffic control, they explored ways of linking ethnography to CSCW design and discussed metaphors for representing manual practice with their limitations. The paper's title answers its own question: the translation faltered.

Cooperation holds without consensus, and collective activity is the unit

Star and Griesemer (1989) analysed how amateurs, professionals, administrators and others connected to the Museum of Vertebrate Zoology worked together. They identified boundary objects that stay adaptable to different viewpoints while keeping their identity across them. Cooperation held through these artefacts without a shared goal, which is how articulation work succeeds where consensus is unavailable.

Schmidt and Simone (1996) turned the insight towards design by developing coordination mechanisms: protocols, classificatory schemes and routines that produce the order of cooperative work without a central controller. Their concept is the bridge to a design vocabulary, and a scheme of that kind has to be read, so a worker in a second language is governed by it. Heath and Luff (1991) showed how much of that work depends on resources a medium carries or transforms. They found the technology transforms verbal and non-verbal conduct and introduces asymmetries between users. They argued those asymmetries may facilitate some forms of collaborative work rather than only hinder them.

Kuutti (1996) supplied the unit of analysis the object requires. He proposed cultural-historical activity theory as a framework for HCI. He set out activity, action and operation as levels of analysis and treated artefacts as mediators of work. The thing to study is collective activity rather than the isolated user. What is coordinated is a mediated, collective accomplishment, and no single person's task description contains it.

Contested question: is cooperative work an object or an aspiration?

The literature agrees that the object ought to be cooperative work and disagrees about what the object delivers. One side reads it as generative. Schmidt and Bannon (1992) define the object, and Schmidt and Simone (1996) show it yields a design vocabulary in coordination mechanisms.

The other side reads it as a relocation of the problem rather than a solution. Hughes and colleagues (1992) found the ethnographic account did not convert into design. Ackerman (2000) generalised the difficulty into a structural claim. The social requirements of cooperative work are under-specified by any formal system, while the mechanisms available are brittle in the face of that under-specification. On this reading the field knows what it must support and cannot yet support it. A second axis cuts across both. Kling (1991) argues the cooperative framing under-describes control, so the object is not politically neutral; a programme that builds coordination mechanisms may build control mechanisms under another name.

What would settle the disagreement is a documented case. An analysis of cooperative work produced a mechanism that held the work together without reinstating central control. The case also carried an account of what design owes that analysis. Such a case would show the object is generative; its absence would support the reading that taking CSCW seriously named the field's problem more precisely than it solved it.

Rate the evidence on each side. The generative reading rests on two conceptual papers, since Schmidt and Bannon (1992) argue a definition and Schmidt and Simone (1996) propose a foundation rather than report a study. The relocation reading rests on the air traffic control ethnography of Hughes and colleagues (1992), which failed to convert, and on Ackerman's (2000) structural argument. One case against a definition decides nothing. While the dispute is open, a designer should build the mechanism and record what the articulation work cost. The strongest objection is that a mechanism holding work together without a central controller is the control arrangement Kling (1991) warned about.

Where the argument is heading

The direction of travel is set by Ackerman's (2000) gap rather than by any new device. He named the social-technical gap as the central challenge for CSCW. The gap divides what the field knows it must support socially from what its systems can support. The naming relocated the field's ambition from describing work to designing around a gap it cannot close. Schmidt and Simone (1996) supply the design vocabulary for that work, and Kuutti (1996) supplies the unit of analysis, collective mediated activity. The question the area carries forward is what a design can honestly claim when it has taken cooperative work seriously and still cannot support all of it.

The sources this unit rests on

Each note states what the document did and found. Identifiers were resolved on 2 November 2026.

• Bannon, L. and Schmidt, K. (1989). CSCW: four characters in search of a context. https://dl.eusset.eu/items/6d7cbaa8-e9e5-4cb8-84d0-5a016a5083bc Examines the name and scope of CSCW and argues the field's identity was being settled by the tools it happened to build. It gives this unit's thesis its pre-history: the dispute was about scope, not terminology.
• Schmidt, K. and Bannon, L. J. (1992). Taking CSCW seriously. doi:10.1007/bf00752449 Argues CSCW had no settled object and defines the field by the support requirements of cooperative work arrangements rather than by computer support for groups, introducing articulation work. It supplies this unit's object.
• Grudin, J. T. (1994). Computer-supported cooperative work: history and focus. doi:10.1109/2.291294 Reconstructs the field's early composition and the work found under the CSCW umbrella, describing the tension between a small-group approach and a systems approach. It shows the field's questions came from product development, not group psychology.
• Grudin, J. T. (1988). Why CSCW applications fail. doi:10.1145/62266.62273 Lists the recurring reasons CSCW applications fail, centred on the mismatch between who does the work and who benefits. It frames failure as a property of the social arrangement rather than of the software.
• Ellis, C. A., Gibbs, S. J. and Rein, G. L. (1991). Groupware: some issues and experiences. doi:10.1145/99977.99987 Surveys groupware systems, organising them by the time and place of interaction, and argues the technology must fit the group's coordination pattern. It is the taxonomy of software this unit contrasts with the cooperative-work object.
• Kling, R. and Scacchi, W. (1982). The web of computing: computer technology as social organisation. doi:10.1016/s0065-2458(08)60567-7 Argues computing is a web of social and technical arrangements whose effects depend on the organisational context that builds and uses them. It is the premise that makes cooperative work, not the artefact, the thing to study.
• Kling, R. (1991). Cooperation, coordination and control in computer-supported work. doi:10.1145/125319.125396 Argues computer-supported work is at once a coordination and a control arrangement, so treating it as purely cooperative hides the interests a system serves. It is the counterweight that keeps this unit's object from being read as harmonious.
• Suchman, L. A. (1987). Plans and situated actions: the problem of human-machine communication. https://archive.org/details/planssituatedact0000such Shows through a photocopier help system that plans do not determine action but are resources people use and repair in situ. It grounds this unit's claim that procedure cannot carry cooperative work.
• Hughes, J., Randall, D. and Shapiro, D. (1992). Faltering from ethnography to design. doi:10.1145/143457.143469 Explores ways of linking ethnographic studies of cooperative work to CSCW design, using an air traffic control project, and discusses metaphors for representing manual practice with their limitations. It shows the object is hard to convert into requirements.
• Star, S. L. and Griesemer, J. R. (1989). Institutional ecology, translations and boundary objects. doi:10.1177/030631289019003001 Analyses how amateurs, professionals and administrators around the Museum of Vertebrate Zoology cooperated through standard methods and boundary objects that stay adaptable to different viewpoints yet keep their identity. It explains how articulation work succeeds without shared goals.
• Schmidt, K. and Simone, C. (1996). Coordination mechanisms: towards a conceptual foundation of CSCW systems design. doi:10.1007/bf00133655 Develops coordination mechanisms as a concept for how the order of cooperative work is achieved without a central controller, analysing protocols, classificatory schemes and routines as constructed artefacts. It bridges the object to a design vocabulary.
• Heath, C. and Luff, P. (1991). Disembodied conduct: communication through video in a multi-media office environment. doi:10.1145/108844.108859 Analysed video-recordings of collaboration through audio-visual links in a dispersed office and found the technology transforms verbal and non-verbal conduct and introduces asymmetries between users. The authors argue those asymmetries may facilitate some forms of collaborative work rather than only hinder them.
• Kuutti, K. (1996). Activity theory as a potential framework for human-computer interaction research. doi:10.7551/mitpress/2137.003.0006 Proposes cultural-historical activity theory as a framework for HCI, with activity, action and operation as its levels and artefacts as mediators of work. It makes collective activity, not the isolated user, the unit of analysis.
• Ackerman, M. S. (2000). The intellectual challenge of CSCW: the gap between social requirements and technical feasibility. doi:10.1207/s15327051hci1523_5 Argues CSCW faces an inherent social-technical gap: human activity is flexible, nuanced and contextualised, yet systems cannot fully support the social world its findings uncover. It states the field's central tension, which this unit uses to close.
• Greenbaum, J. and Kyng, M. (1991). Design at work: cooperative design of computer systems. doi:10.1201/9781003063988 Documents the UTOPIA project, in which union graphic workers and researchers designed newspaper production tools together through mock-ups and joint analysis of the work. It is the unit's instance of designing for cooperative work.