Ethics in Tech: a psychological perspective
summary
Covers concrete social-psychology findings and a plain playbook: Solomon Asch shows 75% conform at least once on a simple line test, Stanley Milgram finds about 65% administer the highest shock in obedience studies (replications report up to 85%), and a Stack Overflow ethics poll of ~70,000 respondents finds ~50% say it “depends” whether to report issues while ~60% blame upper management for bad code choices. Uses Columbia shuttle, Asiana crash and a nurse error to show harm from lacking psychological safety, cites Google Aristotle and Amy Edmondson, and gives three actions: set context, acknowledge vulnerability, and replace blame with curiosity.
AI-written summary · about
chapters (8)
- 0:00Start
- 1:55Why good people make bad decisions
- 10:25Obedience Stanley Milgram
- 15:58Claws of obedience
- 18:08Speak up
- 21:07What can be done? Organisations
- 24:39Psychological safety
- 33:20Learning Problems
related talks
37mEthics in Software Engineering - Should We Care
50mEvil Tech: How Devs Became Villains
31mEthically Wired Computer Ethics for Technologists
55mValues Driven Development
41mEvil Tech: How Devs Became Villains
53mSwearing, Nudity and Other Vulnerable Positions
34mDiverse Leaders in Tech - Psychological Safety: Building Trust, Accountability, and Inclusion
45mHow much do you trust the team?