Critical Hci

Critical HCI is the part of human–computer interaction that treats design as a site of values, power, and consequence rather than only of usability and efficiency.

14 frameworks, from 1970 to today · Human Computer Interaction · Computer Science

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

Overview

Critical HCI is the part of human–computer interaction that treats design as a site of values, power, and consequence rather than only of usability and efficiency1. Where mainstream HCI asks whether a system works well for its user, critical HCI asks who was imagined as the user, whose interests the design serves, what it makes harder to imagine, and who bears the costs. Its practitioners build things—prototypes, workshops, design methods, analytic frameworks—and they also argue about what counts as a good system at all. The stakes are concrete: a welfare algorithm, a persuasive app, a "smart" device, or a hiring tool each encodes assumptions about people that can help or harm them, and critical HCI is the tradition that tries to surface and contest those assumptions before and after they ship.

Situated action and the turn away from the plan (1980s–early 1990s)

The intellectual seed of critical HCI was an argument about how people actually act. Cognitive HCI of the 1980s modeled users as information processors following plans and goals2. In 1987 Lucy Suchman, an anthropologist at Xerox PARC, published Plans and Situated Actions, based on video studies of people using a photocopier's help system. Her finding: people did not follow the instructions; they improvised, reading the situation and the machine's responses moment by moment. Plans, she argued, are resources people use within a situation, not the cause of their action.

This "situated action" view mattered because it undercut the idea that a designer could fully specify use in advance. If action is contingent on circumstance, then design is always incomplete and the user is always a co-producer of what the system becomes. The same years brought participatory design from Scandinavia, where trade-union-linked researchers had since the 1970s worked with workers to shape the computer systems introduced into their workplaces—the UTOPIA project with Swedish and Danish newspaper printers being the best-known case. Its principle was that the people affected by a system should have real say in designing it, not be consulted after the fact3. Together, situated action and participatory design gave critical HCI its two early commitments: use is local and emergent, and design is political.

Values enter the design process (1990s)

The next move was to make values explicit. In the 1990s Helen Nissenbaum argued that technical systems embody political and moral values whether or not their designers intend it, and Batya Friedman and colleagues developed value-sensitive design (VSD), formalized in a 2006 book with Peter Kahn and Alan Borning. VSD proposed a three-part method: conceptual investigation of the values at stake, empirical study of how people actually hold them, and technical investigation of how design supports or undermines them14. A classic illustration is informed consent online—how a system's defaults and flows either enable or erode a user's ability to say no. VSD's contribution was to give designers a vocabulary and procedure for treating values as design requirements rather than afterthoughts.

Critical and reflective design: making the argument visible (mid-2000s)

Around the mid-2000s a group of researchers pushed further, arguing that HCI's default goal—make things easy and pleasant—was itself a value choice that foreclosed dissent. Anthony Dunne and Fiona Raby's critical design (developed through the 1990s and 2000s, notably in their 2001 book Design Noir) used provocative objects—a "digital seedbed," a radio that broadcasts only when someone nearby is moving—to make people question the assumptions built into everyday electronics. These were not products but probes: objects meant to provoke thought rather than serve a use.

In HCI proper, Phoebe Sengers and Bill Gaver organized a 2003 workshop on "ambiguity as a resource for design," and in 2005 Sengers, Kirsten Boehner, Shay David, and Joseph Kaye proposed reflective design, which asked systems to support users in reflecting on their own values and behavior rather than simply being efficient. The same current produced speculative design, closely associated with Dunne and Raby's later work, which imagines alternative futures—often near-future scenarios—to open debate about where technology is heading. These approaches shared a conviction that design's job includes asking "what if" and "what else," not only "what works."

Sustainability and the politics of consumption (mid-2000s onward)

A parallel strand turned critique toward material consequences. Sustainable interaction design, articulated by Eli Blevis in a widely cited 2007 paper, argued that HCI had ignored the environmental footprint of devices and the consumption patterns interfaces encourage. Blevis framed design as a matter of choosing among "sustainable" and "unsustainable" interactions—repair, reuse, and durability versus constant replacement. This connected critical HCI to questions of waste, energy, and the political economy of upgrade cycles, and it broadened the field's sense of what a design decision costs.

Race, gender, and the politics of the field itself (2010s)

The 2010s brought identity and power to the center. Feminist HCI was named in a 2010 paper by Shaowen Bardzell, who argued that HCI's methods and metaphors carried gendered assumptions—about the rational user, about "mastery" of a system—and that feminist theory offered resources for designing otherwise. Bardzell's 2010 survey with Elizabeth Churchill, "Feminism and HCI," mapped the territory. The approach drew on standpoint theory (knowledge is shaped by social position) and on the ethics of care, which treats relationships and dependency as central rather than marginal. Critical race theory in HCI followed, with researchers examining how interfaces and algorithms encode racial bias and how the field's own demographics and defaults exclude. Decolonizing design extended the critique globally, questioning whose knowledge and whose users count as the norm and arguing that design methods exported from wealthy institutions can erase local practices.

Dark patterns and algorithms as interfaces (2010s)

