Work is Not a Dare: Tips for Building Inclusive Teams
summary
Workplaces become a sequence of implied dares that silence questions and encourage solo heroism; the presentation argues that psychological safety — measured by conversational turn‑taking and average social sensitivity from Google’s Project Aristotle — is the decisive factor. Practical moves include adopting a published workflow like GitHub flow, keeping Django‑style markdown docs alongside code (documentation in triplicate), doing design reviews before coding, making code reviews verify docs tooling and deployment plans, and treating high performers as a fragility risk.
AI-written summary · about
chapters (9)
- 0:00Start
- 21:14Set expectations for time commitments
- 29:15to Supportive
- 30:31EVALUATION
- 31:29CONTROL
- 32:36STRATEGY
- 33:27NEUTRALITY
- 34:17SUPERIORITY
- 34:54CERTAINTY
related talks
39mUsing Agile Techniques to Build a More Inclusive Team
35mIntersectional & Inclusive Standards for Developers
26mBetter Together Diversity Networking Lunch
23mHow to Practice Inclusion and Benefit Django
22mInclusion in Open Source - Allies, Outlaws and Dinosaurs
38mBecoming a Stronger Ally: Handling Difficult Situations and...
18mDesign your workplace embracing "Diversity and Inclusion" and walk on air
57mEverything is awesome: the Lego approach to being an awesome coworker