Loading field map
Interaction design emerged in the 1990s as a distinct subfield of Human-Computer Interaction, but from the start it was torn by a fundamental question: what should design optimize for? Some argued for efficiency and usability, measured through task completion and error rates. Others insisted that meaning, experience, and democratic participation mattered more. Still others believed design should provoke, speculate, or make ethical values explicit. These competing visions produced a family of frameworks that continue to shape how interactive systems are conceived, built, and evaluated.
The 1990s saw two frameworks arise simultaneously, each offering a different answer to the question of who should control design. User-Centered Design (UCD) placed the individual user at the center of an iterative process: designers studied users' tasks, built prototypes, tested them, and refined based on feedback. Its strength was its practical focus on usability, and it quickly became the dominant approach in industry. But UCD treated users as informants rather than decision-makers. Participatory Design (PD), rooted in Scandinavian workplace democracy, challenged that assumption. PD insisted that users should be co-designers, not just test subjects, and that design decisions should be made collectively. Where UCD optimized for efficiency, PD optimized for democratic legitimacy. The two frameworks coexisted throughout the 1990s and beyond, but they never fully reconciled: UCD's expert-driven iteration and PD's political commitment to user empowerment remain in tension today.
By the late 1990s, a growing dissatisfaction with task-focused usability opened space for a broader concern: experience. Experience-Centered Design (ECD) drew on pragmatist philosophy, particularly John Dewey's theory of experience, to argue that interaction design should address the whole of lived experience—emotional, aesthetic, temporal, and social—not just cognitive task performance. ECD treated experience as the primary unit of design, not a byproduct of usability. Around the same time, User Experience Design (UXD) emerged as a more industry-friendly translation of similar insights. UXD adopted the language of experience but operationalized it through methods like journey mapping, personas, and satisfaction metrics. The two frameworks share a commitment to experience, but they diverge in depth: ECD remains philosophically grounded and research-oriented, while UXD has become the dominant industry framework, often reduced to a set of tools for improving customer satisfaction. Both remain active, but their relationship is one of productive tension—ECD critiques UXD's tendency to instrumentalize experience, while UXD accuses ECD of being impractical at scale.
The early 2000s brought three frameworks that each challenged the individual-user focus of UCD and UXD, but in different ways. Activity-Centered Design (ACD) drew on activity theory to argue that human action is always mediated by tools, communities, and cultural norms. Instead of designing for a solitary user, ACD analyzed the entire activity system—the subject, object, tools, rules, community, and division of labor—and designed to support the activity as a whole. Embodied Interaction (EI) took a different tack, arguing that cognition is not just in the head but distributed across the body and the environment. EI insisted that interaction design must account for physical movement, spatial awareness, and bodily skill, not just visual and cognitive processing. Systems Design (SD) broadened the unit of analysis further, treating interactive systems as socio-technical wholes where technology, people, organizations, and work practices are interdependent. SD emphasized that design interventions ripple through the entire system, often with unintended consequences. These three frameworks share a rejection of the isolated user, but they differ in their analytical focus: ACD on mediated activity, EI on embodied cognition, and SD on organizational and technical interdependence. They coexist today as complementary lenses, each better suited to different design problems.
As interaction design matured, practitioners began to notice recurring solutions to common problems. Interaction Design Patterns (IDPs) emerged as a way to capture and share these solutions in a reusable form—a pattern describes a problem, its context, and a proven solution. IDPs drew inspiration from Christopher Alexander's pattern language in architecture and from software design patterns. Unlike UCD's iterative testing, which discovers solutions through empirical trial and error, IDPs codify solutions that have already been validated across multiple projects. This made them a practical tool for accelerating design work and for building shared vocabulary across teams. IDPs did not replace UCD; rather, they provided an infrastructure that UCD practitioners could use to avoid reinventing the wheel. Today, IDPs remain a staple of UX practice, though they are often embedded in design systems and component libraries rather than treated as a standalone framework.
Around 2005, a cluster of frameworks emerged that questioned whether design should serve users at all—at least in the conventional sense. Critical Design (CD) used design artifacts to critique existing social, cultural, and technological arrangements. Instead of solving problems, CD aimed to provoke reflection and debate. Speculative Design (SD) shared this critical impulse but oriented toward the future: it created fictional yet plausible scenarios and artifacts to explore possible futures, often as a way to challenge assumptions about technological progress. Value-Sensitive Design (VSD) took a more constructive approach. VSD argued that design is never value-neutral and that designers should explicitly identify and integrate human values—such as privacy, autonomy, and justice—into the design process from the start. VSD provided a structured methodology: conceptual investigations to identify relevant values, empirical investigations to understand stakeholders' perspectives, and technical investigations to analyze how design features support or undermine those values. These three frameworks form an ethical-critical cluster, but they diverge in orientation: CD provokes, SD imagines, and VSD builds. CD and SD often target academic and gallery audiences, while VSD has been adopted in research contexts where ethical analysis is required, such as healthcare and AI design. All three remain active, and they have pushed the field to recognize that design is never merely technical—it is always ethical and political.
Today, no single framework dominates interaction design. In industry, User Experience Design is the most widely adopted framework, often combined with User-Centered Design's iterative methods and Interaction Design Patterns' reusable solutions. Participatory Design has found a home in civic tech, community-based design, and open-source projects, where democratic participation is a core value. In research, Experience-Centered Design, Activity-Centered Design, Embodied Interaction, and Systems Design each have dedicated communities, and Value-Sensitive Design is increasingly used in projects involving AI ethics and data privacy. Critical Design and Speculative Design remain influential in design education and in HCI's more experimental venues.
The leading frameworks agree on one thing: design should be human-centered in some sense. But they disagree sharply on what "human-centered" means. For UXD and UCD, it means satisfying user needs efficiently. For PD, it means giving users political power. For ECD, it means attending to the richness of lived experience. For VSD, it means upholding ethical values. For CD and SD, it means questioning whether "satisfying users" is even the right goal. This pluralism is both the field's greatest strength—it offers multiple tools for different problems—and its ongoing challenge: there is no unified theory of interaction design, and practitioners must navigate competing commitments every time they design. The frameworks do not resolve into a single story; they remain in living disagreement, and that disagreement is what keeps the field alive.