Two developments showed critical HCI's analytic tools turning on the industry itself. In 2010 Harry Brignull coined dark patterns for interface designs that trick users—subscriptions that are easy to start and hard to cancel, confirm-shaming dialogs, hidden costs5. The concept gave researchers and regulators a name for manipulation built into ordinary screens, and it has since entered consumer-protection law in several jurisdictions. Meanwhile, as recommendation feeds and ranking systems became the dominant surface of computing, researchers argued that algorithms function as interfaces: what a user encounters is shaped by a model they cannot see, so the critical questions of transparency, agency, and accountability moved from the screen to the system behind it.

Where critical HCI stands now

Today critical HCI is less a single school than a set of overlapping commitments that run through the field. Value-sensitive design and participatory design are taught as standard methods; feminist HCI, critical race approaches, and decolonizing design have pushed questions of positionality into mainstream venues; dark patterns are a recognized research and policy topic; and speculative and critical design are used in industry and public-sector foresight work. The open questions are live ones: how to make critique actionable without being absorbed as just another design service; how to evaluate speculative work whose value is provocation rather than use; and how to hold algorithmic systems accountable when their behavior is learned rather than authored. What unites the tradition is the conviction that the most important design question is not whether a system works, but for whom, at whose expense, and toward what kind of world.

References

  1. Human–computer interaction (Goals for computers, Methodologies), Wikipedia
  2. Feminist HCI (History), Wikipedia
  3. Participatory design, Wikipedia
  4. Value sensitive design, Wikipedia
  5. Dark pattern, Wikipedia

