I like using the term "incident retrospective." It seems to convey that we would like to retrospect on the incident and learn from it.
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I feel like we embrace failure metaphors. The one that always comes to mind for me is breadcrumb navigation, which notably failed for Hansel and Gretel.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
This is approx the same as planning but not executing a chaos engineering experiment right?
@nora_js has spoken about the value of this. Perhaps interesting to contrast “we failed; how?” W/ “env changes; what happens?” - 1 more reply
New conversation -
-
-
How about more generally "debrief" instead of "post-mortem"?
-
Post-mortems establish the "cause(s) of death". IT services post-mortems establish the cause(s) of failure to provide the service. Sure, if the "patient' is the service, it might be alive, but if the "patient" was the SLA bucket, it is dead. Post-mortem should help prevent more.
End of conversation
New conversation -
-
-
I always thought it was the problem that you'd killed, not the system...
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Agreed it’s a better term. Just like it should be called a ‘go decision’ meeting not ‘go/no-go’
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
-
-
I first heard it in relation to engineering *projects* (and especially failed projects), where it makes more sense... The jump from there to operational incidents is natural but yeah (usually
) not the right term there.Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.