Summary
Designing with rigid assumptions often means creating for a narrow set of “typical” users—people who look and think like us. But this mindset risks excluding real, diverse needs, especially those of people with disabilities, one of the fastest-growing population segments. In this talk, you’ll explore the hidden costs of designing systems for templated personas and learn why flexible, inclusive approaches are essential.
Key Insights
-
•
Disability affects one in five people, not a rare subset.
-
•
The medical model of disability stigmatizes individuals by labeling them as broken.
-
•
Designing for an average user is flawed because the average person does not exist.
-
•
Disability is a spectrum that includes permanent, temporary, and situational conditions.
-
•
Assistive technologies like captions have evolved to benefit broad audiences beyond initial users.
-
•
The aging population is increasing the demand for accessible products as disability becomes more common with age.
-
•
Temporary disabilities impact users who still need to engage with products and services effectively.
-
•
Involving people with disabilities as coworkers and co-designers improves identification and elimination of accessibility barriers.
-
•
QA testing with screen readers is valuable, but user research should be conducted by actual assistive technology users.
-
•
Designing for accessibility benefits all users and future-proofs products against diverse user needs.
Notable Quotes
"The average user doesn’t exist."
"People with disabilities are not one in a thousand, or one in a hundred, they are one in five."
"Disability is not a binary, it’s a spectrum."
"We tend to design for people just like us, which is limiting."
"Temporary disability is real and products should support people when they experience it."
"Captions were once an assistive technology for a tiny subset but are now widely used."
"Failing to design for disabilities means failing to design for our future selves."
"Accessibility isn’t just for developers or designers—everyone has a role to play."
"We cannot remove barriers we aren’t aware of."
"Testing with a screen reader is fine for QA, but user research must be with actual screen reader users."
Or choose a question:
More Videos
"No assistive technology user uses default settings; we spend years customizing everything to work for us."
Sam ProulxSUS: A System Unusable for Twenty Percent of the Population
December 9, 2021
"The biggest bottleneck is the bureaucracy, like the Paperwork Reduction Act, we have to creatively navigate that."
Michael LandEstablishing Design Operations in Government
February 18, 2021
"I spent too much time trying to change company culture and should have focused more on just getting things done."
Shipra KayanHow we Built a VoC (Voice of the Customer) Practice at Upwork from the Ground Up
September 30, 2021
"Innovation is about being fearless, breaking rules, and refusing to stop at the way things have always been done."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"The chief of staff is the bridge between our executive leadership team and the design ops practitioners."
Isaac HeyveldExpand DesignOps Leadership as a Chief of Staff
September 8, 2022
"We categorized all our work into may-do, must-do, and desire-to-do buckets to better allocate our efforts."
Amy EvansHow to Create Change
September 25, 2024
"Telepathy as mind reading means proactively building a talent pipeline and improving recruitment processes."
Kate Koch Prateek KalliFlex Your Super Powers: When a Design Ops Team Scales to Power CX
September 30, 2021
"People don’t share their beliefs; you have to search for and understand them to get true buy-in."
Dave GrayLiminal Thinking: Sense-making for systems in large organizations
May 14, 2015
"We wanted a living network of knowledge so yesterday’s insight connects to today’s evidence and tomorrow’s learning."
Matt DuignanAtomizing Research: Trend or Trap
March 30, 2020
