Tweet
Tweet

Slide 1

Slide 1 text

time “Safety-I”

Slide 2

Slide 2 text

time “non-incident” time continual preventing and catching of incidents “Safety-II”

Slide 3

Slide 3 text

There is no “one weird trick” to understand Resilience Engineering and that’s ok! John Allspaw Adaptive Capacity Labs

Slide 4

Slide 4 text

Resilience Engineering is a FIELD Cybernetics Ecology Safety Science Biology Control Systems Human Factors & Ergonomics Cognitive Systems Engineering Complexity Science Cognitive Psychology Sociology Operations Research

Slide 5

Slide 5 text

Resilience Engineering is a COMMUNITY Rail Maritime Surgery Intelligence Agencies Law Enforcement Aviation/ATM Space Mining Construction Explosives Firefighting Anesthesia Pediatrics Power Grid & Distribution Military Agencies Software Engineering

Slide 6

Slide 6 text

Resilience Engineering is a COMMUNITY Rail Maritime Surgery Intelligence Agencies Law Enforcement Aviation/ATM Space Mining Construction Explosives Firefighting Anesthesia Pediatrics Power Grid & Distribution Military Agencies Software Engineering

Slide 7

Slide 7 text

resilience is not these things • redundancy • robustness • high-availability / fault-tolerance • Chaos Engineering • anything about software or hardware!

Slide 8

Slide 8 text

people are the source of adaptation activities to sustain adaptation

Slide 9

Slide 9 text

unforeseen unanticipated unexpected fundamentally surprising resilience plays out in the…

Slide 10

Slide 10 text

situational surprise Buy a ticket and win

Slide 11

Slide 11 text

Buy a ticket and win Don’t buy a ticket and win fundamental surprise situational surprise

Slide 12

Slide 12 text

“…proactive activities aimed at preparing to be unprepared” ability to handle fundamental surprises

Slide 13

Slide 13 text

Resilience is already present and happening in your org! it’s just difficult for us to “see”

Slide 14

Slide 14 text

example “in the wild” it’s needed for handling fundamental surprises we continually invest in the ability to deploy to production when it’s needed

Slide 15

Slide 15 text

• automated tests • availability of (and expertise involved) peer code review • availability (and familiarity with using) feature/config flags • people available and looking for signs of trouble, focusing attention • the ability to contact others who can help if necessary

Slide 16

Slide 16 text

“too academic?!” we can do this! it’s already happening

Slide 17

Slide 17 text

Understanding Resilience Engineering will take time the concepts are not intuitive and also critically important

Slide 18

Slide 18 text

Change Is Afoot 2018 2019 J. Paul Reed 2018 Nora Jones Casey Rosenthal 2020 Jessica DeVita Chad Todd Tim Tischler 2021 Learning From Incidents In Software http://learningfromincidents.io

Slide 19

Slide 19 text

bit.ly/BoneResilience The next talk you see on this topic should be

Slide 20

Slide 20 text

ResiliencePapers.club LearningFromIncidents.io AdaptiveCapacityLabs.com/blog ResilienceRoundup.com Thanks!