Loading field map
Participatory Design (PD) is a tradition within human-computer interaction (HCI) and, more broadly, within design research and practice, that centers on the direct involvement of the people who will use a technology or system in the processes of its design and development. Rather than treating users as subjects to be observed, informants to be interviewed, or customers to be satisfied, PD treats them as partners and co-designers. The core commitment is that those who will live with the consequences of a design should have a meaningful say in what it becomes.
The fundamental problem PD addresses is the asymmetry of power and knowledge in technology design. When designers and developers create systems without the active participation of the end-users, they risk building tools that are ill-suited to the actual work, social context, or needs of those users. This can lead to systems that are inefficient, frustrating, or even harmful. More deeply, PD emerged from a concern that technology is not neutral: it embodies values and shapes the distribution of power in the settings where it is introduced. A system that automates decision-making, for instance, can either empower workers by giving them better information or disempower them by removing their discretion.
The stakes are therefore both practical and political. Practically, PD aims to produce better designs by tapping into the tacit, situated knowledge that users have—knowledge that is often invisible to outside observers. Politically, PD is committed to workplace democracy and user autonomy. It asks not only "Does this system work?" but "Who benefits from it, and who is harmed?" and "Who gets to decide?" This dual commitment distinguishes PD from other user-centered approaches that may involve users as sources of information but do not grant them decision-making authority.
PD has its roots in the labor movements of Scandinavia in the 1960s and 1970s. At that time, the introduction of computer systems into workplaces was often a top-down process driven by management, with workers having little say. A series of research projects, most notably in Norway and Denmark, brought together computer scientists, trade unionists, and workers to explore how technology could be designed to support, rather than undermine, worker skills and autonomy. These early projects were explicitly political: they sought to give workers a voice in decisions that affected their working lives.
The term "participatory design" itself came into common use in the 1980s, as these Scandinavian ideas spread to other countries, particularly the United States. In the American context, the political urgency was often less pronounced, and PD was frequently adopted as a pragmatic method for improving usability and user acceptance. This created a lasting tension within the field between its original, explicitly political agenda and a more instrumental, method-focused interpretation. The field has also been shaped by influences from other traditions, including action research in the social sciences, which emphasizes collaborative inquiry and change, and the cooperative design movement, which stressed the importance of designers and users working together in mutual learning.
The field is not a single, unified school but rather a set of related approaches that share a core commitment to user participation while differing in their motivations, methods, and assumptions. These approaches have coexisted and influenced each other, and many practitioners combine elements from several.
The original and most politically explicit approach is the Scandinavian tradition. Its organizing assumption is that workers have a democratic right to influence the technologies that shape their work. The primary problem it addresses is the potential for technology to be used as a tool of managerial control, deskilling work, and eroding worker autonomy.
The methods developed in this tradition emphasize mutual learning between designers and users. Designers must learn about the users' work practices, skills, and values, while users must learn about the technical possibilities and constraints of new technologies. This learning is often facilitated through concrete, hands-on activities. Design games are a notable example: simple, rule-based activities that allow participants to explore design ideas and conflicts in a playful but structured way. Mock-ups and prototypes are also central, as they provide a tangible object that users and designers can react to and modify together. The goal is not just to elicit user preferences but to create a space where users can make informed, consequential choices.
A key limitation of this approach is its resource intensity. Genuine mutual learning takes time, and the process can be difficult to scale to large, distributed, or heterogeneous user groups. Furthermore, its political assumptions may not translate directly to contexts where the labor movement is weaker or where the relationship between users and management is not adversarial.
As PD was imported into North America, it was often reframed as a set of techniques for improving the quality of design outcomes, particularly usability. This approach downplays the political agenda and instead emphasizes the practical benefits of user involvement. The problem it addresses is the failure of conventional design processes to produce systems that meet user needs, leading to costly redesigns, low adoption, and user error.
The methods in this tradition are often more structured and tool-oriented. They include techniques such as contextual inquiry (observing and interviewing users in their own environment), participatory workshops (structured sessions where users generate and evaluate design ideas), and iterative prototyping with user feedback. The designer's role is that of a facilitator and translator, helping to articulate user needs and turn them into design requirements.
This approach has been highly influential in making PD practices accessible to mainstream software development, but it has also been criticized within the field for diluting PD's core values. When user participation is treated as just another method to be applied, it can become tokenistic—users are consulted but do not have real power. The distinction between "participation" as a means to an end and "participation" as a democratic right remains a central point of debate.
A more recent and ongoing development is the expansion of PD from a project-based activity to a long-term, ongoing process. This approach, sometimes described as infrastructuring, recognizes that design does not end with the deployment of a system. Instead, the system becomes part of an evolving infrastructure that users continue to shape through their everyday use and adaptation.
The problem this approach addresses is the mismatch between the short-term, project-based nature of most design efforts and the long-term, evolving nature of the sociotechnical systems that PD aims to create. A system that is "finished" at launch is often already outdated, and users' needs and practices will change over time.
The methods here focus on creating the conditions for ongoing participation. This might involve establishing design communities or living labs where users can continue to contribute ideas and feedback. It also involves designing systems that are flexible and modifiable, allowing users to appropriate and adapt them to their own purposes. This approach draws on insights from actor-network theory and science and technology studies, which emphasize the complex, heterogeneous networks of people, technologies, and institutions that shape how a system actually works in practice.
A limitation of this approach is that it can be difficult to sustain. It requires ongoing resources and institutional commitment, and it blurs the boundaries between design, maintenance, and use. It also raises questions about accountability: if users are co-designers of an evolving system, who is responsible when something goes wrong?
The contemporary landscape of PD is characterized by a broadening of its scope and a deepening of its methods. While the workplace remains an important domain, PD is now applied to a wide range of contexts, including healthcare, education, civic technology, and community development. This expansion has brought new challenges, such as how to involve users who are not easily reachable, such as marginalized or vulnerable populations, and how to address issues of power and inequality that extend beyond the workplace.
Several durable themes continue to shape the field. One is the ongoing tension between the political and the pragmatic. Some practitioners argue that PD must retain its critical edge, challenging existing power structures, while others see it primarily as a set of tools for better design. This is not a settled debate, and the field is likely to remain pluralistic.
Another theme is the question of scale. Many of PD's most successful methods were developed for small, co-located groups. How to scale these methods to large, distributed, or online communities is an open problem. Some researchers are exploring the use of digital tools to support remote participation, while others are developing methods for "scaling down" to work with very small groups in depth.
A third theme is the relationship between PD and data. As systems become increasingly data-driven, questions arise about who owns the data, who gets to interpret it, and how data can be used to support, rather than undermine, user agency. PD is beginning to engage with these questions, exploring how users can participate not just in the design of interfaces but in the design of the algorithms and data models that increasingly govern their lives.
Finally, the field continues to grapple with its own methods. There is a growing interest in reflective practice—the systematic examination of how PD is actually done, including its failures and unintended consequences. This self-critical stance is a sign of the field's maturity, as it seeks to understand not only how to do PD but also when it is appropriate, what it can and cannot achieve, and how to do it more honestly and effectively.
In sum, participatory design is best understood not as a fixed set of techniques but as a persistent commitment to the idea that design is a social and political act. Its central question—who gets to shape the technologies that shape us—remains as relevant today as it was in the factory floors of Scandinavia half a century ago. The field's enduring contribution to HCI is not any single method but the insistence that the people who live with technology must have a hand in making it.