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. 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: Flow model – represents the coordination, communication, interaction, roles, and responsibilities of the people in a certain work practice Sequence model – represents the steps users go through to accomplish a certain activity, including breakdowns Cultural model – represents the norms, influences, and pressures that are present in the work environment Artifact model – represents the documents or other physical things that are created while working or are used to support the work.

About this result
This page is automatically generated and may contain information that is not correct, complete, up-to-date, or relevant to your search query. The same applies to every other page on this website. Please make sure to verify the information with EPFL's official sources.
Related courses (2)
CS-486: Interaction design
This course focuses on goal-directed design and interaction design, two subjects treated in depth in the Cooper book (see reference below). To practice these two methods, we propose a design challenge
CS-491: Introduction to IT consulting
This course is an introduction to the alignment of enterprise needs with the possibilities offered by Information Technology (IT). Using a simulated business case, we explore how to define the require
Related lectures (8)
Enterprise and Service-Oriented Architecture
Explores solutions for business and IT alignment, emphasizing key learning points and the importance of contextual inquiry.
Enterprise and Service-Oriented Architecture: Apprenticing With the Customer
Covers active experimentation, contextual design, and stakeholder engagement in business/IT alignment.
Enterprise and Service-Oriented Architecture: Solutions for Business IT Alignment
Explores solutions for business IT alignment through enterprise and service-oriented architecture.
Show more
Related publications (8)
Related concepts (2)
User-centered design
User-centered design (UCD) or user-driven development (UDD) is a framework of process (not restricted to interfaces or technologies) in which usability goals, user characteristics, environment, tasks and workflow of a product, service or process are given extensive attention at each stage of the design process. These tests are conducted with/without actual users during each stage of the process from requirements, pre-production models and post production, completing a circle of proof back to and ensuring that "development proceeds with the user as the center of focus.
Usability
Usability can be described as the capacity of a system to provide a condition for its users to perform the tasks safely, effectively, and efficiently while enjoying the experience. In software engineering, usability is the degree to which a software can be used by specified consumers to achieve quantified objectives with effectiveness, efficiency, and satisfaction in a quantified context of use. The object of use can be a software application, website, book, tool, machine, process, vehicle, or anything a human interacts with.

Graph Chatbot

Chat with Graph Search

Ask any question about EPFL courses, lectures, exercises, research, news, etc. or try the example questions below.

DISCLAIMER: The Graph Chatbot is not programmed to provide explicit or categorical answers to your questions. Rather, it transforms your questions into API requests that are distributed across the various IT services officially administered by EPFL. Its purpose is solely to collect and recommend relevant references to content that you can explore to help you answer your questions.