Source: Comprehensive Guide to Participatory Design in Human-Computer Interaction (SIGCHI literature review, 2014–2024)
Difficulty: Intermediate to Advanced
Prerequisites: Parts 1 and 2 of these notes (Foundations and PD in Practice). You need the four core dimensions and the participant roles before tackling this material.
Tags: participatory design, PD, HCI, challenges, misconceptions, power imbalances, tokenism, Western-centric bias, depoliticisation, future directions, systemic change, cultural diversity, deployment gap
This final set of notes covers the critical perspective on PD: where current practice falls short, what people commonly get wrong about it, and what the research community recommends for the future. This is the material that separates a descriptive exam answer ("PD involves users in design") from a strong critical one ("PD's democratic aspirations are frequently undermined by X, Y, and Z"). If your course involves essay-format assessment, this section is particularly worth knowing.
Current PD practice in HCI faces persistent problems: a focus on short-term issues over long-term deployment, Western-centric bias in the research base, superficial application of PD principles, and unresolved power imbalances. Common misconceptions include equating PD with workshops and ignoring its political commitment. The field's recommended direction involves broader stakeholder involvement, genuine democratic participation, deployment of real systems, and expansion beyond Western contexts.
Tokenistic participation
Involvement that has the appearance of inclusion but gives participants no meaningful influence over outcomes. Think of it as being invited to the meeting but having no say in the decision.
Western-centric bias
The tendency for research and practice to be dominated by perspectives, methods, and contexts from the US, UK, and Western Europe, potentially overlooking other cultural approaches. In simple terms, most of the published PD studies come from a narrow slice of the world, which limits how generalisable the findings are.
Deployment gap
The observed pattern where PD projects often remain at the ideation or exploration stage without progressing to functional, deployed systems that benefit users in practice. Think of it as doing all the design work but never shipping the product.
Power imbalance (in PD)
A situation where certain participants (typically professional designers, researchers, or funders) hold significantly more influence over the process and its outcomes than others (typically end-users or community members). In simple terms, some voices carry more weight than others, even when the stated goal is equality.
Productive conflict
The idea that diverse perspectives and constructive disagreements within PD projects can drive better, more democratic outcomes, rather than being something to avoid. Think of it as healthy debate that sharpens the design rather than derailing it.
The literature review identified several recurring problems in how PD is practised within HCI:
Short-term focus, limited deployment
Many PD projects concentrate on immediate issues and stop at the ideation or exploration stage
Functional systems that directly empower users through real-world deployment are comparatively rare
This undermines PD's goal empowerment dimension
Shallow stakeholder engagement
Most projects engage at the individual or community level
Collaborations involving government, large-scale institutions, or cross-sector partnerships remain scarce
This limits PD's capacity to drive systemic change
Western-centric bias
The majority of published PD studies originate in the US and UK
Non-Western perspectives, local contexts, and culturally specific approaches to participation are underrepresented
This raises questions about the generalisability of PD findings and methods
Superficial application of PD principles
Some projects label themselves as PD when they amount to a single workshop or ideation session
The holistic, iterative, and politically committed nature of PD gets lost
This dilutes the concept and makes it harder to compare studies meaningfully
Power imbalances and exploitation
Participation can be tokenistic, with users invited to contribute but given no real decision-making power
Commercial contexts may use PD language to extract user insights for profit without genuinely empowering participants
Power dynamics between researchers and community participants often go unexamined
These are the mistakes students (and practitioners) most commonly make when thinking about PD:
Overlooking the political commitment
Labelling a practice as PD without ensuring genuine user influence or democratic decision-making
PD without its political dimension is closer to conventional user-centred design
The political commitment (democracy and empowerment) is what distinguishes PD from other participatory methods
Equating PD with workshops or ideation
PD is a holistic, iterative, and politically grounded approach that spans the full design lifecycle
A single brainstorming session does not constitute PD, even if users are present
The iterative and deployment dimensions are essential
Introducing unnecessary jargon
Terms like "iterative participatory design" are redundant (PD is inherently iterative) and can dilute the concept
Precision in terminology matters when writing about PD
Ignoring systemic power dynamics
Failing to recognise how institutional power, social inequalities, and funding structures shape who participates, how they participate, and whose voice counts
A PD project can reproduce the very inequalities it claims to address if power dynamics are not acknowledged and managed
Mutual learning is the dimension most closely tied to knowledge exchange. The literature identifies five categories of knowledge that flow between participants:
User practices: workflow, attitudes, power dynamics within the user's own context
Technology options: capabilities, limitations, and how users perceive existing or proposed technologies
New systems: design concepts, prototypes, and experiences of interacting with them
Design skills: principles, methods, and tools used in the design process
Auxiliary knowledge: domain expertise, research skills, ICT literacy
Designers learn about user contexts and visions. Participants acquire technological understanding, design skills, and domain knowledge. Participants also learn from each other, sharing experiences and perspectives. This multi-directional exchange fosters shared understanding and collective intelligence.
Creativity in PD emerges through collective reflection-in-action. Participants:
Generate new ideas through oral expressions, visual sketches, mock-ups, or hands-on system interaction
Envision future scenarios based on mutual learning and their current practices
Engage in design-by-doing, prototyping, and experiencing systems to refine solutions
This promotes innovative and contextually relevant designs. However, the literature review found that some PD practices lack explicit reflection-in-action, which limits the depth of creative engagement. Where reflection-in-action is absent, PD risks becoming a data-collection exercise rather than a genuinely creative collaboration.
The research community recommends several directions for strengthening PD:
Broaden stakeholder involvement: include diverse communities, organisations, and governments to foster systemic rather than purely local change
Support full democratic participation: ensure co-decision-making roles for users, moving beyond token involvement
Enhance mutual learning: facilitate deep knowledge exchange across user practices, technologies, and design skills, rather than surface-level consultation
Embrace productive conflicts: recognise that diverse perspectives and constructive disagreements drive democratic innovation; do not smooth over differences prematurely
Prioritise deployment and societal impact: move beyond research explorations toward real-world solutions that empower communities through functional systems
Address systemic inequalities: be mindful of power imbalances and exploitation, particularly in commercial or resource-constrained contexts
Expand geographical and cultural scope: incorporate non-Western perspectives and local contexts to enrich PD's global understanding
The deployment gap is visible in many civic technology projects: a council runs a participatory design process to shape a neighbourhood app, publishes a research paper, but the app never launches. The community contributed time and knowledge and received nothing tangible. Conversely, when PD does reach deployment (for example, a co-designed assistive device that reaches production), the impact on users' daily lives can be substantial. The challenge is closing the gap between these two outcomes.
Students sometimes think power imbalances in PD are accidental. They are often structural, built into funding models, institutional hierarchies, and researcher-participant relationships.
It is common to assume that if a project uses PD methods, the outcomes will automatically be democratic. They will not, unless the political commitment dimension is actively maintained throughout.
Some students treat the challenges listed here as reasons to abandon PD. The research community's position is the opposite: these challenges should be addressed to strengthen PD, not to dismiss it.
The deployment gap is sometimes attributed to lack of funding alone. While resources matter, the gap also reflects a research culture that rewards publication over implementation.
⚠️ Essay questions frequently ask you to critically evaluate PD. The challenges (deployment gap, power imbalances, Western-centric bias, superficial application) are your strongest material here.
⚠️ Be able to explain why equating PD with "running a workshop" is a misconception, and what is missing when that happens (political commitment, iteration, deployment).
⚠️ The five categories of mutual learning (user practices, technology options, new systems, design skills, auxiliary knowledge) are good short-answer material.
⚠️ Productive conflict is a concept that examiners like because it is counterintuitive. Be ready to explain why disagreement can be a feature of good PD rather than a problem.
⚠️ Future directions make strong concluding points in essays. Knowing three or four of the recommended strategies and being able to connect them to specific challenges shows analytical depth.
True or false: The deployment gap refers to the time it takes to ship a product after the design phase.
Fill in the blank: The five categories of knowledge exchanged in mutual learning are user practices, technology options, new systems, design skills, and __________.
True or false: Tokenistic participation is consistent with PD's core principles.
Fill in the blank: One recommended future direction for PD is to embrace __________ as drivers of democratic innovation.
True or false: Most published PD studies represent a broad global range of cultural contexts.
(Answers: 1. False, it refers to PD projects that remain at ideation or exploration without deploying functional systems. 2. Auxiliary knowledge. 3. False, it violates the democratic and empowerment dimensions. 4. Productive conflicts. 5. False, there is a Western-centric bias, with most studies from the US and UK.)
Q: Identify and explain three major challenges facing current PD practice in HCI.
A: (1) The deployment gap: many PD projects stop at ideation or exploration and never deliver functional systems, undermining goal empowerment. (2) Power imbalances: participation can be tokenistic, with users invited to contribute but given no real influence over outcomes, particularly in commercial contexts where PD language may be used to extract user insights for profit. (3) Western-centric bias: the majority of published research originates in the US and UK, which limits the cultural diversity of PD methods and findings and raises questions about their applicability elsewhere.
Q: Why is it a misconception to equate Participatory Design with running a workshop?
A: PD is a holistic, iterative, and politically committed design approach that spans the full lifecycle from ideation through deployment. A single workshop may gather user input, but it does not constitute PD unless it is part of a broader process that includes democratic co-decision-making, mutual learning, iterative design, and (ideally) deployment of solutions that empower users. Equating PD with a workshop strips away the political commitment and the iterative nature that define the approach, reducing it to a data-collection exercise.
Q: What is productive conflict in PD, and why do researchers recommend embracing it?
A: Productive conflict refers to constructive disagreements among participants that arise from diverse perspectives, experiences, and priorities. Researchers recommend embracing it because these disagreements can drive democratic innovation: they surface hidden assumptions, reveal competing needs, and lead to more robust design solutions. Smoothing over differences prematurely can result in designs that reflect only the loudest or most powerful voices, undermining PD's democratic commitment.
Q: Describe the five categories of knowledge exchanged through mutual learning in PD.
A: (1) User practices: workflow, attitudes, and power dynamics within the user's context. (2) Technology options: capabilities, limitations, and how users perceive existing or proposed technologies. (3) New systems: design concepts, prototypes, and experiences of interacting with them. (4) Design skills: principles, methods, and tools used in the design process. (5) Auxiliary knowledge: domain expertise, research skills, and ICT literacy. This exchange is multi-directional: designers learn from users, users learn from designers, and participants learn from each other.
The challenges discussed here connect to broader debates in HCI about research impact and the gap between academic design research and real-world deployment. The power-imbalance critique links to design justice, feminist HCI, and postcolonial computing. The recommendation to expand PD's geographical scope connects to work on cross-cultural design and indigenous knowledge systems. The productive-conflict concept has parallels in organisational theory and deliberative democracy.
Related Terms / Search Tags: PD challenges, deployment gap, power imbalances, tokenistic participation, tokenism, Western-centric bias, depoliticisation, misconceptions about PD, productive conflict, mutual learning categories, user practices, technology options, auxiliary knowledge, design justice, future of PD, systemic change, cultural diversity in HCI, reflection-in-action, PD critique, exam preparation HCI