Why psychological safety is the key to sustainable product development
summary
Migrates a mission‑critical hospital data platform—five petabytes—to the cloud with zero downtime by fixing team dynamics rather than processes. Introduces the LAD framework (listen, acknowledge, do): individual interviews, validation, then concrete action and delegation. Builds a team charter, starts regular one‑to‑ones, shifts to private criticism and public praise, and adds tiny rituals (daily dad jokes) to rebuild trust. Result: long‑stranded conflict resolves, people collaborate and the migration completes successfully.
AI-written summary · about
chapters (7)
- 0:00Introduction and speaker intro
- 1:05Why psychological safety matters
- 4:16Psychological safety in high-performance teams
- 7:10Case study: Data migration challenge
- 8:36LAD framework: Listen, acknowledge, do
- 12:09Practical strategies for leaders
- 13:56Closing and call to action
related talks
36mPsychological Safety: Building fearless teams
36mPsychological Safety for Your Platform Engineering
28mCultivating a culture of Psychological Safety in Engineering
41mNavigating Agile Transformations in a Crisis: From Thunderstorm to Smooth Sailing
15mInfusing Psychological Safety into Your Teams
27mFostering psychological safety in distributed teams
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
29mPsychologically safe reliability management