2 ms·
The author strikes me as someone focused on something other than incident and problem management. The answers or depend on what you’re looking at. The cause of
by Spooky23 5y ago
The author strikes me as someone focused on something other than incident and problem management. The answers or depend on what you’re looking at.
The cause of the incident used in the example is the configuration change. Resolution is rollback.
When you look at problem management, the root causes of the problem are likely process issues that need to be addressed. (Or not)
Think of a non tech example to help understand. Look at a picture of an early superhighway from the 1950s like the New York State Thruway, New Jersey Turnpike, etc. Notice that there are no guardrails or they are made of wood.
When a 1950s driver fell asleep and ran off the road, flipping and getting ejected from the car, he died. The cause of the incident was him falling asleep and losing control.
But for the highway engineer, many problems are introduced by this incident. The shoulder could be graded to avoid rollover. Appropriate barriers could prevent the rollover. Rumble strips wake up the driver. For the mechanical engineer at a car company, seatbelts prevent ejection, safety glass prevents eviceration, crumple zones prevent trauma.
None of those things prevent the guy from falling asleep in that incident. But they address the greater problem of highway fatality.
- curryst 5y agoRight, but those aren't things an RCA is meant to address. The RCA identifies the specific method of failure. It's the starting point on your process improvement. X failed because Y, why did we allow Y to occur? The answers to those questions become deliverables. An RCA doesn't handle those things because another section does. That way each team involved can look at what the issue was and how their team can prevent that. The authors solution eeks of a central committee that tells you how you could have prevented it, and they're often ineffective.