Contextual design (CD) is a user-centered design process developed by Hugh Beyer and Karen Holtzblatt. It incorporates ethnographic methods for gathering data relevant to the product via field studies, rationalizing workflows, and designing human–computer interfaces. In practice, this means that researchers aggregate data from customers in the field where people are living and applying these findings into a final product. Contextual design can be seen as an alternative to engineering and feature driven models of creating new systems.
The contextual design process consists of the following top-level steps: contextual inquiry, interpretation, data consolidation, visioning, storyboarding, user environment design, and prototyping.
Main article: Contextual inquiry
Contextual inquiry is a field data collection technique used to capture detailed information about how users of a product interact with the product in their normal work environment. This information is captured by both observations of user behavior and conversations with the user while she or he works. A key aspect of the technique is to partner with the user, letting their work and the issues they encounter guide the interview. Key takeaways from the technique are to learn what users actually do, why they do it that way, latent needs, desires, and core values.
Data from each interview is analyzed and key issues and insights are captured. Detailed work models are also created in order to understand the different aspects of the work that matter for design. Contextual design consists of five work models which are used to model the work tasks and details of the working environment. These work models are:
Data from individual customer interviews are analyzed in order to reveal patterns and the structure across distinct interviews. Models of the same type can be consolidated together (but not generalized—detail must be maintained). Another method of processing the observations is making an affinity diagram ("wall"), as described by Beyer & Holtzblatt:
Beyer & Holtzblatt propose the following color-coding convention for grouping the notes, from lowest to highest level in the hierarchy:
Beyer & Holtzblatt emphasize the importance of building the entire affinity diagram in one or two sessions rather than building smaller affinity diagrams over many sessions. This immersion in the data for an extended period of time helps teams see the broad scope of a problem quickly and encourages a paradigm shift of thought rather than assimilation of ideas.
The design ideas and relevant issues that arise during the process should be included in the affinity diagram. Any holes in the data and areas that need more information should also be labeled. After completing the wall, participants "walk" the affinity diagram to stimulate new ideas and identify any remaining issues or holes in data. The affinity diagram is a bottom-up method. Consolidated data may also be used to create a cause-and-effect diagram or a set of personas describing typical users of the proposed system.
In visioning, a cross-functional team comes together to create stories of how new product concepts, services, and technology can better support the user work practice. The visioning team starts by reviewing the data to identify key issues and opportunities. The data walking session is followed by a group visioning session during which the visioning team generates a variety of new product concepts by telling stories of different usage scenarios based on the data collected. A vision includes the system, its delivery, and support structures to make the new work practice successful, but is told from the user's point of view.
After visioning, the team develops the vision in storyboards, capturing scenarios of how people will work with the new system. Understanding the current way of working, its structure and the complete workflow helps the design team address the problems and design the new workflow. Storyboards work out the details of the vision, guided by the consolidated data, using pictures and text in a series of hand-drawn cells.
The User Environment Design captures the floor plan of the new system. It shows each part of the system, how it supports the user's work, exactly what function is available in that part, and how the user gets to and from other parts of the system. Contextual design uses the User Environment Design (UED) diagram, which displays the focus areas, i.e., areas which are visible to the user or which are relevant to the user. Focus areas can be defined further as functions in a system that support a certain type or part of the work. The UED also presents how the focus areas relate to each other and shows the links between focus areas.
Testing the design ideas with paper prototypes or even with more sophisticated interactive prototypes before the implementation phase helps the designers communicate with users about the new system and develop the design further. Prototypes test the structure of a User Environment Design and initial user interface ideas, as well as the understanding of the work, before the implementation phase. Depending on the results of the prototype test, more iterations or alternative designs may be needed.
Contextual design has primarily been used for the design of computer information systems, including hardware, software. Parts of contextual design have been adapted for use as a usability evaluation method and for contextual application design. Contextual design has also been applied to the design of digital libraries and other learning technologies.
Contextual design has also been used as a means of teaching user-centered design/Human–computer interaction at the university level.
A more lightweight approach to contextual design has been developed by its originators to address an oft-heard criticism that the method is too labor-intensive or lengthy for some needs. Yet others find the designer/user engagement promoted by contextual design to be too brief.
((cite web)): CS1 maint: archived copy as title (link))