Good RCA: Produce some useful documentation to prevent issue from recurring.
Fantastic RCA: Remove requirement that caused the action that resulted in the problem occurring.
Bad RCA: Lets get 12 non technical people on a call to ask the on call engineer who is tired from 6 hours managing the fault, a bunch of technical questions they don't understand the answers to anyway.
(Worst possible fault practice is to bring in a bunch of stakeholders and force the engineer to be on a call with them while they try and investigate the fault)
Worst RCA: A half paragraph describing the problem in the most general terms to meet a contractual RCA requirement.
Fantastic RCA: Remove requirement that caused the action that resulted in the problem occurring.
Bad RCA: Lets get 12 non technical people on a call to ask the on call engineer who is tired from 6 hours managing the fault, a bunch of technical questions they don't understand the answers to anyway.
(Worst possible fault practice is to bring in a bunch of stakeholders and force the engineer to be on a call with them while they try and investigate the fault)
Worst RCA: A half paragraph describing the problem in the most general terms to meet a contractual RCA requirement.