Computer-supported cooperative work

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

The term computer-supported cooperative work (CSCW) was first coined by Irene Greif and Paul M. Cashman in 1984, at a workshop attended by individuals interested in using technology to support people in their work.[1] At about this same time, in 1987 Dr. Charles Findley presented the concept of Collaborative Learning-Work.[2] According to Carstensen and Schmidt,[3] CSCW addresses "how collaborative activities and their coordination can be supported by means of computer systems." On the one hand, many authors consider that CSCW and groupware are synonyms. On the other hand, different authors claim that while groupware refers to real computer-based systems, CSCW focuses on the study of tools and techniques of groupware as well as their psychological, social, and organizational effects. The definition of Wilson (1991)[4] expresses the difference between these two concepts:

<templatestyles src="Template:Blockquote/styles.css" />

CSCW [is] a generic term, which combines the understanding of the way people work in groups with the enabling technologies of computer networking, and associated hardware, software, services and techniques.

Central concerns of CSCW

CSCW is a design-oriented academic field that is interdisciplinary in nature and brings together economists, organizational theorists, educators, social psychologists, sociologists, anthropologists and computer scientists, among others. The expertise of researchers in various and combined disciplines help researchers identify venues for possible development. Despite the variety of disciplines, CSCW is an identifiable research field focused on understanding characteristics of interdependent group work with the objective of designing adequate computer-based technology to support such cooperative work.

Essentially, CSCW goes beyond building technology itself and looks at how people work within groups and organizations and the impacts of technology on those processes. CSCW has ushered in a great extent of melding between social scientists and technologists as developers work together to overcome both technical and non-technical problems within the same user spaces. For example, many R&D professionals working with CSCW are computer scientists who have realized that social factors play an important role in the development of collaborative systems. On the flip side, many social scientists who understand the increasing role of technology in our social world become “technologists” who work in R&D labs to develop cooperative systems.

Over the years, CSCW researchers have identified a number of core dimensions of cooperative work. A non-exhaustive list includes:

  • Awareness: individuals working together need to be able to gain some level of shared knowledge about each other's activities.[5]
  • Articulation work: cooperating individuals must somehow be able to partition work into units, divide it amongst themselves and, after the work is performed, reintegrate it.[6][7]
  • Appropriation (or tailorability): how an individual or group adapts a technology to their own particular situation; the technology may be appropriated in a manner completely unintended by the designers.[8][9][10]

These concepts have largely been derived through the analysis of systems designed by researchers in the CSCW community, or through studies of existing systems (for example, Wikipedia[11]). CSCW researchers that design and build systems try to address core concepts in novel ways. However, the complexity of the domain makes it difficult to produce conclusive results; the success of CSCW systems is often so contingent on the peculiarities of the social context that it is hard to generalize. Consequently, CSCW systems that are based on the design of successful ones may fail to be appropriated in other seemingly similar contexts for a variety of reasons that are nearly impossible to identify a priori.[12] CSCW researcher Mark Ackerman calls this "divide between what we know we must support socially and what we can support technically" the socio-technical gap and describes CSCW's main research agenda to be "exploring, understanding, and hopefully ameliorating" this gap.[13]

CSCW Matrix

the CSCW Matrix

One of the most common ways of conceptualizing CSCW systems is to consider the context of a system's use. One such conceptualization is the CSCW Matrix, first introduced in 1988 by Johansen; it also appears in Baecker (1995).[14] The matrix considers work contexts along two dimensions: first, whether collaboration is co-located or geographically distributed, and second, whether individuals collaborate synchronously (same time) or asynchronously (not depending on others to be around at the same time).

Same time/same place

Face to face interaction

  • Roomware
  • Shared tables, wall displays
  • Digital whiteboards
  • Electronic meeting systems
  • Single display groupware
  • Group Decision Support System

Same time/different place

Remote interaction

Different time/same place

Continuous task (Ongoing TAsk )

  • Team rooms,
  • Large displays
  • Post-it
  • Warrooms

Different time/different place

Communication + Coordination

There is a collaborative mode called multi-synchronous that can not fit the matrix.

Challenges in Computer-Supported Cooperative Work

Leadership

Generally, teams working in a CSCW environment need the same types of leadership as other teams. However, research has shown that distributed CSCW teams may need more direction at the time the group is formed than to traditional working groups, largely to promote cohesion and liking among people who may not have as many opportunities to interact in person, both before and after the formation of the working group.[15]

