Why User Data is about more than Forms
summary
Argues that binary gender fields and rigid name rules produce wrong analytics, bad targeting and real harm, noting roughly 1–5% of people identify outside the binary. Recommends concrete fixes: run stress cases to find low‑frequency high‑impact users, apply the crushed‑form checklist (who needs this, why, required/optional), make titles optional, separate legal name from display/stage name, allow selectable genders plus a free‑text option (Facebook style), and replace “invalid” errors with actionable validation so data stays useful and safe.
AI-written summary · about
chapters (13)
- 0:00Intro
- 0:34Who is Chad
- 1:49People are complicated
- 4:40Assumptions
- 6:50Gender
- 12:36Mis assumptions
- 15:34Painful information
- 22:41Facts
- 26:42Names
- 29:40Stress Cases
- 31:15Crushed in Protocol
- 32:48Ask People
- 35:00Text Fields
related talks
32mHow We Do Identity Wrong
46mGender Inclusivity Is More Than an “Other” Option
24mEliminating Unconscious Biases in Technology Through...
21mWeb Forms: When Someone's Gender is Your Business
47mCreating solutions for everyone
44mInclusive Form Inputs
27mCreating Beautiful, Accessible, and User Friendly Forms
49mEmbedded cultural assumptions: how to annoy and insult your users in one easy step