Desigining for Renaming
summary
County court-ordered name change costs over $400 and can take six months, and dozens of sites still call a person by the old name. Examples: Square and recruiter systems keep old records, Amazon suspends accounts and demands faxes of court orders, Kaiser/Epic medical systems show preferred name to clinicians but older 3270 clerical systems deadname patients. Second Life adds a display name layer but required retrofitting millions of LSL scripts. Concrete fixes: audit where names appear, propagate changes everywhere, and prefer display-name systems that actually work.
AI-written summary · about
chapters (15)
- 0:00Start
- 0:09Design for Renaming
- 6:10Name changes aren't just for #girlslikeus
- 6:3280% of US residents who identify as women change their name when they marry.
- 7:0940 to 50% of marriages end in divorce.
- 7:54Immigration and Naturalization
- 8:1540% of trans * people don't have id matching their gender.
- 10:26Computers are really good at microaggressions.
- 14:16The State is Transphobic
- 16:17There's always one more system.
- 33:00But not clerical staff.
- 36:40Audit where names appear in your systems.
- 37:23Ask users what they should be called. Use that in customer facing systems and CSR tools.
- 38:17Fire your "Real Name" policy.
- 39:24OPEN SOURCE BRIDGE
related talks
13mWhat's in a Name (Validation)?
49mEmbedded cultural assumptions: how to annoy and insult your users in one easy step
32mHow We Do Identity Wrong
48mCollecting information with care
42mWhy User Data is about more than Forms
44m“System of Systems”
29mWhat's in a Name: From Variables to Domain-Driven Design
13mDesign Systems Showcase: Naming (and renaming) a Design System