Contextual Design¶
Beyer, H., & Holtzblatt, K. (1998). Contextual Design: Defining Customer-Centered Systems. Morgan Kaufmann.
Cited by¶
6 citations across 6 artifacts.
Each citation links to the sentence it supports in the citing article.
Primes¶
- Emic And Etic
- The emic description is how users describe the tool in their own task language and mental models, gathered by contextual inquiry and interviews; its closure condition is competence — a user can confirm or reject whether a described mental model is theirs.
This sourceEstablishes contextual inquiry for eliciting users' own task language and mental models (emic), coordinated with analyst-side usability and behavior analysis (etic).
- The emic description is how users describe the tool in their own task language and mental models, gathered by contextual inquiry and interviews; its closure condition is competence — a user can confirm or reject whether a described mental model is theirs.
Domain-specific¶
- Fieldnotes
- In design and UX research, contextual inquiry imports the fieldnotes discipline into product development
This sourceBeyer and Holtzblatt's method of observing people at their work, through Contextual Inquiry, to shape product and system design.
Supported in partVerified against the source
- In design and UX research, contextual inquiry imports the fieldnotes discipline into product development
Mechanisms¶
- Contextual Inquiry
- The distinguishing stance is master–apprentice: the user leads as the expert doing their own work, and the researcher follows as an apprentice who interrupts only to ask why something is done a certain way, in the moment it is done.
This sourceContextual inquiry uses a master-apprentice relationship in which the customer performs real work as expert and the interviewer observes and asks questions in context.
- The distinguishing stance is master–apprentice: the user leads as the expert doing their own work, and the researcher follows as an apprentice who interrupts only to ask why something is done a certain way, in the moment it is done.
- Contextual Inquiry Note
- This is the master-apprentice model at the heart of contextual inquiry: the practitioner leads, the researcher learns.
This sourceFrames contextual inquiry as a master–apprentice relationship in which the practitioner demonstrates the work and the interviewer learns from it.
- This is the master-apprentice model at the heart of contextual inquiry: the practitioner leads, the researcher learns.
- Operator Shadowing and Contextual Inquiry
- - Shadow real work, in context. The inquirer observes the operator during actual tasks and asks about decisions as they happen, not in a later interview stripped of the situation — a master–apprentice stance in which the operator narrates and the inquirer learns.
This sourceContextual inquiry observes work in its real setting and uses a master-apprentice partnership to discuss decisions as they occur.
- - Shadow real work, in context. The inquirer observes the operator during actual tasks and asks about decisions as they happen, not in a later interview stripped of the situation — a master–apprentice stance in which the operator narrates and the inquirer learns.
- User Research Synthesis
- Using affinity diagramming — the KJ method of grouping raw observations into themes — they cluster what they see, then triangulate: an interviewee's complaint that "I couldn't invite my team yet" is checked against a spike in tickets at the same step and a sharp drop-off in the recordings at exactly that screen.
This sourceDescribes affinity diagramming as organizing contextual-interview observations into hierarchical themes.
- Using affinity diagramming — the KJ method of grouping raw observations into themes — they cluster what they see, then triangulate: an interviewee's complaint that "I couldn't invite my team yet" is checked against a spike in tickets at the same step and a sharp drop-off in the recordings at exactly that screen.
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Read against the text for 1 of 6 citations: 1 supported in part. Each verdict is shown under its citation below, with what in the work backs the sentence.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 4 other ways.
- https://books.google.com/books/about/Contextual_Design.html?id=T8pcH4QjATkC ×1
- https://books.google.com/books?hl=en&id=sVKuMvaFzjQC&pgis=1 ×1
- https://search.worldcat.org/title/37211180 ×1
- https://search.worldcat.org/title/contextual-design-defining-customer-centered-systems/oclc/37792315 ×1
Registry ID ref:b329c093c271 · see in the full table