Cscw

Computer-supported cooperative work (CSCW) is the study of how people work together and how computer systems can help or hinder them.

11 frameworks, from 1975 to today · Human Computer Interaction · Computer Science

still a working view ended · each leads to its entry below

Overview

Computer-supported cooperative work (CSCW) is the study of how people work together and how computer systems can help or hinder them1. Its subject is not the single user at a single screen but groups, teams, organizations, and, later, whole publics coordinating across distance and time. What is at stake is practical and political at once: a hospital shift handover that loses a patient's allergy because the record system was built for individual entry; an air-traffic control room where shared awareness depends on who can see which strip of paper; a workplace where a scheduling algorithm quietly reorganizes who gets to rest. CSCW grew up asking why systems designed for one person fail when the real work is collective, and it has kept asking that question as the collective has expanded from the office to the platform.

Groupware and the office of the 1980s

The field's name was coined in the mid-1980s, when a group of researchers, many from Xerox PARC and the organizational-behavior tradition, organized a workshop that became the first CSCW conference in 1986. The motivating problem was concrete: personal computing had arrived, but the tools assumed a solitary worker. Email existed, but shared calendars, shared documents, and shared workspaces were primitive or absent. The term groupware named the class of systems meant to support groups directly12.

Early groupware split along two axes that still organize the field: same place versus different place, and same time versus different time. A meeting-room system for a shared electronic whiteboard is same-place, same-time; email is different-place, different-time1. The taxonomy made a point that mattered: coordination across time and distance is not a degraded version of face-to-face work but a different problem with its own costs. Systems such as the Coordinator, which tried to structure office communication as explicit speech acts (requests, promises, commitments), and shared-editing and meeting-support tools of the late 1980s and 1990s put these ideas into practice. Some worked; many were rejected by the people they were built for, and those rejections taught the field as much as the successes.

Workplace studies: why the designed system and the real work diverge

The central early lesson came from ethnography. Researchers went into offices, control rooms, and laboratories and watched what people actually did, and repeatedly found that the formal procedures a system encoded were not the procedures people used. Lucy Suchman's Plans and Situated Actions (1987) made the theoretical case: human action is not the execution of a pre-formed plan but is situated, improvised in response to the concrete circumstances of the moment. A photocopier help system that tried to script the user's every step failed because real troubleshooting is responsive and contingent.

Workplace studies built on this. Studies of air-traffic control, hospital wards, and newsrooms showed that much of the coordination that keeps work going is invisible to formal records: a glance, a shouted update, a note left on a desk. Christian Heath and Paul Luff's work on control rooms, and later studies of London Underground operations, documented how shared physical space and peripheral awareness do coordination work that no database captures. The practical implication was sharp: a system that digitizes the visible procedure while erasing the informal, situated work around it can make an organization worse. This is the social-technical gap, named by Mark Ackerman in 2000: the persistent mismatch between what social life requires and what technology can encode. Ackerman argued the gap is not a bug to be closed but a permanent condition to be designed around.

Coordination and awareness theory

