Designing groupware for congruency in use
Wolfgang Prinz, Gloria Mark, Uta Pankoke-Babatz · 1998
ti this paper, we present experiences from long-term groupware developmen~introduction and use in an organization.We report lessons learned concerning how a complex design process operates and how its components interac~Our experiences suggest that the processes of requirement analysis, system developmen~and user support need to fac~tate the mer=tig of individud work patterns into congruent system usage.We confirm tbe chm=tig nature of groupwae use by reporting empirical restits descnbmg different learning phases.Ke~ords Cooperative desi~gn,user advocacy, groupware requirements, group work, system inwoduction, prototyping.This paper begins with a description showing how coordination with groupware use is related to the process of group developmen~We then outiine our particular design approach explaining how we tried to achieve a common understanding between tie design team and users, and how we tried to account for user group developmen~ h the foUowing section we present empirical results on the actual use of the system in the work setting, illustrating how tbe group stived to achieve congruent conventions.*POL~e~is funded by