How Privilege Defines Performance
summary
Argument: definitions of "performance" mirror the builder's privilege and miss real users. Evidence: Majestic Million/WCAG lists common accessibility fails, Firefox/Chrome device lists center iPhones not Tecno/Huawei, Framer gender flag uses true=male, and tests show valuation vs worker pay—Lyft IPO $24.3B while drivers average $3.30 per hour—plus concrete failures like Facebook soap dispenser and Google Photos mislabels. Response: a public Self Define API and open dictionary plus bots to reduce emotional labor and force concrete, testable changes rather than vague empathy.
AI-written summary · about
chapters (15)
- 0:00Introduction and background
- 6:13Privilege and perspective
- 8:47Defining privilege
- 12:09Systemic oppression
- 15:09Confronting personal privilege
- 18:26The power of privilege
- 21:07Meritocracy vs reality
- 24:38Implicit bias in technology
- 27:17Centered experiences
- 30:39Narrow worldviews
- 32:52Subjectivity in algorithms
- 35:14Beyond empathy to trust
- 38:08Sharing power and resources
- 41:08Taking action
- 42:18Q&A and self-defined
related talks
41mHow Privilege Defines Performance
26mPrivilege as a Technical Debt
49mDeconstructing Privilege
24m“Works for Me”
24mPrivilege as a technical debt
54mAn empathy exercise: contextualising the question of privilege
19mPerceived Performance, And Why It Matters
23mUsing Privilege Arbitrage to Increase Inclusion