Resources aka msOPS 30 repo aka msmymsignitethetour http

Resources aka. ms/OPS 30 repo aka. ms/mymsignitethetour

http: //www. americanairmuseum. com/aircraft/10376

Here’s our map

Here’s our map

Monitoring

Incident Response Monitoring

Post-Incident Review Incident Response Monitoring

Testing/Release Post-Incident Review Incident Response Monitoring

Capacity/Scale Testing/Release Post-Incident Review Incident Response Monitoring

UX Dev Capacity/Scale Testing/Release Post-Incident Review Incident Response Monitoring

UX Dev Capacity/Scale OPS 50 Testing/Release OPS 40 Post-Incident Review OPS 30 Incident Response OPS 20 Monitoring OPS 10

UX Dev Capacity/Scale OPS 50 Testing/Release OPS 40 Post-Incident Review OPS 30 Incident Response OPS 20 Monitoring OPS 10

Agenda

Why should we learn from incidents?

https: //aka. ms/csfail

2 2 https: //aka. ms/csfail

2 3 “Complex systems contain changing mixtures of failures latent within them. ” https: //aka. ms/csfail

2 4 “Complex systems contain changing mixtures of failures latent within them. ” “Complex systems run in degraded mode. ” https: //aka. ms/csfail

2 5

Language matters

Post-incident Review Baselines

Detection Readiness Response Lifecycle of an incident Analysis Remediation

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

So what’s the big idea?

You can’t fire your way to reliability. aka. ms/OPS 30 #MSIgnite

So what’s the big idea?

A post-incident review is NOT…

So what’s the big idea?

Step 1: Gather the data

Gather the data demos

4 3 Alphonse Chapanis

4 4

4 5

Four Common Traps

Trap 1: Attribution to “human error” aka. ms/OPS 30 #MSIgnite 47

Trap 1: Attribution to “human error”

Trap 2: Counterfactual reasoning aka. ms/OPS 30 #MSIgnite

Trap 2: Counterfactual reasoning

Trap 3: Normative language aka. ms/OPS 30 Microsoft Confidential Photograph by Nimish Gogri (https: //flic. kr/p/8 WXy 8 B) #MSIgnite 51

Trap 3: Normative language

Trap 4: Mechanistic reasoning aka. ms/OPS 30 Microsoft Confidential #MSIgnite

Trap 4: Mechanistic reasoning

Four Helpful Practices

Practice 1: Run a facilitated post-incident review aka. ms/OPS 30 #MSIgnite

1. Run a facilitated post-incident review

Practice 2: Ask better questions aka. ms/OPS 30 #MSIgnite

2. Ask better questions https: //aka. ms/etsydebriefing

Practice 3: Ask how things went right aka. ms/OPS 30 #MSIgnite

3. Ask how things went right

Practice 4: Keep review and planning meetings separate aka. ms/OPS 30 #MSIgnite

4. Keep review and planning meetings separate

To Review Run a facilitated post-incident review meeting Ask better questions Ask how things went right

Epilogue

UX Dev Capacity/Scale OPS 50 Testing/Release OPS 40 Post-Incident Review OPS 30 Incident Response OPS 20 Monitoring OPS 10

/MS Learn alert aka. ms/OPS 30 MSLearn. Collection

Microsoft. com/Certifications Microsoft. com/Learn aka. ms/Learning. Partner

Resources aka. ms/OPS 30 repo aka. ms/mymsignitethetour

/Upcoming session alert