Creativity

With increased participation in CSCW working environments, researchers have become interested in studying creativity in such forums. However, research has shown that the interface elements of CSCW environments often slow down creative collaboration due to the design of interfaces themselves. There seems to be a gap between what people need socially to engage in creativity and the technical designs available to support such creativity. As such, researchers are continuing to investigate the tools that people need in order to creatively work in groups and are focusing their efforts on developing usable, supportive systems to cultivate creative group input and participation.[16]

Adoption of Groupware

Groupware goes hand in hand with CSCW. The term refers to software that is designed to support activities of a group or organization over a network and includes email, conferencing tools, group calendars, workflow management tools, etc.[17]

While groupware enables geographically dispersed teams to achieve organizational goals and engage in cooperative work, there are also many challenges that accompany use of such systems. For instance, groupware often requires users to learn a new system, which users may perceive as creating more work for them without much benefit. If team members are not willing to learn and adopt groupware, it is difficult (if not impossible) for the organization to develop the requisite critical mass for the groupware to be useful. Further, research has found that groupware requires careful implementation into a group setting, and product developers have not as yet been able to find the most optimal way to introduce such systems into organizational environments.[17]

On the technical side, networking issues with groupware often create challenges in using groupware for CSCW. While access to the Internet is becoming increasingly ubiquitous, geographically dispersed users still face challenges of differing network conditions. For instance, web conferencing can be quite challenging if some members have a very slow connection and others are able to utilize high speed connections.[17]

Intergenerational Groups

One of the recurring challenges in CSCW environments is development of an infrastructure that can bridge cross-generational gaps in virtual teams.[18]

Ideally, system designs will accommodate all team members, but orienting older workers to new CSCW tools can often be difficult. This can cause problems in virtual teams due to the necessity of incorporating the wealth of knowledge and expertise that older workers bring to the table with the technological challenges of new virtual environments. Orienting and retraining older workers to effectively utilize new technology can often be difficult, as they generally have less experience than younger workers with learning such new technologies.

Advantages of CSCW

While CSCW working environments certainly face challenges, they also provide many advantages as well. For instance, teams that work together asynchronously provide members with the luxury to contribute when they want, from the location of their choosing, thus eliminating the need for members to “synchronize schedules.”[19] CSCW also allows employees with specific expertise to be a part of teams without the concern of geographic restraints.”[20]

CSCW can also result in major cost savings to companies who implement virtual teams and allow employees to work at home by eliminating the need for travel, rented office space, parking, electricity office equipment, etc. Conversely, from the employee’s perspective, commuting costs and time associated with communing are also eliminated.

Further, research has shown that the use of multiple communication threads can increase group participation and contribution from more team members and foster a less egalitarian communication structure.[17][21] Along the same lines, text-based CSCW communication, such as email, allows users to keep a record of communication and can promote long-term collaboration and learning through observing others.[22]

Challenges in CSCW Research

Differing Meanings

Even within the CSCW field, researchers often rely on different journals, research, contextual factors and schools of thought, which can result in disagreement and confusion especially when common terms in the field are used in subtly different ways (“user,” “implementation,” etc.) Also, user requirements change over time and are often not clear to participants due to their evolving nature and the fact that requirements are always in flux.[1]

Identifying User Needs

Because organizations are so nuanced, CSCW researchers often have difficulty deciding which set(s) of tools will benefit a particular group.[23] This is exacerbated by the fact that it is almost impossible to accurately identify user/group/organization needs and requirements because such needs and requirements inevitably change through the introduction of the system itself. Even when researchers study requirements through several iterations, such requirements often change and evolve yet again by the time that researchers have completed a particular iteration of inquiry.

Evaluation and Measurement

The range of disciplinary approaches leveraged in implementing CSCW systems makes CSCW difficult to evaluate, measure, and generalize to multiple populations. Because researchers evaluating CSCW systems often bypass quantitative data in favor of naturalistic inquiry, results can be largely subjective due to the complexity and nuances of organizations themselves. Possibly as a result of the debate between qualitative and quantitative researchers, three evaluation approaches have emerged in the literature examining CSCW systems. However, each approach faces its own unique challenges and weaknesses:[24]

