Cultural Relativism a Prism for Constructing Communities
summary
Argues that cultural relativism is a practical lens to find friction in cross‑cultural dev teams and gives concrete fixes: use ethnographic awareness, declare a single project culture, enforce no main-branch commits and require code in VCS for review, make it safe to fail and safe to disagree, shift standups to allow discussion, and surface management actions publicly. Example: transferring work to a team that hides failure and avoids disagreement — the enforced rules and public failures increase openness and produce better contributions.
AI-written summary · about
chapters (12)
- 0:00Cultural relativism intro
- 1:29Defining culture
- 3:59History and principles
- 7:55Why relativism matters
- 8:36Culture and language
- 10:43Cross-cultural pitfalls
- 12:30Cultural taboos
- 13:57Case study barriers
- 19:22Cultural sensitivity
- 21:06Cross-cultural project
- 22:55Respect and collaboration
- 23:16Q&A
related talks
43mThe Influence of Cultural Relativism
14mInclusive leadership across cultures: Practical patterns for global engineering teams
16mDealing with culture divide and internal advocacy
01h 41mPNSQC 2013 - Valerie Berset-Price
31mBuilding High-Performing Cross-Cultural Teams
17mBuilding High Performance Teams Across Cultures
45mCulture Add Over Culture Fit
54mThe Culture Map