practiceExperience & interface

Inclusive Design

Inclusive design is a process that recognizes exclusion, learns from human diversity, and creates adaptable solutions with affected people.

Download Markdown (.md)

01What it means

Inclusive design examines mismatches between people and products rather than treating one imagined average user as the norm. It deliberately involves people whose perspectives are often excluded, uses their experiences to reshape the problem, and looks for solutions that can extend to others without erasing specific needs.[1][2][3]

Designing with people excluded by current assumptions Identify mismatch, involve lived experience, and test who benefits or is newly excluded
  1. 01Map exclusionWho is missing from the framing
  2. 02Remove participation barriersRecruit relevant lived experience
  3. 03Learn from mismatchNeeds, context, power, tradeoffs
  4. 04Co-create alternativesMultiple ways to participate or complete
  5. 05Evaluate + continueBenefits, new exclusions, ongoing relationship

Permanent, temporary, and situational mismatches can inform design without being treated as equivalent experiences.

02Why it matters

Teams reproduce their own assumptions when participation is narrow. Inclusive practice reveals barriers and priorities earlier, improves problem framing, and can create more flexible products while respecting that one solution will not serve every person equally.

03When to use it

Use inclusive design during discovery, recruitment, concept development, prototyping, and evaluation—particularly where identity, ability, language, income, culture, or environment may shape access. Budget for participation rather than seeking validation at the end.

04How it works

  1. Map who may be excluded by the current problem framing and team assumptions.
  2. Recruit people with relevant lived experience and remove participation barriers.
  3. Learn from permanent, temporary, and situational mismatches without treating them as equivalent.
  4. Co-create and prototype multiple ways to participate or complete the task.
  5. Evaluate benefits and new exclusions with affected people.
  6. Document unresolved trade-offs and continue the relationship after launch.

05A practical example

Example

A video-meeting team works with Deaf and hard-of-hearing participants to improve captions, speaker identification, correction, and transcript controls. The resulting design also helps people in noisy rooms, but the team continues to evaluate the distinct needs of primary participants.

06Where it breaks

“Benefits everyone” can become an excuse to stop centering disabled or marginalized people. Inclusive workshops do not redistribute decision power by themselves, and no product can cover all human diversity; targeted accommodations and specialist accessibility work may still be required.

Common mistakes

  • Inviting one participant to represent an entire community.
  • Using personas instead of engaging people with lived experience.
  • Claiming broad benefits while ignoring the group that exposed the barrier.
  • Treating inclusion as inspiration rather than paid, influential participation.

07Sources

  1. Microsoft Inclusive DesignMicrosoft Design · Institutional methodologyMicrosoft Inclusive Design
  2. Inclusive 101 GuidebookMicrosoft Design · Institutional guidanceInclusive 101 Guidebook
  3. Introduction to Web AccessibilityW3C Web Accessibility Initiative · Institutional guidanceIntroduction to Web Accessibility
View saved topics

Start typing to search titles, definitions, categories, and frameworks.