Embedded cultural assumptions: how to annoy and insult your users in one easy step
summary
Examples: government tax-credit letters arrive addressed to "Mr Julia" because the form only accepts Mrs or Miss, the kennel club rejects the 38th repeated dog name due to Roman numerals breaking at 38, and an events system populated from WordPress JS mangles non‑Latin characters. A legacy Access roster is migrated to a proper relational DB, SQL scripts null out inferred genders, and ad‑hoc fixes silently merge distinct people. Practical takeaway: assumptions about names, encodings and identities cause failures, protests (2013) and political flareups (2022).
AI-written summary · about
chapters (15)
- 0:00Embedded cultural assumptions
- 1:24Cultural missteps examples
- 6:20Defining embedded assumptions
- 8:49Why monocultural teams miss these issues
- 11:39Name handling assumptions
- 17:19Database validation pitfalls
- 21:53Names as identifiers problems
- 24:01Age-specific expectations
- 27:57Gender assumptions in DB
- 33:16Trust and self-ID challenges
- 34:42Nationality field complexities
- 37:48Changing personal data
- 39:56Lessons from mistakes
- 41:00Better data handling principles
- 42:47Q&A on healthcare, titles, AI
related talks
48mCollecting information with care
42mWhy User Data is about more than Forms
37m"Walking A Mile In Your Users' Shoes"
24mEliminating Unconscious Biases in Technology Through...
34mHello, my name is __________.
42mSystems of Exclusion
11mA name that disempowers
28mCross-Cultural Differences and How to Include All Users