Qualitative research methods in design and development

In recent years, we have seen an increase in the use of qualitative and ethnographic methods for the design of systems. This rise has been motivated , at least in part, by the following factors: the need to understand user work before design begins; the inadequacy of many traditional forms of data and requirements gathering when applied to interface design problems; the need to involve users in the design process; and the increasing recognition that the transition to a modern interface metaphor, that is, a GUI, is insufficient to produce a usable system. At the same time, we have learned that qualitative and ethnographic methods of data collection and analysis are not simply new and different methods that can be directly " plugged into " an existing development process. The methods, procedures, and fundamental assumptions of qualitative techniques have a different origin than those of classic engineering approaches. Qualitative approaches fly in the face of the engineering and marketing cultures in many companies. It's not surprising that many designers who have introduced these techniques have also described themselves as cultural change agents and offer prescriptions for cultural change and alternative approaches to engineering systems [1, 15]. The discrepancies between the engineering culture and the roots of qualitative research are often implicit, and are the source of

[1]  C. Dennis Allen Succeeding as a clandestine change agent , 1995, CACM.

[2]  Michael J. Muller,et al.  Participatory design , 1993, CACM.

[3]  Michael Good,et al.  Participatory design of a portable torque-feedback device , 1992, CHI.

[4]  Karen Holtzblatt,et al.  Making customer-centered design work for teams , 1993, CACM.

[5]  Richard E. Zultner,et al.  TQM for technical teams , 1993, CACM.

[6]  Kate Ehrlich,et al.  Usability engineering for Lotus 1–2–3 release 4 , 1994 .

[7]  Mary Elizabeth Raven,et al.  Using contextual inquiry to learn about your audiences , 1996, ASTR.

[8]  Stanley H. Caplan Making usability a Kodak product differentiator , 1994 .

[9]  Dennis R. Wixon,et al.  Changing the Rules: A Pragmatic Approach to Product Development , 1993, Digit. Tech. J..

[10]  R. Hepburn,et al.  BEING AND TIME , 2010 .

[11]  Karen Holtzblatt,et al.  Apprenticing with the customer , 1995, CACM.

[12]  Jeff A. Johnson,et al.  User preferences for task-specific vs. generic application software , 1994, CHI '94.

[13]  Anthony F. Hutchings,et al.  Creating products customers demand , 1995, CACM.

[14]  Deborah Hix,et al.  A taxonomic model for developing high impact formative usability evaluation methods , 1994, CHI Conference Companion.

[15]  Michael Wiklund,et al.  Usability in practice: how companies develop user-friendly products , 1994 .

[16]  RavenMary Elizabeth,et al.  Using contextual inquiry to learn about your audiences , 1996 .

[17]  Michael J. Muller,et al.  Taxonomy of PD Practices: A Brief Practitioner's Guide , 1993, Commun. ACM.

[18]  Clayton Lewis,et al.  Making usable, useful, productivity-enhancing computer applications , 1991, CACM.

[19]  Finn Kensing,et al.  PD: structure in the toolbox , 1993, CACM.

[20]  R. Barker,et al.  Midwest and its children: the psychological ecology of an American town. , 1954 .

[21]  Morten Kyng,et al.  The design challenge—creating a Mosaic out of chaos , 1995, CHI '95.