The frameworks of Critical Hci

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

  1. 1970-Present

    Participatory Design

    Who should have a say in designing a system?

    About Participatory Design
    Participatory design is a framework within critical HCI that begins with a simple but radical premise: the people who will live with a technology should have a genuine hand in shaping it. It is not a design style, a set of visual guidelines, or a usability method. It is a stance about who holds power in the design process. Where mainstream HCI treats the "user" as a subject to be studied, measured, and accommodated, participatory design treats people as co-designers, partners, and decision-makers. The core organizing idea is that design is a political act, and that the legitimacy of a design outcome depends on the participation of those it affects.
    The problem participatory design addresses is twofold. First, there is an epistemic problem: designers and researchers do not have complete knowledge of the contexts, practices, and values of the people who will use a system. No amount of observation or user testing can fully substitute for the lived expertise of workers, citizens, or patients. Second, there is a political problem: when design decisions are made exclusively by managers, engineers, or outside experts, the resulting technology can reinforce existing power imbalances, extract labor more efficiently, or simply ignore the needs of the most vulnerable stakeholders. Participatory design emerged to challenge the assumption that technology is a neutral tool delivered to passive recipients. Instead, it insists that the design process itself is a site where power is exercised, and that this power should be shared.
    This distinguishes participatory design from nearby approaches in critical HCI. Value-Sensitive Design, which follows it chronologically, asks designers to consider human values like privacy, justice, and autonomy as a conceptual checklist during design. Participatory design, by contrast, does not begin with a predefined list of values; it begins with a process of collective inquiry and negotiation. Speculative and Critical Design uses provocative artifacts to question assumptions about the future, often with little or no involvement from the people who might inhabit that future. Participatory design is grounded in the present, in concrete workplaces and communities, and it insists on the direct involvement of those people. Feminist HCI shares participatory design's concern with power and marginalization, but it is primarily a critical lens for analyzing and guiding design, whereas participatory design is a practical methodology with a specific historical commitment to democratic decision-making.
    To understand participatory design, it helps to learn its concepts in a logical order. Start with the idea of stakeholders—everyone who is affected by a design, not just the direct users. This includes workers, managers, customers, and sometimes the broader public. Next comes genuine participation, which is not the same as consultation. Sherry Arnstein's 1969 "Ladder of Citizen Participation" is a foundational reference here: it distinguishes between manipulation, therapy, and informing (which are non-participation or tokenism) and partnership, delegated power, and citizen control (which are genuine participation). Participatory design aims for the upper rungs of this ladder.
    From there, learn about the collective resource approach, a term from the Scandinavian tradition. This approach treats workers' knowledge and labor as a resource that should be mobilized in design, not extracted from them. It is closely tied to action research, a methodology where researchers work with a community to solve problems and create change, rather than studying them from a distance. The practical techniques of participatory design follow from these principles: co-design workshops where stakeholders and designers sketch, prototype, and discuss together; prototyping as a shared activity rather than a designer-only deliverable; and organizational games or other structured activities that help participants articulate their work practices and aspirations. A crucial concept is the division of labor between designers and participants: designers do not abdicate their responsibility. As Wendy Mackay and Michel Beaudouin-Lafon put it, a common misconception is that participatory design means leaving design entirely to users. In reality, designers bring their craft, while participants bring their expertise; the skill lies in facilitating a productive exchange.
    The intellectual history of participatory design is rooted in Scandinavia in the 1970s, and this is its defining period. It grew out of a political context where trade unions were powerful and where there was a strong social democratic commitment to workplace democracy. The Norwegian Iron and Metal Workers Union (NJMF) project in the early 1970s is a seminal case: researchers worked directly with union members to develop computer applications that would support workers' interests, rather than simply increasing managerial control. This project marked a shift from studying workers to working with them. The broader Scandinavian movement drew on two intellectual traditions: sociotechnical design, which argues that technical and social systems must be designed together, and action research, which emphasizes collaborative inquiry for social improvement. The 1971 Design Research Society conference in Manchester, UK, on "Design Participation," helped spread these ideas internationally, and the 1960s and 1970s also saw parallel movements in architecture and urban planning, where citizens demanded a voice in the design of their built environment. Participatory design in HCI is thus one branch of a much wider democratic turn in design.
    The key figures are well established. Sherry Arnstein, though not an HCI researcher, provided the conceptual vocabulary of participation with her 1969 ladder. In the Scandinavian systems design tradition, researchers like Kristen Nygaard and Olav Terje Bergo were central to the NJMF project, and later scholars such as Pelle Ehn and Susanne Bødker developed and codified participatory design methods in the 1980s and 1990s. Ehn's work, in particular, connected participatory design to theories of language games and democracy, arguing that design is a process of creating shared understanding through practical activity. These figures established the core curriculum of participatory design within its dominant period, from 1970 through the mid-1990s. After 1996, Value-Sensitive Design emerged as a successor framework, and participatory design continued as a living tradition, but its foundational concepts and canonical works belong to this earlier period.
    The continuing significance of participatory design in critical HCI is substantial. It remains one of the few frameworks in the field that is explicitly committed to shifting power, not just analyzing it. In an era of large-scale data systems, algorithmic decision-making, and AI, the question of who gets to shape technology is more urgent than ever. Participatory design offers a practical, tested answer: build the design process around the people who will be affected. It has been applied beyond the workplace to civic technology, health services, community development, and the design of public infrastructure. Its methods have been adapted to address issues of marginalization, such as designing with disabled users, elderly populations, or communities facing digital divides. While later frameworks like Feminist HCI and Postcolonial and Decolonial Computing have deepened the critique of power, participatory design provides the methodological backbone for acting on that critique.
    For the reader, no specialist knowledge is required to understand participatory design. A basic familiarity with the idea that design involves choices and trade-offs is helpful, but the framework's concepts are accessible and grounded in everyday experience. The main prerequisite is a willingness to question the default assumption that experts know best. If you have ever been in a meeting where a decision was made about a tool you would have to use, without being asked, you already understand the problem participatory design addresses. The framework's contribution is to offer a disciplined, principled way of doing things differently: not designing for people, but designing with them.
    The 8 concepts its tower teaches
    • Stakeholders
    • Genuine Participation
    • Collective Resource Approach
    • Action Research
    • Co-design Workshops
    • Prototyping
    • Organizational Games
    • Division of Labor

    Fly to its tower in Nousfarer

  2. 1987-Present

    Situated Action

    How do people actually act with technology?

    Fly to its tower in Nousfarer

  3. 1996-Present

    Value-Sensitive Design

    How can values be built into design?

    Fly to its tower in Nousfarer

  4. 1999-Present

    Critical Design

    How can design provoke critical thought?

    Fly to its tower in Nousfarer

  5. 2005-Present

    Reflective Design

    How can systems support users' reflection?

    Fly to its tower in Nousfarer

  6. 2005-Present

    Speculative Design

    What alternative futures could technology bring?

    Fly to its tower in Nousfarer

  7. 2007-Present

    Sustainable Interaction Design

    How can design reduce environmental harm?

    Fly to its tower in Nousfarer

  8. 2010-Present

    Dark pattern

    How do interfaces trick and manipulate users?

    Fly to its tower in Nousfarer

  9. 2010-Present

    Feminist HCI

    How do gender assumptions shape technology design?

    Fly to its tower in Nousfarer

  10. 2015-Present

    Algorithmic Accountability

    Who is responsible when algorithms cause harm?

    Fly to its tower in Nousfarer

  11. 2015-Present

    Algorithms as Interfaces

    How do unseen algorithms shape what users encounter?

    Fly to its tower in Nousfarer

  12. 2015-Present

    Critical Race Theory in HCI

    How do interfaces and algorithms encode racial bias?

    Fly to its tower in Nousfarer

  13. 2015-Present

    Decolonizing Design

    Whose knowledge and users count as the norm?

    Fly to its tower in Nousfarer

  14. 2018-Present

    Ethics of Care in HCI

    How can design support relationships and care?

    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.

Participatory DesignSituated ActionValue-Sensitive DesignCritical DesignReflective DesignSpeculative DesignSustainable Interaction DesignDark patternFeminist HCIAlgorithmic AccountabilityAlgorithms as InterfacesCritical Race Theory in HCIDecolonizing DesignEthics of Care in HCI

Beyond the field

Where Critical Hci's ideas came from in other fields, and what they led to there: the strongest 12 of 49 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.

Critical Hci is a planet in Nousfarer

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

Land on Critical Hci

Related fields

Fields its ideas are linked to

More in Human Computer Interaction

See where Critical Hci sits on the Map of Human Knowledge