Safety Knights

We used the 5 why method but I feel like the fishbone method could be a lot more thorough because it has you look at all the different components that could of lead to an incident. The problem is the amount of time it takes to do the RCA! If only we had more time to really dig deep! You have to make time for the RCA though because you obviously want to solve the REAL reason why an incident occurred.

It all depends on the type of incident. The 5 why method is simple, but implies that there's only one causal factor, which usually isn't true. There are often multiple causal factors.

I've used a fault tree analysis (FTA) in a lot of incidents resulting in an injury or illness.

If it involves process safety, usually an FMEA/PFMEA is beneficial.

If it involves machinery, a fishbone diagram is usually my go-to.

I don’t think any one method or system is sufficient. I use a combination of Tap Root®️, 5 Whys and others as needed and depending upon complexity.

Fall tree analysis preferred for me. (Oops, accidentally hit the “report to admin” button)

5-why is our primary, but we also rely heavily on fishbones, FMEA, fault tree analysis and others.

Way back in my Tier 1 Auto Supplier Days (1976-1995), we used Ford's "8D" (The 8 Disciplines of Problems Solving) process. All three domestic auto makers used that format up to at least "95" when I moved to hydraulics, so I do not know about Auto since.
In 2001 my former employer started a Lean Transformation, which we achieved about 2005. ALL PROBLEMS, including all OSHA Recordables and "Serious Near-Misses", required the "A3" process. A3 stands for the type and size paper an "A3" is printed on. In process the "A3" is very similar to "8D" except it adds two more disciplines (steps), Teamwork and Follow-up.
An "A3" and "8D" use all kinds of PS techniques, some examples, Low Hanging Fruit, 5-Why, Pareto, Fish-Bone, Tauguchi DOE, and on and on. Remember "A3" is a Lean Principle so must have two essential things, all goals mush be SMART (Specific, Measurable, Achievable, Realistic, and Time-Bound), and the entire "A3" must follow PDCA (Plan, Do, Act, Check). A3 is a PROCESS that may use several PS techniques at the same time!
Been out of the Corp world for 5 years now. AS a consultant when I talk to my small manufacturing clients, I ask about PS, they shrug, look puzzled, and say, "What?"
Even though it has been 5 year, after 41 years doing PS I can do an A3 in my sleep! Like riding a bike!

I use event and causal factors mapping. It helps determine the questions that need to be asked, documents the timeline of the event, and, if done correctly, identifies the causal factors. It also helps determine the true root cause. For each causal factor, the 5-Whys is used to drive to the root cause, direct cause, and/or contributing cause(s). It is a lot of work, but in my humble opinion, it is a priceless tool that combines the best of all the tools. Lastly, it gives a pictorial representation of the event, which can be used to debrief the sponsor/owner of the root cause.

typically for incidents, it's 5 why/taproot. When engineering new methods/machines/components, its FMEA

Since no one has yet mentioned it, I enjoy using the Think Reliability Cause Mapping for root cause. https://www.thinkreliability.com/
It is a great tool, as it can incorporate the 5 why and fishbone in one convenient Excel sheet.