Building resilience in our organizations...
summary
Argues that resilience depends less on tech stacks and more on repairing trust after incidents, claiming deployment is an act of courage and failures mainly erode trust. Recommends concrete practices: checklists, monitoring, automated tests, clear job expectations, peer and self ratings, and a promise cycle (clarify, commit, act, report, review). Offers an actionable behavior checklist using elements like reliability and confidentiality to locate breaches and guide repair so teams actually recover.
AI-written summary · about
chapters (18)
- 0:00Intro
- 0:27Have you ever
- 0:58The reasons
- 1:13Building resilience
- 1:28Cost of change
- 1:43Complex systems
- 1:58Uncertainty
- 2:13Managing uncertainty
- 2:28Deploying is an act of courage
- 2:43Risk and vulnerability
- 2:57Trust
- 3:12Expectations
- 3:27Clear Job Expectations
- 3:43Promise Cycle
- 3:58Trust and Failure
- 4:13Behaviors
- 4:42Trust and resilience
- 4:58Conclusion
related talks
22mResilience Is Not Enough
24mResilient Systems Require Resilient People
44mDeveloping a Culture of Reliability and Resilience through Chaos
13mApplication Resilience - Whose Job Is It Anyway?
43mResilience Engineering Mythbusting
20mRefactoring Trust on Your Team
34mResilience Isn’t a Buzzword
05mWhat is resilience engineering