Fail Fast, Fail Often - Make Safety a Prerequisite for your Team
summary
Psychological safety drives team effectiveness, backed by Google’s research, so make it a precondition for experiments and ops. Concrete practices: blue-green deployments, canary releases, feature toggles and continuous integration let teams release small, reversible changes (examples include 5% canary rollouts). Run lightweight post‑mortems with 5 Whys, use “popcorn flow” experiments, and adopt Toyota’s Jidoka red‑stop. Facebook’s dark‑launch gatekeeper for Messenger is a concrete build that validates features on a small cohort before wide release.
AI-written summary · about
chapters (18)
- 0:00Introduction to talk
- 1:48About the speaker
- 2:52Fear and blame culture
- 4:40Fear kills innovation
- 5:44Psychological safety defined
- 6:55Management practice model curiosity
- 8:42Continuous learning in teams
- 10:08Safe to fail environments
- 10:50Freedom with responsibility
- 11:35Root cause analysis
- 12:17Post-mortems and debriefing
- 13:22Engineering low-risk releases
- 14:25Blue-green and canary deployments
- 16:35Feature toggles and dark launches
- 18:23Facebook’s dark launch example
- 19:05Value of feedback systems
- 20:11CI/CD and safe deployments
- 21:15Summary and call to action
related talks
01h 28mDon't Fail Fast -Learn Fast: Innovating Fast is a Must
22mPsychological safety: How to become a team that learns
36mPsychological Safety: Building fearless teams
59mThe continuous culture
53mDeliver Results, Not Just Releases: Control & Observability in CD
45m"Moving Fast at Scale"
30mLead Times and Psychological Safety within the Five Ideals
43mBetter Software Development Systems through Stress