Designing beyond caricatures: Embracing real, diverse user needs
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
"Remote research methods can cast a wider net, but some briefs still require on-the-ground presence."
Chloe Amos-EdkinsA Cultural Approach: Research in the Context of Glocalisation
March 27, 2023
"The factory clocks were instruments not for measurement but for cheating and oppression."
Tricia WangSpatial Collapse: Designing for Emergent Culture
January 8, 2024
"Edgy asks three fundamental questions: Why are we here? What’s the role this enterprise plays in people’s lives? And what do we need to make it work?"
Milan Guenther Benjamin KumpfThe $212 billion ‘so what?’: unlocking impact in development cooperation
November 20, 2025
"Without a human in the loop, AI can go off and do crazy disastrous things."
Jon Fukuda Amy Evans Ignacio Martinez Joe MeersmanThe Big Question about Innovation: A Panel Discussion
September 25, 2024
"Language matters—make your OKRs user-centric and customer-focused to avoid them feeling like overhead."
Bria Alexander Benson Low Natalya Pemberton Stephanie GoldthorpeOKRs—Helpful or Harmful?
January 20, 2022
"The more technology we bring in, the more users lose agency and empowerment, but we need to flip this back."
John TaschekMaking People the X-Factor in the Enterprise
June 15, 2018
"Enterprise problems are often engineering problems as much as design problems."
Dan WillisEnterprise Storytelling Sessions
May 13, 2015
"We’re very careful about PII and only the lead researcher and research ops managers have access to sensitive data."
Tracy McGoldrickIBM User Experience Program—The What, Why and How
October 15, 2021
"April will lead us through provocations and thoughts about where we want to be once we leave here."
Alana WashingtonTheme 3 Intro
October 1, 2021