Methodology-oriented frameworks explain the methods of inquiry available to CSCW researchers without providing guidance for selecting the best method for a particular research question or population.

Conceptual frameworks provide guidelines for determining factors that a researcher should consider and evaluate through CSCW research but fail to link conceptual constructs with methodological approaches. Thus, while researchers may know what factors are important to their inquiry, they may have difficulty understanding which methodologies will result in the most informative findings.

Concept-oriented frameworks provide specific advice for studying isolated aspects of CSCW but lack guidance as to how specific areas of study can be combined to form more comprehensive insight.

CSCW Conferences

Since 2010, the Association for Computing Machinery has hosted a yearly conference on CSCW. From 1986-2010, it was held biannually.[25] The conference is currently held in February or March and features research in the design and use of technologies that affect organizational and group work. With the rapidly increasing development of new devices that allow collaboration from different locations and contexts, CSCW seeks to bring together researchers from across academia and industry to discuss the many facets of virtual collaboration from both social and technical perspectives.

Internationally, The Institute of Electrical and Electronics Engineers sponsors the International Conference on Computer Supported Work and Design, which takes place yearly.[26] In addition, the European Society for Socially Embedded Technologies sponsors the European Conference on Computer Supported Cooperative Work, which has been held every two years since 1989.[27][28]

See also

CSCW most cited papers

The 47 CSCW Handbook Papers.[29] This paper list is the result of a citation graph analysis of the CSCW Conference. It has been established in 2006 and reviewed by the CSCW Community. This list only contains papers published in one conference; papers published at other venues have also had significant impact on the CSCW community.

The “CSCW handbook”[29] papers were chosen as the overall most cited within the CSCW conference <...> It led to a list of 47 papers, corresponding to about 11% of all papers.

  1. Lua error in package.lua at line 80: module 'strict' not found.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. Lua error in package.lua at line 80: module 'strict' not found.
  29. Lua error in package.lua at line 80: module 'strict' not found.
  30. Lua error in package.lua at line 80: module 'strict' not found.
  31. Lua error in package.lua at line 80: module 'strict' not found.
  32. Lua error in package.lua at line 80: module 'strict' not found.
  33. Lua error in package.lua at line 80: module 'strict' not found.
  34. Lua error in package.lua at line 80: module 'strict' not found.
  35. Lua error in package.lua at line 80: module 'strict' not found.
  36. Lua error in package.lua at line 80: module 'strict' not found.
  37. Lua error in package.lua at line 80: module 'strict' not found.
  38. Lua error in package.lua at line 80: module 'strict' not found.
  39. Lua error in package.lua at line 80: module 'strict' not found.
  40. Lua error in package.lua at line 80: module 'strict' not found.
  41. Lua error in package.lua at line 80: module 'strict' not found.
  42. Lua error in package.lua at line 80: module 'strict' not found.
  43. Lua error in package.lua at line 80: module 'strict' not found.
  44. Lua error in package.lua at line 80: module 'strict' not found.
  45. Lua error in package.lua at line 80: module 'strict' not found.
  46. Lua error in package.lua at line 80: module 'strict' not found.
  47. Lua error in package.lua at line 80: module 'strict' not found.

References

  1. 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. .Findley, Charles A. 1989. Collaborative Learning-work. Presentation at the Pacific Telecommunications Council 1989 Conference, January 15–20, Honolulu, Hawaii.Collaborative Networked Learning Project – Digital Equipment Corporation. Primary documents stored on Internet Archive
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. 17.0 17.1 17.2 17.3 Lua error in package.lua at line 80: module 'strict' not found.
  18. Lua error in package.lua at line 80: module 'strict' not found.
  19. Lua error in package.lua at line 80: module 'strict' not found.
  20. Lua error in package.lua at line 80: module 'strict' not found.
  21. Lua error in package.lua at line 80: module 'strict' not found.
  22. Lua error in package.lua at line 80: module 'strict' not found.
  23. Lua error in package.lua at line 80: module 'strict' not found.
  24. Lua error in package.lua at line 80: module 'strict' not found.
  25. Lua error in package.lua at line 80: module 'strict' not found.
  26. Lua error in package.lua at line 80: module 'strict' not found.
  27. Lua error in package.lua at line 80: module 'strict' not found.
  28. http://www.ecscw.org/
  29. 29.0 29.1 Lua error in package.lua at line 80: module 'strict' not found.

External links