OEE Top-Loss Diagnosis Workbook

Interactive workbook for frontline teams to intake OEE loss data, rank top availability/performance/quality losses, run 5‑Whys per loss, design small experiments, record success metrics, and capture sustainment steps — saved for team follow-up and continuous learning.

Interactive Tool

OEE Top-Loss Diagnosis Workbook

Purpose

This interactive workbook helps frontline teams quickly identify, quantify, and prioritize the top Availability, Performance, and Quality losses affecting your OEE. Use it to capture the facts, run a lightweight 5‑Whys for each top loss, propose and plan small experiments, and record the success metrics and sustainment steps that keep improvements in place.

How to use

  1. Complete the data intake for the line, shift and date range you are diagnosing.
  2. Enter up to five candidate losses (start with the ones that feel biggest).
  3. Estimate minutes lost and frequency so you can rank by impact; rank losses from 1 (highest priority) to 5 (lowest).
  4. For each top loss, run a short 5‑Whys, capture a hypothesis, and plan a small experiment you can try within a shift or two.
  5. Save the workbook, assign owners, run the experiment, record results, and use the sustainment checklist to lock in the gain.

Tip: If you have a continuous data source (MES/MES/OEE tool), use these fields to record the measured values and references so the team can later verify results.

Enter plant or site name (e.g., Plant A).
Where these losses are occurring (line name or number).
Which shift is being diagnosed.
Specify the date range or single date for this analysis (e.g., 2026-08-01 to 2026-08-07).
Where OEE / downtime numbers came from (MES, manual log, supervisor report).
Short context for the team (product mix, recent changes, known issues).
To prioritize, estimate impact = (minutes lost per event × events per period) or use your best available measure. Enter ranks 1 (highest) to 5 (lowest).
Describe the observed loss (e.g., Machine warm-up delay, sensor faults, scrap at operation X).
Estimate minutes lost each time this loss happens.
How often this typically occurs in a week.
Choose the main category that best fits the loss.
Assign a rank where 1 = highest priority (use unique ranks where possible).
Briefly describe the immediate cause you observed.
Why did this happen? (first answer)
Ask why again; build on prior answer.
Third why. Keep going until root cause feels actionable.
Fourth why.
Fifth why — capture the likely root cause.
Short hypothesis: if we [change / fix], then [expected measurable outcome].
Plan a small, time-boxed test (who, what, where, how long, data to collect). Keep it low-cost and reversible.
How will you know the experiment worked? (e.g., reduce minutes lost per occurrence from X to Y, reduce frequency from A to B). Include measurement method and sample period.
Who will run the experiment and collect results?
Target date for experiment or evaluation (YYYY-MM-DD).
Actions to lock in the improvement if the experiment succeeds (training, standard work, poka-yoke, spare parts, schedule change).
(Optional) Enter another loss to analyze.
(Optional)
(Optional)
(Optional)
Select actions you will perform if the experiment succeeds.
Where and how you will collect data to validate the experiment result (who, what, when, sample size).
Express as minutes saved, % availability/performance/quality, or other measurable benefit.
Who will do what next and by when.
After the experiment, record outcomes, unexpected learnings, and further actions.
You can explore this tool now. Sign in or create an account to save your responses and return to them later.
Make this tool part of your work

Save a personal copy, bring it to your team, or tailor the questions and workflow to fit what you are hungry to improve.

Member customization and team collaboration are coming soon.

Discussion

Comments and conversation will live here.