Interaction Design Theory

Interaction design is the practice of shaping how people and computational things act on each other over time.

12 frameworks, from 1940 to today · Design · Arts & Architecture

still a working view ended · each leads to its entry below

Overview

Interaction design is the practice of shaping how people and computational things act on each other over time1. Its theory asks what makes an interaction good, meaningful, or just: how a person's intentions meet a system's responses, what a device should afford, whose values get built into software, and who gets to decide. The field matters because almost every designed thing now contains behavior—a phone, a ticket machine, a hospital record system—and the quality of that behavior is a design question, not merely an engineering one. This is the history of the ideas practitioners made, argued over, and taught.

Human Factors and the Operator (1940s–1960s)

The earliest strand came from wartime and industrial psychology. Researchers studied how human operators actually performed with machines—how quickly a pilot read a dial, where errors clustered, how fatigue degraded attention. The discipline that formed around this work, human factors or ergonomics, treated the human as a component of a system to be matched to the machine. Its central method was measurement: reaction times, error rates, anthropometric data.

The approach's limitation became clear as machines grew more complex. Matching knobs to hands did not explain why operators misunderstood what a system was doing. The problem was cognitive, not just physical, and the vocabulary of the 1950s had no way to describe it.

Direct Manipulation and the Graphical Interface (1970s–1980s)

The decisive shift came from computing. At Xerox PARC in the 1970s, researchers building the Alto workstation confronted a problem: command-line systems forced users to remember syntax and imagine invisible states. The response was direct manipulation—an idea articulated most influentially by Ben Shneiderman in the early 1980s—in which objects of interest are visible on screen and can be acted on as if directly: you drag a file to a folder rather than typing a move command2. The interface shows the result of an action immediately, and actions are reversible2.

The concrete case is the desktop metaphor itself: icons, windows, a pointer2. Its power was that it let users form a mental model from visible objects rather than from memorized rules. This made computing legible to people who had never programmed, and it set the terms—visibility, immediate feedback, reversibility—that interaction design still uses.

Affordances and the Psychology of Everyday Things (1980s)

Alongside the graphical interface came a theory of how objects communicate their use. The psychologist James J. Gibson had introduced affordance in the 1970s to mean the possibilities for action that an environment offers an animal—a surface affords walking, a handle affords grasping. Donald Norman imported the term into design in his 1988 book The Design of Everyday Things, arguing that good design makes the right action obvious and the wrong one hard13. His famous example: a door with a flat plate that must be pushed, versus one with a handle that invites pulling. When a door needs a sign saying "push," the design has failed.

Norman later distinguished real affordances from perceived affordances and from conventions, a refinement that matters because the term is often used loosely. The idea's contribution was to locate usability in the relationship between person and object rather than in the object alone.

User-Centered Design and Its Methods (1980s–1990s)

The 1980s also produced the framework that organized the field's practice: user-centered design. Norman's laboratory work and the broader usability movement argued that designers should study actual users—their tasks, their errors, their language—before and during design, and test prototypes with them. The methods that followed were empirical: think-aloud usability testing, where a person narrates their attempt to complete a task while an observer notes where they stumble; heuristic evaluation, where experts check an interface against a list of known problems45.

The limitation was that user-centered design tended to treat the user as a fixed entity to be discovered and served. It worked well for well-defined tasks and poorly for settings where the "user" was a whole organization with conflicting needs.

Contextual Design and the Workplace (1990s)

That gap drove contextual design, developed by Hugh Beyer and Karen Holtzblatt and published in 1998. Its core method, contextual inquiry, sends designers into the field to observe and interview people while they work, in their own environment, rather than in a lab6. From those observations the team builds models—of the workflow, the physical setting, the sequence of tasks—and designs against them76. The insight was that work is situated: what people say they do and what they actually do diverge, and only fieldwork catches the difference. This made interaction design answerable to organizational reality, and it fed directly into the participatory strand.

Participatory Design: Users as Co-Designers (1970s onward)

