What factors and developments led to the establishment of the area of CSCW?
- The area of Office Automation (OA) had reached the end of an era, due to a lack of understanding the system requirements needed.
- The need to learn more about people working in groups and organizations and how technology affects that.
- Although some MIS people acknowledged the need for collaborative systems, the vendor companies designing and building these systems ignored it for the most part
- CSCW started as a joint effort between the system developers and specialists from a wide array of fields centered towards human interaction and behavioural science
- Groupware development has largely been funded by goverment contracts and telecomunication companies who want to tap into the market of Small Groups and Projects (see figure). The complexity to support large government contracts provided a substantial incentive to spur the development of CSCW and groupware.
What are the differences between US and EU research traditions in CSCW?
- The US primarily focus on Human-Computer interaction thus focusing more on small-group applications.
- Here, computer research industry labs and industry support for University are more influential, research is more intertwined.
- Experimental and observational - Emperical Research
- They feel that their EU counterpart's work often lack substance.
- Conferences are organized for the larger audiences interested and focuses on the polished product, rather than the developmental stages.
- The EU research stress organizational and large-project issues
- Not so intertwined, since most research is government funded and in-house focused.
- Driven by Social, Political or Economic theory which results in a broad platform being able to support a multitude of expansive software for collaborative approaches.
- Work also reflects a strong link to cultural norms and risks oversimplification.
- American workers strike EU as unmotivated or shallow
- Gatherings are attended by professionals and researchers to share current work and ideas and present.
What does Nunamaker tell about the role of anonymity in groupware systems?
- When an organization decides to implement a groupware system or systems, anonymity could potentially be very useful for the initial/start-up phases. This is due to the "secretive" aspect where people feel that they are "safe" from reprimand and thus generate more comments with greater candour. This can help the organization greatly, since users will be totally honest about improvements that need to be done or potential downsides to the system. However, as soon as the whole system is running and for the most part being used, anonymity should be phased out. This will help the organization to poll users on which ideas they support most and also elevate the system to a platform of user-acceptance and consensus.
- Anonymity in this case is used conditionally, depending on what the organization wants to achieve. However, it can also be abused by some users who see it as a back-door to being rude, offensive or vindictive. Education and feedback are good ways to counter the above and to enable users to use the system for a collaborative advancement.