--- title: "RCA Mechanism" slug: "rca-mechanism" tags: ["Root Cause Analysis", "5 Whys", "RCA", "RCA Mechanism"] updated: 2025-04-30T09:57:52Z published: 2025-04-30T09:57:52Z canonical: "help.symphonysummitai.com/rca-mechanism" --- > ## Documentation Index > Fetch the complete documentation index at: https://help.symphonysummitai.com/llms.txt > Use this file to discover all available pages before exploring further. # RCA Mechanism Root Cause Analysis (RCA) is a mechanism to uncover the underlying causes of Problem Records to prevent their recurrence. It involves a systematic process of data collection, problem identification, causal factor charting, and root cause identification, using methods such as the **5 Whys** analysis. The **5 Whys** technique aids RCA by prompting repeated "why" questions to uncover a problem's root cause. This approach addresses root causes, enabling lasting solutions that improve system reliability and customer satisfaction while fostering continuous improvement. Let us explore the following Use Case for the **5 Why** analysis! | **Use Case** **User Persona:** **Application Designer****Analyst** | **Solution** | | --- | --- | | NovaTech has been experiencing intermittent downtime on its customer portal, causing slow performance and delays in ticket submissions. As a result, users are frustrated, and there have been increased complaints about the portal's usability. | To address the issue, the Administrator activates the 5 Whys widget within the problem management module. This feature helps the analyst investigate the root cause by prompting them to ask a series of “Why” questions. Through this structured inquiry process, the analyst uncovers the underlying cause of the downtime and identifies an appropriate remediation strategy to resolve the issue and prevent future occurrences. | ## **Enable 5 Why Widget in Form Designer** The **5 Why** widget must be added in the Manage Problem Records Admin Form through the Form Designer. To enable the **5 Why** widget, perform the following steps: 1. Navigate to **Service Management** > **Design Studio** > **Module** > **Problem** > **Form** **Designer**. The list of Forms created for the Problem Management module is displayed. 2. Open **the Manage Problem Records** form. Click **Publish** to update the form's status to **Maintenance**. 3. Click **Design Form**. 4. Click **Widgets**, drag and drop the **5 Why** widget into the **RCA** tab. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-QMB11FGG.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=7NZfLeWdrEA4KCbbOch0pBLKjs00aVDKF9EarZI4sd4%3D) Figure: 5 Why 5. Click **Next** and **Publish** the form. ## **5 Why in Problem Record** The 5 Why widget appears on the RCA tab while creating a new Problem Record. While creating a Problem Record Analysts and Admins can choose Methodology as **5 Why** analysis. To create a new **Problem Record** using 5 Why analysis, perform the following steps: 1. Navigate to **Service Management** > **Problem** > **Manage Problem Records** > **New**. 2. Enter all the mandatory details for the Problem Record. 3. Click the **RCA** tab and select the **5 Why** from the **Methodology** dropdown. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-51D5DQU5.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=0qSwJrixrStCiOhmIrVuI9B19gNJsCQLZ%2FQ2uSDqslU%3D) Figure: Methodology 4. The **5 Why** analysis is displayed. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/image-KB50C5JF.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=wnvZr02wkqvos0whkkPZL9q%2FJv%2FCcHxra%2BC%2BV%2Fg5oaM%3D) Figure: 5 Why analysis The following table lists the fields available in the **5 Why** section. | **Field** | **Description** | | --- | --- | | Problem Statement | The symptom of the Problem Record is auto updated as the Problem Statement. **For example**: If the symptom of the Problem Record is Slow performance of the Customer Portal, then the Problem Statement is same as the symptom. | | Why | Specify the reason why the problem occurred. | | Description ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/rca-mechanism-image-lnu9h9cb.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=sc58wqBDSSQShLwbcBruhf9pAiD3PX0mS4RzGDsZ8io%3D) | Click the Description icon to enable the description box for each Why. | | Delete ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/rca-mechanism-image-n3p2jvzb.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=vckuemVEwLzR%2F0%2B3QJKygZDzGnoz%2BGG4jLyxbY1srhI%3D) | Click the Delete icon to delete the Why statement. | | Add![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/rca-mechanism-image-i9o6nclz.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=ATeWeS%2FW6ZSu8iC7xAdovpyDFxNP3QAX7yZ6thGVveA%3D) | Click the Add icon to add multiple Why statements. | Click **Save** to submit the Problem Record. After the created Problem Record is approved or moved to any further status from approved, the **Remediation** tab is displayed in the **5 Why** analysis. Remediation refers to the actions taken to address and fix the root cause identified through the process. Remediation is available for every Why statement. ![](https://cdn.document360.io/62351b42-cfbd-43ad-8ce1-82b8f455337f/Images/Documentation/rca-mechanism-image-05q9wel1.png?sv=2026-02-06&spr=https&st=2026-11-22T14%3A44%3A15Z&se=2026-11-22T15%3A44%3A15Z&sr=b&sp=r&sig=XM6wSElxZ5E2Uem0wUgvADJ9ThFs1F%2Bvra2La7j2Vsw%3D) Figure: Remediation The following table lists the fields available in the **Remediation** section. | **Field** | **Description** | | --- | --- | | Cause | Specifies the cause identified for the corresponding Why statement for the Problem Record. | | Description | This field offers an in-depth explanation of the identified cause, clarifying how it directly contributed to the issue. It provides valuable insights into the problem, facilitating effective remediation planning. | | Action Owner* | Select the action owner for the cause. The dropdown menu displays the names of the analysts. | | Status* | Select the status of the cause such as - New - In Progress, - Pending - No solution available, etc. | | Target Completion Date | Select the target completion date for the mentioned cause. | | Attachment | Attach the attachments related to the cause. | | Remediation | Specify the details of the remediation related to the cause. | | Remarks | Specify any additional remarks. | The Admin Forms are configurable forms. The Application Designer designs the Admin form and an Administrator provide the values for pre-designed fields in Admin Form. For Example - Priority Form