Q2.13.3Power asymmetry in co-design workshopsdesignresearch

Prevent organizational power from dominating the workshop

Aliases: power asymmetry · voice dominance · participation equity

What it is

Voice dominance in co-design is not merely talking more. Rank, professional authority, resource control, or client status can make some accounts more likely to enter the agenda and final artifact. Frontline staff, contractors, or users may self-censor under evaluative risk even with equal airtime, so apparent agreement need not reflect independent agreement.

Why it happens

High-power members can define vocabulary, evaluate ideas early, control the boundary of feasible resources, or signal which conclusions will be adopted. Others accommodate, stay silent, or translate concerns into safer language. A shared artifact then compresses that power process into an apparently neutral result. Turn-taking changes conversational access but does not remove career consequences or unequal decision rights.

Studying it

Collect private or anonymous individual input before joint work, then compare which ideas disappear, change, or are absorbed after groups combine. Record proposal provenance, objections, interruptions, and decision rationales; inspect patterns by role rather than reporting consensus alone. Provide a confidential post-session channel for concerns that were unsafe to voice in the room.

Where it stops holding

Separation and anonymity reduce some pressure but can remove useful negotiation across roles, while wording may still reveal identity in a small team. Including organizational leaders is not inherently harmful: they can clarify constraints and commit resources. The issue is how power shapes evidence and decisions, not permanently excluding a category of participant.

Applying it

  • Generate in groups separated by power or reporting lines before a rule-governed joint comparison.
  • Use private submission, rotating facilitation, and unattributed display while stating anonymity limits.
  • Preserve who proposed, who decided, and why an idea was adopted as artifact metadata.
  • Carry unresolved disagreements into the deliverable instead of erasing them as consensus.

Related

  • Same group: Q2.13.1 Generative participation · Q2.13.2 Outputs as evidence
  • Adjacent: Q2.05.2 Dominant speakers crowd out others · Q1.14.3 Stakeholder presence
  • Search terms: power asymmetry · participation equity · co-design facilitation

Cards in the same group

Quick Actions

Share

Share this page

ios_share

https://hci.top/en/handbook/Q2.13.3