Participatory design began in Scandinavia in the 1970s, in a political context: trade unions and researchers in Norway and Denmark argued that workers affected by new computer systems should help design them. The landmark projects—the Norwegian Iron and Metal Workers Union's collaboration with researchers, and the Swedish DEMOS project on democratic planning—treated design as a negotiation among stakeholders, not a service delivered to passive users. Techniques such as future workshops and low-fidelity prototyping let non-designers make concrete proposals.

The claim was both ethical and practical: people know their own work better than outsiders, and giving them design power produces better systems and fairer outcomes. This strand remains the field's main channel for questions of power and voice.

Experience, Emotion, and the Reflective Turn (1990s–2000s)

By the late 1990s, usability alone seemed insufficient. A system could be efficient and still feel cold or meaningless. Experience-centered design reframed the goal from task completion to the quality of the lived encounter—pleasure, engagement, aesthetics. Researchers drew on pragmatist philosophy and on the idea of flow to describe absorbed use. The practical consequence was attention to the felt texture of interaction: animation, sound, pacing, personality.

A related move was reflective design, articulated by Phoebe Sengers and colleagues in the mid-2000s, which argued that designers should support users in reflecting on their own behavior and the system's assumptions rather than optimizing them toward unexamined goals. The example often cited is the "reflective" thermostat or feedback display that makes a household's energy use visible and debatable rather than merely automated.

Affective computing, pioneered by Rosalind Picard in the 1990s, took a different route: building systems that sense and respond to human emotion through facial expression, voice, or physiological signals. It remains contested—its critics question whether emotion can be reliably inferred from such signals—but it established that feeling is a legitimate object of computational design.

Values, Critique, and Speculation (1990s–2010s)

The question of whose values a system encodes became explicit with value-sensitive design, developed by Batya Friedman and collaborators from the 1990s. Its method is to identify stakeholders, enumerate the values at stake (privacy, autonomy, trust, fairness), and trace how design decisions support or undermine them. A concrete case is the design of web cookies and consent dialogs, where the value of informed consent collides with commercial incentives—value-sensitive design makes that collision visible and arguable rather than accidental.

Critical and speculative design, associated with Anthony Dunne and Fiona Raby from the late 1990s, pushed further: instead of solving problems, design objects and scenarios that provoke debate about possible futures89. Their projects—fictional products, imagined technologies—are not meant to be used but to be argued with. This gave the field a mode of critique distinct from usability.

Feminist and postcolonial critiques entered from the 2000s, arguing that the field's "user" was implicitly a Western, able-bodied, often male figure, and that design methods carried unexamined assumptions about whose knowledge counted. These critiques did not produce a single method so much as a persistent set of questions about standpoint, exclusion, and whose futures get designed.

The Present: Competing Frameworks and Open Questions

Today these strands coexist rather than supersede one another. User-centered and contextual methods remain the working backbone of professional practice, taught in every interaction design program. Participatory and value-sensitive approaches supply the ethical and political vocabulary, increasingly invoked in AI and public-sector design. Experience-centered and reflective design inform work on engagement and wellbeing. Critical and speculative design lives mostly in research and education, where it functions as a check on solutionism.

The open questions are the ones the history keeps returning to: how to design for people whose needs conflict; whether emotion and values can be reliably designed for at all; and who holds authority when designers, users, and institutions disagree about what a system should do. The field's theories are, in the end, competing answers to a single stubborn problem—how to make computational behavior fit human life.

References

  1. Interaction design (introduction, Related disciplines), Wikipedia
  2. Direct manipulation interface, Wikipedia
  3. User-centered design (History), Wikipedia
  4. Think aloud protocol (introduction, History), Wikipedia
  5. Heuristic evaluation, Wikipedia
  6. Contextual inquiry (introduction, History of the method), Wikipedia
  7. Contextual design, Wikipedia
  8. Speculative design, Wikipedia
  9. Critical design (introduction, History), Wikipedia

The frameworks of Interaction Design Theory