If informal awareness matters, how do you build for it? A body of theory grew up around coordination (how interdependent activities are aligned) and awareness (what people know about others' activities without asking)1. The distinction between explicit coordination, done through messages and forms, and implicit coordination, done through shared context, became central. Systems began to display "awareness information": who is online, what they are editing, where the cursor is. The tension is that awareness cues are also surveillance. A shared calendar that helps a team also lets a manager watch. CSCW's coordination theory therefore carried an ethical edge from early on, asking how much visibility a cooperative system should provide and to whom.

Participatory design and the Scandinavian inheritance

A parallel strand came from Scandinavia, where trade unions and researchers had, since the 1970s, insisted that workers should help design the systems that would restructure their jobs. The participatory design tradition, associated with projects such as the UTOPIA effort in the Nordic graphics industry, brought workers into design workshops and treated them as experts in their own labor. Its methods, including future workshops and cooperative prototyping, crossed into CSCW and shaped the field's conviction that design is a negotiation among stakeholders with unequal power, not a technical optimization. This inheritance is why CSCW has always been more comfortable than mainstream HCI with questions about who benefits from a system.

From the office to social computing

Through the 1990s the field's scope widened. The internet and then the web moved cooperative work out of the office. Social computing named the study of systems whose primary product is social: mailing lists, wikis, social network sites, recommendation and reputation systems. Research on online communities, open-source collaboration, and Wikipedia's coordination showed that large groups could self-organize with light technical scaffolding, and that the design of that scaffolding (who can edit, how reputation accrues, how conflict is handled) determined whether the community thrived. The unit of analysis shifted from the team to the crowd, and the methods shifted with it, toward large-scale data analysis alongside ethnography.

Values, critique, and the turn to platforms

As computing moved from tools to infrastructures, CSCW's critical wing grew. Value-sensitive design, developed by Batya Friedman and colleagues from the 1990s, argued that systems embody values (privacy, trust, autonomy, fairness) whether or not designers intend it, and offered methods for making those values explicit and deliberate. Critical CSCW pushed further, asking whose interests a system serves and treating design as a site of power. The field's attention turned to platforms and algorithms: the recommendation systems, ranking algorithms, and gig-work dispatchers that now mediate cooperative activity at scale. Studies of ride-hailing drivers, content moderators, and warehouse workers examined how algorithmic management coordinates labor while hiding its logic from the people subject to it, reviving the old awareness-and-coordination questions in a new key.

Where the field stands

Today CSCW is a broad, methodologically plural field. Ethnography and workplace studies remain central for understanding what work actually is; large-scale quantitative analysis of platform data has joined them. The design concerns of groupware and participatory design persist in the study of collaborative tools, remote work, and civic technology. The social-technical gap is still the field's organizing problem, and the questions it leaves open are live: how to design for awareness without surveillance, how to give workers and communities genuine voice in systems that manage them, and how to study coordination when the coordinating infrastructure is a proprietary algorithm no researcher can inspect. The field began by noticing that the solitary user was a fiction; it has spent four decades discovering how far that fiction reached.

References

  1. Computer-supported cooperative work (introduction, Central concerns and concepts, Adoption of groupware, Matrix, Same time/different place – remote interaction), Wikipedia
  2. Collaborative software, Wikipedia

The frameworks of Cscw

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1975-Present

    Participatory design

    Who should have a voice in designing systems that reshape work?

    Fly to its tower in Nousfarer

  2. 1984-2000

    Collaborative software

    How can software directly support groups working together?

    Fly to its tower in Nousfarer

  3. 1986-Present

    Workplace studies

    What do people actually do that formal procedures miss?

    About Workplace studies
    Workplace Studies emerged in the late 1980s and early 1990s as a direct response to the brittle, tool-centric failures of earlier groupware. Where Computer-Mediated Communication treated cooperation as a channel problem and Groupware assumed that better interfaces would automatically foster collaboration, Workplace Studies asked a different question: what does real cooperative work actually look like, moment by moment, in its natural setting? The answer required a shift in method and theory—away from laboratory experiments and formal models and toward sustained ethnographic observation of work as it unfolds. In the CSCW subfield, Workplace Studies became the primary vehicle for recovering the tacit, situated, and improvisational character of human cooperation, and for translating those insights into design guidance that respects the complexity of actual practice.
    In a first course on Workplace Studies, students encounter a set of concepts that form the backbone of the framework. The logical teaching spine begins with the foundational method: Ethnographic Observation of Work and Field Studies of Technology Use. These are not generic data-collection techniques; they are the committed practice of watching real people doing real tasks, in their actual workplaces, over extended periods. The theoretical lens that justifies this approach is Situated Action, the idea that plans and protocols are always embedded in—and shaped by—the material and social circumstances of the moment. From here, the curriculum moves to the core phenomena that ethnographic observation reveals: Articulation Work (the invisible labour of meshing tasks across people and resources), Coordination Mechanisms (the explicit or implicit arrangements that keep joint activity aligned), and Awareness in Cooperative Work (the ongoing, peripheral monitoring of colleagues' actions that enables smooth interaction).
    A second cluster centres on the tension between formal procedures and lived practice. Students learn to recognise Workarounds and Informal Practices as intelligent adaptations, not deviance; to study Routines and Procedures as resources that workers actively negotiate rather than blindly follow; and to appreciate Tacit Knowledge in Collaboration—the know-how that can be demonstrated but not fully articulated. Turning to analysis, the curriculum introduces Work Practice Analysis as a disciplined way of converting ethnographic raw material into design-relevant findings; Technology-in-Practice as the insight that technologies acquire meaning only through how people actually use them; and the Materiality of Work, which foregrounds how physical objects, tools, and spaces shape cooperation. Finally, students explore Interactional Expertise (the ability to participate competently in another community's practice) and Cognitive Artifacts (external representations or devices that support cognition in the wild). These last two concepts bridge Workplace Studies to neighbouring discussions of distributed expertise and material cognition.
    The intellectual history of Workplace Studies in CSCW runs through two main tributaries. The first is the ethnomethodology of Harold Garfinkel, which treated social order as an ongoing, practical accomplishment. The second is Lucy Suchman's landmark 1987 book Plans and Situated Actions, which directly challenged the planning model of human action then dominant in Artificial Intelligence and human-computer interaction. Suchman's work demonstrated, through careful analysis of photocopier use, that people rely on ad hoc responses to local contingencies far more than on pre-scripted plans. Although Plans and Situated Actions pre-dates the formal label 'Workplace Studies' (which solidified around 1990), it is the foundational precursor. Within the 1990-2026 dominance window, the key figures are Christian Heath and Paul Luff, whose 1992 study of London Underground control rooms revealed how operators used talk, gesture, and shared screens to produce seamless coordination in high-stakes settings. At Xerox PARC, Jack Whalen and Marilyn Whalen conducted extensive field studies of call centres and repair work, showing how seemingly scripted work was continually improvised. The 2000 collection Workplace Studies: Recovering Work Practice and Informing System Design, edited by Luff, Hindmarsh, and Heath, codified the framework's methods and findings for a broad CSCW audience.
    Workplace Studies coexisted with its immediate predecessor, Socio-Technical Design, but shifted emphasis: whereas Socio-Technical Design focused on jointly optimising technology and organisational structure, Workplace Studies prioritised fine-grained observation of practice as the starting point for any intervention. The framework also interacted critically with Workflow Systems, which emerged around 1994 and tried to formalise and automate coordination. Workplace Studies consistently showed that workflow models fell short because they could not accommodate the flexibility and tacit knowledge that real work demanded. In later years, Workplace Studies influenced Social Computing (by providing ethnographic methods for studying online communities) and Crowd Work (by documenting the invisible articulation work in platform labour). However, its core contribution remains the insistence that effective CSCW design must begin by watching—not assuming—how people actually work together.
    The 14 concepts its tower teaches
    • Articulation Work
    • Awareness in Cooperative Work
    • Cognitive Artifacts
    • Coordination Mechanisms
    • Ethnographic Observation of Work
    • Field Studies of Technology Use
    • Interactional Expertise
    • Materiality of Work
    • Routines and Procedures
    • Situated Action
    • Tacit Knowledge in Collaboration
    • Technology-in-Practice
    • Work Practice Analysis
    • Workarounds and Informal Practices

    Fly to its tower in Nousfarer

  4. 1987-2005

    Situated action

    Is action the execution of plans or improvised in circumstances?

    Fly to its tower in Nousfarer

  5. 1992-Present

    Coordination and awareness theory

    How do people align activities and know what others are doing?

    Fly to its tower in Nousfarer

  6. 1994-Present

    Social computing

    How do large groups self-organize through social systems?

    Fly to its tower in Nousfarer

  7. 1996-Present

    Value-sensitive design

    How can designers make the values systems embody explicit?

    Fly to its tower in Nousfarer

  8. 2000-Present

    Social-technical gap

    Why do social requirements always exceed what technology encodes?

    Fly to its tower in Nousfarer

  9. 2005-Present

    Critical CSCW

    Whose interests does a system serve, and who bears its costs?

    Fly to its tower in Nousfarer

  10. 2015-Present

    Algorithmic management and platform labor

    How do algorithms coordinate labor while hiding their logic?

    Fly to its tower in Nousfarer

  11. 2015-Present

    Platform and algorithm studies

    How do platforms and algorithms shape what people see and do?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

Participatory designCollaborative softwareWorkplace studiesSituated actionCoordination and awareness theorySocial computingValue-sensitive designSocial-technical gapCritical CSCWAlgorithmic management and platform l…Platform and algorithm studies

Beyond the field

Where Cscw's ideas came from in other fields, and what they led to there: the strongest 12 of 48 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Cscw is a planet in Nousfarer

Its city has a tower for each of these 11 frameworks. Land, walk in, and climb one concept at a time.

Land on Cscw

Related fields

Fields its ideas are linked to

More in Human Computer Interaction

See where Cscw sits on the Map of Human Knowledge