Personnel Chaos Engineering and Building a Resilient Organizational Structure
summary
Uses deliberate chaos experiments on people tools and processes to find concrete failures and fix them for the lab opening: infrastructure chaos drops product failure probability from 0.75 to 0.15 and overall risk to 0.1125; security chaos finds an unencrypted DB so encryption at rest cuts that risk to a 0.35 probability; personnel tests like lying lemur and access monkey expose single approver bottlenecks leading to added backups, documentation, automated recovery and a peer structure that keeps the lab opening on time and wins a contract
AI-written summary · about
chapters (18)
- 0:00Start
- 0:48What Chaos Engineering Is
- 1:40Use Case
- 2:59Summary What Is Chaos Engineering
- 3:33Key Steps
- 4:12History Where Did Chaos Engineering Come from
- 4:48Chaos Monkey
- 12:20What Types of Tools and Tricks Can We Use for Organizational Chaos Engineering
- 18:30Tools
- 20:40Spammer Spider Monkey
- 25:20Building a Resilient Organization
- 26:02Peer Structure
- 31:54Mentoring
- 33:49Training and Development
- 35:02Tool Set Resiliency
- 36:58Process Resiliency
- 37:10Approval Management
- 37:48Show the Workflow for Processes by Default
related talks
27mImplementing Chaos Engr. in a Risk Averse Culture
43mBuilding a culture from Chaos
36mLeadership During Chaos
10mWho is responsible for Chaos?
23mBring Chaos to Your Org
43mBetter Software Development Systems through Stress
15mIncident Ready: Chaos Engineer Your Incident Response
42mRing-fence the Chaos: When Technical Teams Meet Organisational Systems