Skill Guide

Human-centered design and participatory co-design with neurodiverse and disabled stakeholders

A collaborative design methodology where neurodiverse and disabled individuals are treated as essential, equal partners throughout the entire design and development process to create universally accessible and usable products and systems.

It minimizes costly post-launch redesigns, regulatory non-compliance, and market exclusion by embedding accessibility and inclusivity from the ground up. This directly translates to expanded market share, enhanced brand reputation, and innovation driven by diverse human perspectives.

1 Careers

1 Categories

9.2 Avg Demand

15% Avg AI Risk

How to Learn Human-centered design and participatory co-design with neurodiverse and disabled stakeholders

Focus on foundational ethics and terminology. 1) Master the social model of disability versus the medical model. 2) Learn core accessibility principles (WCAG, POUR: Perceivable, Operable, Understandable, Robust). 3) Practice active listening and communication adjustments (e.g., plain language, offering multiple response modalities).

Transition to practical facilitation and method application. 1) Run mock co-design sessions using specific artifacts (storyboards, low-fi prototypes) with feedback loops designed for cognitive diversity. 2) Avoid tokenism by ensuring participants are compensated and have genuine influence. 3) Common mistake: designating one 'accessibility expert' rather than distributing this responsibility across the team.

Master systemic integration and advocacy. 1) Architect organizational processes that institutionalize co-design (e.g., integrating lived-experience review boards into governance). 2) Develop strategic frameworks for scaling inclusive practices across product portfolios. 3) Mentor teams on navigating complex trade-offs between universal design, business constraints, and specific user needs without compromising ethical commitments.

Practice Projects

Beginner

Case Study/Exercise

Conducting an Accessible User Interview

Scenario

You need to interview a neurodiverse user (e.g., someone with ADHD) about a new productivity app feature. Your standard rapid-fire, unstructured interview style has been ineffective.

How to Execute

1) Pre-session: Send interview questions in advance in multiple formats (text, audio). 2) Session setup: Offer choice of medium (video, voice-only, text chat) and a clear agenda with timeboxes. 3) Facilitation: Use direct, concrete questions; allow extended pause times; summarize understanding frequently. 4) Post-session: Validate your notes with the participant asynchronously.

Intermediate

Case Study/Exercise

Co-Designing a Mobile Banking Onboarding Flow

Scenario

Your team is redesigning a bank's mobile app onboarding. You must ensure it is accessible to users with motor impairments (e.g., limited dexterity) and visual impairments.

How to Execute

1) Recruit and compensate a diverse panel of 6-8 users with varying abilities. 2) Facilitate a workshop using tangible, high-contrast, large-print physical cards to represent screen elements for rearrangement. 3) Implement a 'pair-prototyping' session where a designer and a user with a motor impairment jointly configure interaction targets and gesture alternatives. 4) Synthesize findings by mapping pain points to specific WCAG success criteria for developer handoff.

Advanced

Case Study/Exercise

Institutionalizing Co-Design in a Fintech Startup

Scenario

As the new Head of Design, you are tasked with making participatory co-design with disabled stakeholders a standard, non-negotiable part of the product lifecycle at a fast-growing fintech startup, against resistance citing speed-to-market.

How to Execute

1) Develop a 'Minimum Viable Inclusivity' (MVI) protocol-lightweight, mandatory checkpoints (e.g., review by a neurodiverse consultant at wireframe and beta stages). 2) Build a permanent, compensated 'Lived Experience Advisory Panel' with clear charter and direct product team access. 3) Create and distribute internal 'Inclusive Design Debt' metrics to quantify the cost of retrofitting, tying it to business KPIs like support ticket volume. 4) Advocate for and secure budget by modeling the ROI of inclusive features on customer acquisition and retention in target segments.

Tools & Frameworks

Mental Models & Methodologies

Social Model of DisabilityDouble Diamond (with integrated co-design gates)Persona Spectrum (Microsoft Inclusive Design Toolkit)POUR Accessibility Principles

The Social Model shifts focus from fixing the individual to removing societal barriers. The Double Diamond structure ensures problem space exploration includes affected communities. The Persona Spectrum helps expand target users beyond edge cases to situational limitations. POUR provides a concrete technical benchmark for accessibility.

Facilitation & Communication Tools

Participatory Design CardsAccess Needs & Communication Passport templatesMultiple Modality Feedback Platforms (e.g., Miro with accessibility plugins, Figma with commenting alternatives)

Use PD Cards to make abstract design concepts tangible and manipulable for all participants. Communication Passports allow users to pre-specify their access needs and preferences, setting the stage for a respectful session. Ensure your digital tools support screen readers, keyboard navigation, and alternative input methods.

Interview Questions

Answer Strategy

Use the STAR (Situation, Task, Action, Result) method. Focus on demonstrating humility, the concrete nature of the feedback, and the systemic change it prompted. Sample Answer: 'In a recent education platform project, a user with dyslexia found our color-coded progress system meaningless. They provided feedback that spatial layout (like a tree diagram) was more intuitive for them than color hues. I re-convened the design team to prototype two new visualization schemes, validated them with the user and others, and we shipped a hybrid model that allowed user-preference switching. This led to a 15% increase in progress-tracking feature usage.'

Answer Strategy

Tests strategic thinking and negotiation skills. The answer should frame standards as a non-negotiable floor, not a ceiling, and user preferences as valuable data for exceeding that floor. Sample Answer: 'I view WCAG AAA as the foundational engineering specification-it is a baseline requirement, not a negotiation point. Co-design feedback then informs how we *exceed* that baseline to delight and empower. When conflicts arise, I use a 'must-do, should-do, could-do' framework. Accessibility mandates are 'must-dos.' User preferences become 'should-dos' and 'could-dos,' which are prioritized through impact-effort analysis and iterative testing. My role is to facilitate that prioritization transparently with the team and stakeholders.'