Why CSCW applications fail: problems in the design and evaluationof organizational interfaces
CSCW '88 Proceedings of the 1988 ACM conference on Computer-supported cooperative work
The VideoWindow system in informal communication
CSCW '90 Proceedings of the 1990 ACM conference on Computer-supported cooperative work
Studies in computer supported cooperative work: theory, practice and design
Studies in computer supported cooperative work: theory, practice and design
CSCW: four characters in search of a context
Studies in computer supported cooperative work
Harmonious working and CSCW: computer technology and air traffic control
Studies in computer supported cooperative work
Cooperative prototyping studies—users and designers a dental case record system
Studies in computer supported cooperative work
Emancipation of and by computer-supported cooperative work
Scandinavian Journal of Information Systems
New Technology and Practical Police Work: The Social Context of Technical Innovation
New Technology and Practical Police Work: The Social Context of Technical Innovation
Understanding Computers and Cognition: A New Foundation for Design
Understanding Computers and Cognition: A New Foundation for Design
Work-Oriented Design of Computer Artifacts
Work-Oriented Design of Computer Artifacts
Talking Work: Language-games, Organisations and Computer Supported Cooperative Work
Computer Supported Cooperative Work
Workflow management systems for process organisations
Workflow management systems for process organisations
Computer Supported Cooperative Work
Computational Coordination Mechanisms: A tale of a struggle for flexibility
Computer Supported Cooperative Work
Hi-index | 0.00 |
We argue there is still much confusion about what is meant by cooperative work, and therefore what is meant by CSCW. It does not arise simply where more than one person is involved, and other attempts to delimit the field do not succeed. Since all work is socially organised, it would seem that all work potentially falls within the CSCW domain. If so, then (i) it would not be confined to a particular class of system ('groupware'); (ii) it would not be a small specialism bul would extend virtually throughout system design; and (iii) its interdisciplinary character would affect large areas of its contributing disciplines. We defend these consequences, and argue that CSCW is therefore more akin to a paradigm shift for its contributing disciplines than a particular subdiscipline in itself. We also consider not what CSCW is but how it has arisen in terms of a political economy - the interests of researchers, funding institutions and clients - and a set of ideologies. This sets out a position for contributing disciplines, but leaves open the detailed content of interdisciplinary relations.