Each framework is a way of working the field has used: when it held, and the question it answers.

  1. 1940-1985

    Ergonomics

    How do people perform with machines?

    Fly to its tower in Nousfarer

  2. 1975-Present

    Participatory Design

    Who should decide how technology is designed?

    About Participatory Design
    Participatory design is an approach to designing interactive systems that treats the people who will use a system as active partners in its creation, rather than as passive subjects to be studied or as consumers to be served. Its distinctive organizing idea is that those who will live with the consequences of a design—workers, citizens, patients, community members—have a legitimate and necessary role in deciding what that design should be. The designer does not design for users; the designer designs with them. This is not a style or a set of interface conventions, but a process-oriented commitment to sharing power over design decisions.
    The problem participatory design addresses is twofold. The first is practical: systems designed without genuine input from their users frequently fail to fit the realities of their work and lives. They may be technically sound but organizationally disruptive, or they may solve a problem that was never the real problem. The second is political: design decisions shape who can do what, who has access, and who is excluded. When design authority rests solely with managers, engineers, or outside experts, the resulting system can reinforce existing power imbalances. Participatory design emerged from the conviction that these two problems are inseparable—that good design requires democratizing the design process itself.
    This focus on stakeholder involvement and democratization is what distinguishes participatory design from nearby approaches. User-centered design, for example, also emphasizes understanding users, but it typically does so through observation, interviews, and usability testing, with the designer retaining final authority over the outcome. The user is a source of information; the designer is the expert. Participatory design, by contrast, positions users as co-designers with genuine decision-making power. It is also distinct from value-sensitive design, which analyzes how values are embedded in technology, but does not necessarily require the direct participation of affected stakeholders in the design process itself. Participatory design is less about analyzing values from a distance and more about creating a shared space where different perspectives can negotiate the design together.
    To understand how participatory design works in practice, it helps to learn its core concepts in a natural order. The first concept is stakeholder involvement, the principle that all parties affected by a system—not just end users, but also managers, maintainers, and sometimes customers—should have a voice. The second is genuine participation, which is not the same as being consulted. A useful way to think about this is the idea of a "ladder" of participation, where the lower rungs are forms of tokenism or manipulation, and the higher rungs represent real citizen control over decisions. Genuine participation means the stakeholders' contributions can actually change the design, not merely comment on it after the fact.
    From there, the essential methods follow. Workshops are structured sessions where users and designers work together on design tasks, often using low-fidelity materials like paper, cardboard, or sticky notes to explore ideas without the constraints of working code. Prototyping is central: rather than presenting a finished system for feedback, designers create rough, early versions that users can react to, modify, and build upon. The prototype is not a demonstration but a shared object for thinking. Scenario building and storyboarding help participants imagine future use situations and articulate needs that are hard to express in abstract terms. Throughout, the designer's role shifts from author to facilitator—someone who provides tools and structure for the group's collective creativity, while still taking responsibility for the craft of the final design.
    The intellectual history of participatory design is rooted in Scandinavia in the 1970s, where it grew out of a collaboration between researchers, trade unions, and workers. The context was the introduction of computer systems into workplaces, which workers feared would deskill their jobs, monitor their performance, or eliminate their autonomy. Research projects, most notably the Norwegian Iron and Metal Workers Union project, took an explicitly action-oriented approach: rather than studying workers from the outside, researchers worked directly with union members to develop strategies for influencing the design and use of new computer systems. This "collective resource approach" held that workers had a right to participate in decisions about the technology that would shape their working lives. The movement drew on action research and sociotechnical design, and it carried an explicit political commitment to workplace democracy.
    A landmark conceptual contribution from this period is Sherry Arnstein's 1969 article "A Ladder of Citizen Participation," which provided a lasting vocabulary for distinguishing genuine participation from its counterfeits. Arnstein's ladder ranges from manipulation and therapy at the bottom—where participation is used to educate or placate—through informing, consultation, and placation in the middle, to partnership, delegated power, and citizen control at the top. This framework made it possible to ask a sharp question of any participatory effort: how much real power are the participants actually wielding? The term "participatory design" itself, along with the related "co-design," became widely used in the following decades as the approach spread beyond Scandinavia and beyond the workplace, into community planning, health services, and product design.
    The continuing significance of participatory design lies in its insistence that design is a political act. As interactive systems have moved from the workplace into every corner of daily life, the question of who gets to shape them has only grown more urgent. Participatory design offers a practical answer: build the people who are affected by a system into its design process from the start. Its methods have been taken up in civic technology, public service design, and community-based projects, and its principles inform debates about algorithmic accountability and data justice. While the approach originated in the 1970s, its core insight—that expertise in living with a system is a form of expertise that design cannot do without—remains a vital corrective to the assumption that good design is something experts do to or for others.
    No specialist background is required to understand participatory design. A basic familiarity with how software or other interactive products are built is helpful for appreciating the constraints designers work under, but the framework itself is concerned with processes, relationships, and power, not with technical implementation. The most useful prerequisites are a willingness to take seriously the perspectives of people who are not designers, and an interest in the question of who should have authority over the technologies that shape our lives.
    The 6 concepts its tower teaches
    • Stakeholder Involvement
    • Genuine Participation
    • Designer as Facilitator
    • Participatory Workshops
    • Participatory Prototyping
    • Scenario Building and Storyboarding

    Fly to its tower in Nousfarer

  3. 1981-Present

    Direct manipulation interface

    How can interfaces make actions visible and reversible?

    Fly to its tower in Nousfarer

  4. 1986-Present

    User-Centered Design

    How do we design for users' actual tasks?

    About User-Centered Design
    User-Centered Design (UCD) is a framework of design processes that places the intended user at the center of every stage of product development. Its core premise is that a product should be shaped around the needs, behaviors, and limitations of the people who will use it, rather than forcing users to adapt to the product’s technical capabilities. This approach emerged in the late 1970s and gained prominence through the 1980s, fundamentally shifting how interactive systems were conceived and evaluated. The central question UCD asks is not "What can this technology do?" but rather "What do users need to accomplish, and how can the design make that as intuitive and efficient as possible?"
    The problem UCD addresses is the persistent failure of technology to match human cognition and behavior. Before its widespread adoption, software and hardware were often designed from an engineering perspective, prioritizing system architecture, processing efficiency, and feature sets. This frequently resulted in products that were powerful but opaque, requiring users to memorize complex commands, decipher unclear mappings between controls and outcomes, and adapt to the system's logic rather than their own. UCD emerged as a corrective, arguing that usability is not a cosmetic afterthought but a fundamental requirement. It applies cognitive science principles to design, acknowledging that users have limited working memory, form mental models of how things work, and make errors when feedback is absent or misleading.
    UCD differs from nearby approaches in a crucial way. Participatory Design, which emerged slightly earlier, involves users as active co-designers in the creation process, treating their input as a form of democratic participation. UCD, by contrast, typically treats users as subjects of study—observing, interviewing, and testing them—but the design decisions remain with the professional designer. Similarly, Activity Theory focuses on the broader cultural and historical context of human activity, while UCD concentrates on the immediate interaction between a single user and a specific task. The most important distinction is between UCD and technology-centered design: UCD begins with user research and iterates based on user feedback, whereas technology-centered design begins with a technical capability and seeks applications for it.
    To understand UCD, it is helpful to learn its concepts in a logical sequence. The first concept is user research, which involves gathering data about who the users are, what they want to achieve, and the environment in which they work. This can include interviews, observation, and analysis of existing tasks. The second is usability goals, which are explicit, measurable criteria such as learnability (how quickly a novice can become competent), efficiency (how quickly an expert can perform tasks), and error prevention. The third is iterative design, the practice of designing, testing, and refining in repeated cycles. This is paired with the fourth concept, usability testing, where representative users attempt realistic tasks with a prototype or early version of the product while designers observe where they struggle. The fifth concept is feedback and mapping, drawn from cognitive psychology: the system must provide clear, immediate feedback for every action, and the relationship between controls, actions, and results must be visible and intuitive.
    The intellectual history of UCD is anchored in the work of Donald Norman and his colleagues at the University of California, San Diego. The term "user-centered design" was coined by Rob Kling in 1977, but it was Norman who popularized the concept. His 1986 edited volume, User-Centered System Design: New Perspectives on Human-Computer Interaction, established the framework as a formal approach within human-computer interaction. Norman's 1988 book, The Design of Everyday Things, brought the ideas to a broader audience. In that work, he articulated key principles that remain central to UCD: simplifying task structures so that possible actions are obvious; making things visible, including the system's conceptual model and the results of actions; ensuring correct mappings between intended results and required actions; and exploiting natural constraints to guide behavior. Norman emphasized that good design should make the user's mental model align with the system's actual operation, and he argued that user errors are often the fault of poor design rather than user incompetence.
    The continuing significance of UCD lies in its enduring relevance to modern interactive systems. While the framework originated in the 1980s, its principles have become the foundation for contemporary user experience (UX) design. The emphasis on iterative testing, user research, and usability goals is now standard practice in software development, web design, and mobile application design. UCD also provides a critical lens for evaluating emerging technologies; as artificial intelligence and ubiquitous computing create increasingly complex interactions, the UCD mandate to simplify tasks, provide clear feedback, and respect user mental models remains a necessary corrective. Later frameworks, such as Experience-Centered Design, have expanded the focus beyond usability to include emotional and aesthetic dimensions, but they build upon the UCD foundation rather than replacing it.
    No specialist knowledge is required to understand the core concepts of User-Centered Design. A basic familiarity with how people use computers or mobile devices is helpful, but the framework's principles are drawn from everyday human cognition and can be grasped through simple examples, such as a poorly designed door handle or a confusing microwave interface. The value of UCD lies not in technical expertise but in a disciplined attention to the user's perspective—a skill that can be practiced by anyone who has ever been frustrated by a product and asked, "Why did they design it this way?"
    The 6 concepts its tower teaches
    • Usability Goals
    • User Research
    • Iterative Design
    • Usability Testing
    • Feedback and Mapping
    • Mental Models

    Fly to its tower in Nousfarer

  5. 1988-Present

    Affordance

    How do objects communicate their use?

    Fly to its tower in Nousfarer

  6. 1990-Present

    Contextual Design

    How do we understand work as it is actually done?

    Fly to its tower in Nousfarer

  7. 1995-Present

    Affective Computing

    Can machines sense and respond to emotion?

    Fly to its tower in Nousfarer

  8. 1995-Present

    Experience-Centered Design

    What makes an interaction feel meaningful?

    About Experience-Centered Design
    Experience-Centered Design (ECD) emerged in the mid-1990s as a distinct response to a growing dissatisfaction with the prevailing approaches to human-computer interaction. While earlier frameworks had successfully shifted focus from the machine to the human, ECD’s founders argued that the field had become too narrowly fixated on the user as a cognitive processor—a being defined primarily by goals, tasks, and efficiency metrics. The central problem ECD addresses is that this task-oriented view misses the richer, messier, and more profound ways people actually live with technology. A person does not merely "use" a smartphone; they feel anxiety when its battery dies, joy when a photo resurfaces a memory, and a sense of identity through the communities it connects them to. ECD was built to give designers a framework for engaging with this full, felt quality of interaction.
    The distinctive organizing idea of Experience-Centered Design is that the primary subject of design is not the artifact itself, nor the user’s task performance, but the experience that arises in the encounter between the two. This experience is understood as a holistic, temporal, and deeply subjective phenomenon. It is holistic because it integrates perception, emotion, cognition, and physical action into a single unified whole; it is temporal because it unfolds over time with a beginning, middle, and end; and it is subjective because its meaning is constructed by the individual person living through it. In this view, a design is successful not when it is merely usable, but when it creates a meaningful, coherent, and engaging experience for the person involved.
    To understand ECD, it helps to contrast it with its immediate neighbors. User-Centered Design (UCD), which dominated the 1980s and 1990s, focuses on designing for the user by analyzing their tasks, goals, and cognitive limitations. ECD shares UCD’s commitment to putting people first, but it rejects the reduction of the person to a set of task requirements. Participatory Design emphasizes the democratic involvement of users in the design process itself, treating them as partners in co-creation. ECD values this involvement but is more concerned with the quality of the resulting experience than with the political process of its creation. Value-Sensitive Design focuses on embedding ethical values like privacy, justice, and autonomy into technology. ECD is related in its concern for human well-being, but it is less prescriptive about which values matter and more interested in the phenomenological texture of how values are felt in practice. In short, ECD shifts the unit of analysis from the task (UCD), the process (Participatory Design), or the value (VSD) to the lived experience itself.
    The essential concepts of ECD can be learned in a natural progression, each building on the last. The first and most foundational concept is experience as a phenomenon. This draws on the philosophical tradition of phenomenology, particularly the work of John Dewey and Martin Heidegger, to argue that experience is not a byproduct of interaction but the very substance of it. Dewey’s notion of an "experience" as a complete, meaningful unit—like a satisfying meal or a gripping novel—is central here. The second concept is the holistic triad of user, artifact, and context. ECD insists that experience cannot be located solely in the user’s head, the artifact’s features, or the environment’s constraints; it emerges from the dynamic relationship among all three. A design that is delightful in one context may be frustrating in another, and the same artifact can yield radically different experiences for different people.
    The third concept is the four threads of experience, a framework proposed by ECD pioneers John McCarthy and Peter Wright in their seminal 2004 book Technology as Experience. These threads are the sensual (the visceral, bodily engagement with the technology), the emotional (the feelings and moods that arise), the compositional (the narrative structure and sense of coherence), and the spatio-temporal (the way the experience is situated in time and space). These threads are not separate categories but interwoven dimensions that together constitute the whole experience. The fourth concept is dialogue and meaning-making. ECD holds that experience is not something a designer can directly create; rather, the designer creates the conditions for an experience, and the user actively makes meaning through an ongoing dialogue with the artifact. This shifts the designer’s role from author to choreographer, crafting the possibilities for experience rather than dictating its outcome.
    The intellectual history of Experience-Centered Design is rooted in the broader turn toward phenomenology and pragmatism in human-computer interaction during the 1990s. The field’s most influential figures are John McCarthy and Peter Wright, whose work at the intersection of computer science and the humanities gave ECD its theoretical backbone. Their 2004 book Technology as Experience is widely considered the foundational text, and their subsequent writings, including Experience-Centered Design: Designers, Users, and Communities in Dialogue (2015), extended the framework into practical methodology. Other important contributors include Paul Dourish, whose 2001 book Where the Action Is introduced the concept of embodied interaction, arguing that meaning in interaction arises from our physical, situated engagement with the world. The influence of philosopher John Dewey’s aesthetics and pragmatism is also pervasive, providing the framework with its understanding of experience as a continuous, meaning-laden stream. The framework gained traction through the late 1990s and 2000s as the rise of consumer digital products—from the web to mobile devices—made it increasingly obvious that people were not just using technology but living with it, feeling with it, and forming identities through it.
    The continuing significance of Experience-Centered Design lies in its ability to address the emotional and existential dimensions of technology that purely functional frameworks cannot capture. As interactive systems have become intimate companions—tracking our health, mediating our relationships, and shaping our sense of self—the need to design for experience rather than mere utility has only grown. ECD provides a critical lens for evaluating whether a technology enriches or diminishes the quality of human life, and it offers a vocabulary for articulating why some digital products feel magical while others feel hollow. It also serves as a corrective to the relentless optimization culture of modern tech, reminding designers that efficiency without meaning is a shallow victory. In an era of persuasive design, algorithmic feeds, and immersive environments, the framework’s insistence on the user as a feeling, meaning-making being is more relevant than ever.
    For the reader approaching this framework, no specialist background in philosophy or computer science is required. A basic familiarity with the general concerns of interaction design—usability, user research, and the design process—will be helpful but is not a prerequisite. The most important preparation is a willingness to attend to your own experiences with technology and to take seriously the subjective, emotional, and contextual dimensions of interaction that are often dismissed as "soft" or "unscientific." ECD rewards curiosity about human meaning-making and a tolerance for ambiguity, since it deals with phenomena that resist precise measurement. With that orientation, the framework offers a powerful and humane way of thinking about what it means to design for people.
    The 4 concepts its tower teaches
    • Experience as a Phenomenon
    • Holistic Triad of User, Artifact, and Context
    • Four Threads of Experience
    • Dialogue and Meaning-Making

    Fly to its tower in Nousfarer

  9. 1996-Present

    Value-Sensitive Design

    Whose values are built into technology?

    About Value-Sensitive Design
    Value-Sensitive Design (VSD) is a theoretically grounded approach to designing technology that accounts for human values in a principled and comprehensive manner. It emerged in the late 1980s and early 1990s within the fields of human-computer interaction and information systems design, developed primarily by Batya Friedman and Peter Kahn at the University of Washington. Where most design frameworks of its era focused on usability, efficiency, or user satisfaction, VSD asks a different, more fundamental question: how should we design technologies that honor the values of the people they affect? It treats values not as an afterthought or a constraint, but as a primary design material.
    The problem VSD addresses is that technologies are not value-neutral. Every interactive system, from a social media feed to a hospital scheduling tool, embodies choices about what matters: privacy, autonomy, trust, accountability, or convenience. These choices are often made implicitly by designers who may not recognize the ethical weight of their decisions. VSD provides a method for making those choices explicit and deliberate. It insists that designers have a responsibility to consider not only the direct users of a system but also the indirect stakeholders—people who are affected by a technology without ever touching it. A school surveillance system, for example, affects not just the students being monitored but also their families, teachers, and the broader community.
    The framework is built on a distinctive organizing idea: that values can be investigated and designed for through three interconnected types of inquiry. Conceptual investigations identify who the stakeholders are and which values are implicated in a given design context. Empirical investigations study how people actually experience and interpret those values in practice, often through interviews, observations, or surveys. Technological investigations examine how the properties of the technology itself—its algorithms, data structures, or interface affordances—support or undermine particular values. These three investigations are meant to be iterative, feeding back into one another as the design evolves. A designer might begin with a conceptual analysis of privacy, then conduct empirical studies to see how users understand privacy in a specific context, then prototype a technical feature that supports that understanding, which in turn reveals new conceptual questions.
    To understand VSD, it helps to learn its concepts in a sensible order. First, grasp the distinction between direct stakeholders—people who interact with the system—and indirect stakeholders—people who are affected by it without interacting. Second, understand the idea of value heuristics: a provisional list of values that are commonly implicated in technology design, such as privacy, autonomy, trust, justice, and human welfare. These heuristics are not a rigid checklist but a starting point for asking which values matter in a given context. Third, learn the tripartite method of conceptual, empirical, and technological investigation. Fourth, appreciate the commitment to iterative design: VSD is not a one-pass process but a continuous cycle of reflection and revision. Finally, understand that VSD is proactive rather than reactive. It seeks to anticipate value tensions before a system is deployed, rather than responding to harms after they occur.
    The intellectual history of VSD is closely tied to the broader turn in interaction design toward ethics and social responsibility. It grew out of earlier work in computer ethics and the philosophy of technology, but it distinguished itself by offering a practical, design-oriented method rather than a purely theoretical critique. Friedman and Kahn’s early work in the 1990s established the core framework, and their collaboration with computer scientist Alan Borning on projects like the UrbanSim planning simulation demonstrated how VSD could be applied to complex civic systems. The approach gained traction throughout the 2000s and 2010s, influencing fields as diverse as privacy engineering, robotics, and artificial intelligence. A landmark synthesis appeared in 2019 with the publication of Value Sensitive Design: Shaping Technology with Moral Imagination by Batya Friedman and David Hendry, which articulated the framework’s explicit moral commitments to human well-being, justice, and dignity.
    VSD differs from nearby approaches in interaction design theory in important ways. User-Centered Design focuses on usability and user experience, treating the user’s goals and tasks as the primary design driver. VSD broadens the scope to include values that may not be salient to users in the moment—privacy, for example, is often something people care about abstractly but fail to act on in practice. Participatory Design shares VSD’s concern with stakeholder involvement, but it emphasizes democratic participation in the design process itself, whereas VSD is more focused on the values that should shape the outcome. Activity Theory and Cognitive Systems Engineering analyze how people and technologies form complex systems, but they are primarily descriptive and analytical; VSD is explicitly normative, concerned with how things ought to be. Experience-Centered Design, which emerged around the same time, focuses on the felt quality of interaction, whereas VSD focuses on the ethical quality of the relationship between technology and human life.
    The continuing significance of VSD lies in its relevance to contemporary challenges. As artificial intelligence systems make decisions that affect people’s lives, from loan approvals to medical diagnoses, the question of how to embed values like fairness and accountability into algorithms has become urgent. VSD provides a vocabulary and a method for addressing that question systematically. It has been adapted into approaches like Privacy by Design and Care-Centered Value Sensitive Design, which tailor the general framework to specific domains. Critics have argued that VSD’s value heuristics can be too vague or that it risks imposing the designer’s values on users. These critiques have led to refinements, including a greater emphasis on eliciting values from empirical contexts rather than assuming them in advance. Despite these debates, VSD remains one of the most influential frameworks for thinking about ethics in design, precisely because it refuses to separate the technical from the moral.
    For readers new to interaction design theory, no specialist background is required to engage with VSD. A basic familiarity with how software and digital systems are built is helpful but not necessary. The framework is accessible because it begins with ordinary human concerns—privacy, trust, fairness—and asks how those concerns are shaped by the technologies we create. What is required is a willingness to treat design as a moral activity and to take seriously the idea that the choices made during the design process have consequences for how people live. VSD offers a disciplined way to do that, one that has proven durable across decades of technological change.
    The 6 concepts its tower teaches
    • Value-Sensitive Design
    • Direct and Indirect Stakeholders
    • Value Heuristics
    • Tripartite Method
    • Iterative Design
    • Proactive Approach

    Fly to its tower in Nousfarer

  10. 1998-Present

    Critical and Speculative Design

    How can design provoke debate about possible futures?

    Fly to its tower in Nousfarer

  11. 2005-Present
  12. 2005-Present

    Reflective Design

    How can systems support reflection on behavior?

    Fly to its tower in Nousfarer

How the ideas connect

Each arrow runs from an earlier idea to the later one it shaped. The list below says what passed between them.

ErgonomicsParticipatory DesignDirect manipulation interfaceUser-Centered DesignAffordanceContextual DesignAffective ComputingExperience-Centered DesignValue-Sensitive DesignCritical and Speculative DesignFeminist and Postcolonial Design Crit…Reflective Design

Beyond the field

Where Interaction Design Theory's ideas came from in other fields, and what they led to there: the strongest 12 of 59 links.

A city in Nousfarer: a red-carpeted stair climbing terraces to a crowned tower on an acropolis, more towers round it, forest and snowy mountains beyond.
A city in Nousfarer, the game played in the browser.

Interaction Design Theory is a planet in Nousfarer

Its city has a tower for each of these 12 frameworks. Land, walk in, and climb one concept at a time.

Land on Interaction Design Theory

Related fields

Fields its ideas are linked to

More in Design

See where Interaction Design Theory sits on the Map of Human Knowledge