Menu

UX

Participatory Design

A practical UX method for involving users as active collaborators so design decisions are grounded in real perspectives from the start.

How to use participatory design to involve users directly in shaping ideas and solutions, leading to stronger alignment and more relevant outcomes.

4 min read

What it is

Participatory design is a UX method where users are actively involved in the design , contributing ideas, , and decisions.

It goes beyond or testing by treating users as collaborators rather than subjects.

Participants work alongside designers and teams to explore problems, generate concepts, and refine solutions.

This can happen through workshops, activities, or ongoing collaboration.

The goal is to ensure the design reflects real user needs and perspectives from the start.

Participatory design is most useful when the quality of the solution depends on users helping shape it, not just evaluating it afterward.

When to use it

Use this method when user input is critical to the outcome.

It is most useful when:

You are designing for complex or specialised users
You want deeper user involvement
You are exploring new or unclear problem spaces
You need strong alignment with user needs
You are working on high-impact or sensitive experiences

It is less useful when:

Users cannot easily participate
The problem is simple or well understood
You need quick validation rather than collaboration
Participatory design is often used in discovery and early design phases.

Key takeaway

Use participatory design when involving users directly will reduce assumption risk and improve confidence that the solution fits real needs.

How to run it

Set up properly

Be clear on how and when participants will be involved across the project, not just in one . Participatory design is a stance rather than a workshop.

Agree how contributions will influence decisions, and be honest where they will not.

Run the method

Participatory design involves users throughout the as ongoing partners rather than occasional contributors. It differs from co-design mainly in duration and commitment.

  1. Involve people early, while the problem is still being framed rather than after it is settled.
  2. Run collaborative activities at each stage: exploring problems, generating ideas, reviewing work.
  3. Explore problems and solutions together, allowing participants to challenge the framing itself.
  4. Encourage open discussion, including disagreement with the team.
  5. Iterate based on shared , and show participants what changed as a result.

Close the loop every time. Participation that never visibly changes anything is consultation, and people stop turning up.

Capture and make sense of it

The value comes from sustained involvement. Across the project, document:

  • How participant input changed decisions, specifically
  • Where the team's framing was wrong and was corrected
  • Tensions between participant preference and other
  • The relationship built, which is an asset for future work

Use this for with a defined community, and where the cost of designing the wrong thing is high.

What to look for

Focus on:

Input: ideas and contributions from users
Engagement: level of participation
Alignment: how well solutions match user needs
Themes: patterns across input
Direction: where the design should go

Where it goes wrong

Most issues come from:

Users guide design, but they don’t replace it.

Involving people once and calling it participatory
Bringing them in after the framing is settled
Accepting every suggestion without testing it
Leaving roles and influence undefined
Never closing the loop, so participation becomes consultation

What you get from it

Done properly, this method gives you:

Input across the project rather than at one session
Decisions visibly changed by what participants said
Correction of framing the team had wrong
A relationship that is an asset for the next project

Key takeaway

It helps ensure you are building the right thing.

Get in touch

If this sounds like something you need, we can help you involve your users in the design process and build solutions that truly work for them.

No guesswork. No assumptions. Just design shaped by real people.

FAQ

Common questions

A few practical answers to the questions that usually come up around this method.

What is participatory design in UX?

It is a method where users actively take part in the design process.

When should you use participatory design?

Use it when user involvement is key to success.

How is it different from co-design?

Participatory design is broader and often ongoing, while co-design workshops are more structured sessions.

Who should be involved?

Real users, alongside designers and stakeholders.

Does participatory design improve UX?

Yes. It leads to more relevant and user-centred solutions.

Quick take

If you want users shaping the solution, not just reacting to it, use participatory design.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services.

Previous feedback

I had a fantastic experience working with Andy. One of his most impressive achievements during our time at NHS HEE was masterminding a deeply complex information architecture for a new platform that brought together a large number of legacy websites.

Will Parkhouse

Senior Content Designer