5 Whys Excel - Free Template

1. Open the Instructions tab first to review the purpose of each section and the meaning of the analysis fields.
2. Go to 5 Whys Analysis and enter the issue ID, problem statement, date identified, reported by, and department in an available row.
3. Ask why the problem occurred, then record the answer in Why 1. Continue through Why 5, treating each answer as the basis for the next question.
4. Write the root cause in Why 5, then document the corrective action, responsible owner, and target date.
5. Select Open, In Progress, or Closed in Status and High, Medium, or Low in Priority using the provided lists.
6. Review Days Open and the summary totals below the analysis area. Do not replace the Days Open formulas.
7. Open Dashboard to review the calculated metrics, department breakdown, status chart, and department chart.

A production supervisor can use this workbook after a machine failure, a quality manager can use it after a defect, and a logistics manager can use it after a late shipment. The sample rows show three concrete cases: an assembly-line breakdown, a Dallas shipment delay, and a product defect found during quality inspection.

Operations And Quality Investigations

Start with the event rather than a suspected solution. For the sample assembly-line issue, the five answers move from an overheated conveyor motor to a seized bearing, missed lubrication, an un followed preventive-maintenance schedule, and manual maintenance tracking that is often skipped. That chain gives the team a more useful corrective action than simply replacing the motor.

Cross-Department Follow-Up

The Department field lets a manager distinguish Manufacturing, Logistics, and Quality work from IT, Safety, Customer Service, Packaging, or Production issues. The Dashboard counts these departments separately, which helps an operations meeting focus on where investigations are accumulating instead of relying on anecdotal updates.

This format also suits a small warehouse, plant, or service operation that needs a shared issue register without introducing a separate system. One row contains the investigation and its follow-up, while the Owner and Target Date fields make responsibility visible.

The workbook uses three permitted status values: Open, In Progress, and Closed. The Status column drives the Days Open calculation, while the Dashboard counts each status with COUNTIF formulas and calculates the closed percentage from the closed count divided by total issues.

Days Open Logic

For an active issue, Days Open uses today's date minus Date Identified. For a closed issue, it uses Target Date minus Date Identified. In the sample, the quality issue identified on 07/03/2026 is marked Closed with a target date of 07/18/2026, so the calculated duration is based on 15 days rather than continuing to increase.

Controlled Inputs And Outputs

Status and Priority use list validation, which limits entries to the workbook's defined choices. The analysis rows are prepared through row 13, and the Dashboard formulas reference those rows. Days Open, summary counts, average duration, and charts are calculated outputs; the issue descriptions, five why answers, actions, owners, dates, and selections are user inputs.

The workbook is an operational tracker, not a live database. If you add rows above the summary totals, follow the Instructions sheet: copy the formatting and Days Open formula down, then update summary ranges as needed.

The most damaging failure is stopping at the first visible cause. In the sample late-shipment investigation, the truck left six hours late, but the analysis continues through dock congestion, two failed forklifts, delayed maintenance requests, and the absence of a backup-equipment plan. Recording only the six-hour delay would point the team toward the symptom instead of the control problem.

Weak Answers Produce Weak Actions

Answers such as employee error or equipment problem do not explain what process allowed the issue to occur. A useful Why 5 should be specific enough to support the Corrective Action field, such as adding reset verification to the training program or creating a backup-equipment plan with a maintenance service-level agreement.

Unowned Actions Stay Open

An action without an Owner or Target Date cannot be managed during a follow-up meeting. The sample rows show named owners and dates such as 07/15/2026, 07/18/2026, and 07/20/2026. Leaving those fields blank makes the Dashboard's open and in-progress counts look complete while the underlying work remains unassigned.

Another breakdown occurs when users overwrite Days Open or type inconsistent status labels. A single entry such as In progress instead of In Progress will not match the list-driven formulas, so the dashboard can undercount the real workload.

Choose one recurring review time, such as the weekly production meeting or the logistics team's Monday operations review. Before the meeting, update Status, Owner, Target Date, and corrective-action notes; during the meeting, use the Dashboard to decide which open or high-priority investigations need attention.

Keep Entries Consistent

• Use one clear problem statement per row rather than combining several events.
• Write each Why as a factual answer that leads naturally to the next question.
• Use the provided status and priority lists instead of typing alternatives.
• Leave Days Open formulas intact and review the result after changing dates or status.

Close The Loop

Do not select Closed merely because an action was assigned. Mark an issue closed after the corrective action has been completed and the responsible team has verified the result. The closed duration then uses the target date and remains stable instead of continuing to use today's date.

The workbook is a practical starting point for the prepared analysis area. If your team regularly manages more than the available rows, needs several investigators editing simultaneously, or requires audit history and notifications, move the process into a dedicated quality or operations system rather than relying on manual range updates.