Root Cause Analysis

At OpenCraft, we do Root Cause Analyses (RCAs) for incidents, problems, or setbacks that require a deeper understanding of their underlying causes. The purpose of an RCA is to determine what went wrong and come up with ways to prevent similar issues from happening in the future.

When to Write an RCA

RCAs are written for scenarios such as:

• Security breaches
• Tasks taken from the Last Resort Backlog
• Stuck tickets incorrectly assigned to newcomers

Steps to Create an RCA

1. Visit the RCA folder in Drive
2. Check if an RCA already exists for this issue
3. If not, duplicate the RCA template
4. Give the new document a descriptive name
5. Follow the sections in the template to complete the document
6. Request a review from the CEO, as well as a team member with insight into the issue at hand
7. If more reviewers are needed, use the Core Committer field in the related Jira task
8. Address reviewers’ feedback and adjust the RCA as needed
9. Attend to any action items identified during the RCA process

You’re done! Thanks for taking the time to complete this RCA and help prevent similar hiccups in the future.

---

Last update: 2024-11-20