# Using 5 Whys Analysis (QMS)

QMS supports the ability for a user to perform and document a 5 Whys root cause analysis of a _Quality Event_, _Complaint_, _Deviation_, _Lab Investigation_, _Continuous Improvement_, or _Finding_.

A 5 Whys Analysis is a common cause-effect technique used to perform root cause analysis. The general approach is to start with your problem statement and ask "why" after each answer, forming the basis of the new "why" until you clearly identify the root cause.

## 5 Whys Analysis Tool

If enabled by an Admin, QMS includes the Root Cause Analysis Tool, which allows you to perform and document a 5 Whys Analysis in an easy-to-use interface. While the event which triggers a root cause analysis will vary depending on your organization's quality processes, the QMS 5 Whys Analysis tool is flexible and allows for a wide breadth of analysis variations. As you add Whys, root causes, and other information to the tool, a tree forms, showing your path and justifications.

## Performing a 5 Whys Analysis

Follow these steps to perform a 5 Whys Analysis in QMS:

  1. From the originating record, such as a _Quality Event_, _Complaint_, _Deviation_, _Finding_, _Continuous Improvement_, or _Lab Investigation_, navigate to the _Root Cause Analysis_ section.
  2. Click into the appropriate _Root Cause Analysis_ record or create a new record.
  3. Enter a Problem statement.
  4. Use the [5 Whys Analysis Tool section][1] interface to continue or complete your analysis against that Problem statement.
  5. Once you have completed your analysis, follow your business processes to move the _Root Cause Analysis_ record to the _Completed_ lifecycle state type. In some cases, this may include performing a user action on the _Root Cause Analysis_ record.

When a _Root Cause Analysis_ record enters the _Completed_ lifecycle state type, Vault automatically creates _Root Cause_ records of the appropriate type, if applicable, for each root cause identified in the Root Cause Analysis Tool, and data from individual _Root Cause Analysis Item_ records is transferred to the automatically generated _Root Causes_. Any data transferred in this manner cannot be edited later unless the user re-opens the analysis and updates the data via the interface.

If you reopen the analysis and change a _Root Cause_ value from **Yes** to **No** or **Not Determined**, the previously created _Root Cause_ record is removed. If you change the _Root Cause_ object type to another value, the previously created _Root Cause_ record is removed and recreated as the new type with the new data associated to that object type.

## About the 5 Whys Analysis Interface {#interface}

The Root Cause Analysis Tool section is a flexible interface for performing and documenting a 5 Whys Analysis. You can collapse or expand each box within the section to manage your view. The percentage drop-down in the top right of the section determines the zoom level.

### Adding a Why

The basic component of a 5 Whys Analysis is a Why? question and answer, along with a determination as to whether that answer is the root cause. To add a Why? box:

1. Click **+ Why**.
2. Enter an answer statement.
3. In the **Root Cause** drop-down, select **No**, **Yes**, or **Not Determined**:
   * **No**: Allows you to add new Why? boxes underneath the current box by clicking the plus (**+**) icon.
   * **Yes**: Allows you to enter additional information pertinent to the root cause. This information will be populated on the resulting _Root Cause_ record created when the _Root Cause Analysis_ enters the _Completed_ lifecycle state type.
   * **Not Determined**: Allows you to enter a justification reason as to why this line of Whys may not result in a definitive root cause.
4. Click **Save** in the Why? box to save the data entered and proceed. When you click **Save**, the fields are unavailable until the green Saved indicator is displayed at the bottom right of the Why? box.

### Expanding the Analysis

Anytime during the analysis, you can expand into a new line of Whys, discard Why boxes if they are unhelpful using the trashcan icon, or branch a line of Whys by clicking the plus (**+**) icon in an upper-level box. The Root Cause Analysis Tool supports up to ten (10) simultaneous trees, with up to 20 boxes in each one.

When you delete a Why? box, Vault renumbers any remaining boxes automatically. Deleting a Why? box also deletes boxes below it in the tree.

## Related Permissions

To perform a 5 Whys Analysis, you must have a role or permission sets that provide:

  * _Read_, and _Edit_ permissions for the _Root Cause Analysis_ object and _5 Whys Analysis_ object type
  * _Read_, _Create_, _Edit_, and _Delete_ permissions to the _Root Cause Analysis Item_ object and _Why_ object type
  * _Read_, _Create_, and _Delete_ permissions to the _Root Cause_ object
  * _View_ permissions on the _Root Cause Analysis Tool_ object control within the _Root Cause Analysis_ object permission settings

  [1]: #interface