Similar here. Was pumped in an RCA with "why?" multiple times. The 'root cause' was I fucked up and missed something. But that was because "prod was broken right then, fix ASAP!" and no one else understands the problem, and we're understaffed, and people 'reviewed' the code without understanding what it was doing (or why) and one 'fix' led to another problem, and that 'fix' led to a third, and trying to explain this in an 'RCA' meeting confused the heck out of everyone because there were 3 different days/times people saw the problem, and could not understand it was one original thing that triggered, with cascading problems in the 'fixes', etc.
You keep asking "why?" and only want one 'thing' to be 'actionable'... you will raise my frustration level. The root cause is an emergent property of understaffing, poor communication practices and a belief that everything can be reduced to a jira card providing sufficient context and understanding for a diverse audience with different skills and needs.
You keep asking "why?" and only want one 'thing' to be 'actionable'... you will raise my frustration level. The root cause is an emergent property of understaffing, poor communication practices and a belief that everything can be reduced to a jira card providing sufficient context and understanding for a diverse audience with different skills and needs.