Involve users directly in the design process as co-creators.
Detailed description
Participatory Design is a collaborative methodology that directly involves end users as co-creators in the design process, allowing them to actively contribute ideas, solutions, and feedback during structured workshops. This technique democratizes the design process, ensuring that solutions genuinely reflect user needs and perspectives, while generating greater acceptance and ownership of the final product. Academic research supports its effectiveness in creating more inclusive and user-centered solutions (Interaction Design Foundation). It is especially valuable for projects that impact specific communities or require mass adoption.
Main objective
Involve users directly in the design process as co-creators.
When to use it
Ideation and solution definition phases.
Effort level
Medium to High
Recommended number of users
5–15 users in workshops
Advantages
Access to the tacit: It uncovers needs that users cannot put into words.
Empowerment and democracy: It gives users a voice in decision-making, which is especially powerful in the design of public services or government (civic design).
Alignment and ownership: When users (or internal stakeholders) take part in creating something, they feel it as their own, which reduces resistance to change and increases adoption.
Innovation: It generates divergent ideas that the internal design team might not have considered because of its own biases.
Disadvantages
Requires expert facilitation: It is not simply a "brainstorm." If it is not facilitated well, the loudest voices can dominate (groupthink), or users can feel intimidated by the creative task.
Resource-intensive: It is costly in preparation time (building the toolkits), in running the session, and above all in analyzing complex, unstructured qualitative data.
Not final design: Users are not professional designers. Their solutions can be technically unfeasible or inconsistent. The value lies in the intent behind their design, not in the literal solution.
When to use
•Complex service design
•Collaborative innovation
•Systemic problems
•When there's resistance to change
Metrics
•Participation level
•Ideas generated
•Consensus reached
•User ownership
Practical example
Organize a workshop where users draw or model how a control dashboard should be.