4 ms·
True. In a case this simple, you likely wouldn't have to write an RCA. However, most real life situations I've seen show that there's always room to improve. F
by awill 8y ago
True. In a case this simple, you likely wouldn't have to write an RCA.
However, most real life situations I've seen show that there's always room to improve.
For example, how quickly did your service recover once the underlying platform recovered. Rare events (like DC failure) can be a bad thing for operational training. Teams forget how to recover. No runbooks, no training, or tooling that's infrequently used no longer works.
- grogenaut 8y agoYou actually want to assign to root cause and track that. Them over time you build up data on if it's worth it to stay on one platform or not. Eg doing this let's you build a risk profile to counter the $/time argument against. Then you get to make an informed decision. You don't just shruggie and move in "that ship has sailed" at least if you're doing it right.