Psychological Safety: Building fearless teams
summary
A clear claim: teams with high psychological safety and high performance standards hit a “learning zone” that improves outcomes, supported by Google’s Project Aristotle. Practical actions shown: leaders do active listening, ask coaching questions, delegate, call out shaming, and measure via Slido survey or team questionnaires. Concrete example: an Android dev struggles with a legacy service locator to Koin proposal, leaves after three months, joins a new team and after two months helps introduce Compose, showing the approach can work.
AI-written summary · about
chapters (11)
- 0:00Introduction to talk
- 5:00Charlie’s story explained
- 10:57What is psychological safety
- 17:39Audience reflection questions
- 17:59Leaders building psychological safety
- 23:16Mistakes as learning opportunities
- 25:21Humanizing team connections
- 27:05Team responsibility and delegation
- 30:31Failing to create psychological safety
- 31:13Why psychological safety is missing
- 34:08Charlie’s happy ending
related talks
22mPsychological safety: How to become a team that learns
40mHigh Performance via Psychological Safety
22mUnleash Your Team's Potential Through The 4 Stages Of Psychological Safety
22mKeynote: Psychological Safety and the High Performing Team
15mInfusing Psychological Safety into Your Teams
09m“Taking the lead – Building psychological safety at work!”
27mFostering psychological safety in distributed teams
34mDiverse Leaders in Tech - Psychological Safety: Building Trust, Accountability, and Inclusion