Short answer

When designing for diverse and distributed user groups, implement methods that foster ongoing dialogue and shared understanding across contexts, such as inter-contextual workshops and documented user experiences.

Field
User-Centred Design
Source
Journal of the Association for Information Systems (2009)
Method
Case Study
Evidence
Moderate effect

Participatory design methodologies must evolve to accommodate distributed user groups and diverse work contexts, shifting focus from custom software to user empowerment. This user-centred design research insight is drawn from a 2009 study published in Journal of the Association for Information Systems. Using Case study, researchers explored how this design variable affects real-world outcomes. The key design takeaway: When designing for diverse and distributed user groups, implement methods that foster ongoing dialogue and shared understanding across contexts, such as inter-contextual workshops and documented user experiences.

Study
User-Centred DesignHigh ImpactModerate effect

Distributed Participatory Design: Adapting Software Across Diverse Workflows

Participatory design methodologies must evolve to accommodate distributed user groups and diverse work contexts, shifting focus from custom software to user empowerment.

Journal of the Association for Information Systems · 2009

01

Key Findings

  • 01Traditional participatory design is limited in addressing distributed users and diverse work contexts.
  • 02Inter-contextual user workshops are effective for bringing together users from different contexts and developers.
  • 03Commented case studies provide persistent documentation of distributed use experiences and design decisions.
  • 04The focus of participatory design can shift from custom software development to empowering users to assess their own practices and technology use.
02

Application

Design takeaway

When designing for diverse and distributed user groups, implement methods that foster ongoing dialogue and shared understanding across contexts, such as inter-contextual workshops and documented user experiences.

How to apply

When developing a product intended for use by multiple, distinct user groups (e.g., different departments, external partners, or online communities), plan for structured opportunities for these groups to interact with each other and the design team, and document their shared experiences and evolving needs.

Project actions

  • 01Consider how users in different environments or with different roles might interact with your design.
  • 02Plan for methods that allow for feedback and adaptation beyond initial user testing.
  • 03Document the evolution of your design based on diverse user input.
03

Method & Evidence

AimHow can participatory design methods be adapted to effectively support the development and evolution of software systems across multiple, diverse user contexts?
MethodCase Study
ProcedureA ten-year case study documented the development and adaptation of a groupware system. This involved establishing inter-contextual user workshops and creating commented case studies to facilitate persistent, documented interaction between users from different contexts and developers.
ContextSoftware development for groupware systems, extending to diverse communities and virtual networks.

Variables

IVUser context diversity, distribution of users
DVEffectiveness of participatory design, software adaptation, user empowerment
CVType of software system, duration of development
04

Strengths & Limitations

Strengths

  • +Longitudinal study provides deep insights into the evolution of participatory design practices.
  • +Addresses a critical gap in participatory design literature concerning distributed and diverse user bases.

Limitations

It can be challenging and time-consuming to organize and facilitate interactions between multiple user groups. Ensuring that feedback from one group doesn't unduly influence or overshadow feedback from another requires careful management.

Reliability & validity

The validity of the findings is supported by the long duration of the case study and the detailed documentation of the process. Reliability might be a concern due to the specific context of the groupware system and the qualitative nature of the data.

Think critically

To what extent can the principles of inter-contextual participatory design be applied to physical product design, rather than solely software?

05

Design Principles

"Design for distributed participation by creating mechanisms for continuous feedback and knowledge sharing across diverse user contexts."

As work becomes increasingly distributed and diverse, traditional participatory design approaches focused on single organizations are insufficient. Designers need to develop methods that can effectively engage users across different contexts, fostering a sense of ownership and enabling continuous adaptation of digital tools.

06

What This Means for Your Design

When you design something that lots of different people will use in different ways, you can't just ask one group. You need to find ways for all the different users to talk to each other and the designers, and keep records of how they use it, so the design can keep getting better for everyone.

How to use in your project

  • 1.Reference this study when discussing the challenges of user research with diverse or distributed user groups.
  • 2.Use the concept of inter-contextual workshops to justify methods for gathering feedback from multiple user personas.
07

Add to My Project

08

Quick Cite

Paragraph starter

The challenges of designing for diverse and distributed user groups, as highlighted by Obendorf et al. (2009), underscore the need for adaptive participatory design methods. Their work on inter-contextual workshops and commented case studies offers a framework for engaging users across varied contexts, shifting the design focus towards empowering users to critically assess their own technology use and practice, a crucial consideration for any design project aiming for broad applicability and sustained relevance.

09

Source

Journal of the Association for Information Systems

Inter-Contextual Distributed Participatory Design

journal · 2009

View source

Questions About This Research

What does the research say about distributed participatory design: adapting software across diverse workflows?
When designing for diverse and distributed user groups, implement methods that foster ongoing dialogue and shared understanding across contexts, such as inter-contextual workshops and documented user experiences. Evidence: Journal of the Association for Information Systems (2009).
Why does "Distributed Participatory Design: Adapting Software Across Diverse Workflows" matter for design?
As work becomes increasingly distributed and diverse, traditional participatory design approaches focused on single organizations are insufficient. Designers need to develop methods that can effectively engage users across different contexts, fostering a sense of ownership and enabling continuous adaptation of digital tools.
How can designers apply this research?
When designing for diverse and distributed user groups, implement methods that foster ongoing dialogue and shared understanding across contexts, such as inter-contextual workshops and documented user experiences.
What were the main findings?
Traditional participatory design is limited in addressing distributed users and diverse work contexts.. Inter-contextual user workshops are effective for bringing together users from different contexts and developers.. Commented case studies provide persistent documentation of distributed use experiences and design decisions.. The focus of participatory design can shift from custom software development to empowering users to assess their own practices and technology use.
What research method was used?
Case Study.
How strong is the evidence?
Evidence strength is rated Moderate effect, based on a 2009 journal from Journal of the Association for Information Systems.
What should I do differently in my next project?
When developing a product intended for use by multiple, distinct user groups (e.g., different departments, external partners, or online communities), plan for structured opportunities for these groups to interact with each other and the design team, and document their shared experiences and evolving needs.
What are the limitations?
The long duration of the case study might not reflect the pace of modern development cycles. The specific groupware system may have unique characteristics that limit generalizability.