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."
Dig deeper—ask the Rosenbot:
More Videos
"I’m going to need to bring my A game."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"This is a moment to rethink identity beyond UX and get creative with income streams and career paths."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"You shouldn’t send another survey unless you’ve implemented changes and allowed time for behavior to adapt."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"Surprisingly, when nudging vaccines, consumers preferred seeing every eligible vaccine listed, even controversial ones like COVID-19."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"Momentum in users is like energy in fluid—strong motivation drives fast, decisive movement."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"Anecdotal feedback from team members helps leaders understand the real impact of change."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"Work on yourself. Understand your identity and privilege before trying to serve others."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Design Ops might not just support design anymore—our work is requested by non-designers and solving broader business problems."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"In large complex systems, the dots are scattered across silos and time zones, making progress feel elusive."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
Latest Books All books
Dig deeper with the Rosenbot
What challenges arise when balancing short-term focus with long-term transformation goals?
What does it mean for design ops to shift from managing existing processes to architecting infrastructure and cultural change at scale?
What continuous strategies support sustaining an accessibility culture across teams?