OEE loss diagnosis workbook

Interactive, step-by-step workbook to quantify, validate, root-cause, and prioritize your top availability, performance, and quality losses. Designed for cross-functional kaizen sprints and operator-centered experiments — captures evidence, owners, containment actions, experiment plans, and measured results.

Interactive Tool

OEE loss diagnosis workbook

Purpose

This interactive workbook helps your team capture the top OEE losses, validate the data, record root-cause hypotheses with evidence, and turn the highest-value opportunities into short experiments with clear success criteria. Run this after a baseline OEE measurement and use it with a cross-functional team for focused improvement sprints.

How to use

  1. Enter baseline OEE and team context.
  2. List your top losses (up to five). For each loss, record measurement, data source, validation checks, root-cause hypothesis, evidence, owner, containment actions, and an experiment idea.
  3. Score expected impact (1–10) and ease (1–5) to prioritize—calculate a manual priority score or use the prioritization notes to decide.
  4. Plan short experiments, record results, and update the workbook. Repeat until the loss is reduced to an acceptable level.

Use concise, evidence-based entries. Avoid vague descriptions — include timestamps, data sources, and tangible measures whenever possible.

Date or date range for the baseline OEE measurement (e.g., 2026-08-01 to 2026-08-07)
Overall baseline OEE as a percentage (e.g., 62.5)
Portion of scheduled time available (e.g., 85)
Speed efficiency (e.g., 92)
Good parts portion (e.g., 99.5)
List participants, line/area, shift, and product or process being examined.
Fill each Loss slot for your top 1–5 losses. Use precise names (e.g., 'Changeover delay', 'Motor failure', 'Operator adjustment', 'Quality: burrs causing rework').
Short descriptive name
Minutes lost or percent lost. Also enter units in the next field.
Where this number comes from (MES, shift log, timestamped observation, operator count)
Quick validation: Have you checked source timestamps, sensor logs, or operator logs?
State your best-root cause hypothesis in one sentence (e.g., 'Changeover takes extra 12 minutes due to missing tools and non-standard sequence').
Attach or describe concrete evidence: timestamps, photos, error codes, witness names, sample parts, trending data.
Name and role of the person accountable for running the containment and experiment.
Immediate actions to contain the loss while you test experiments.
A short, time-boxed experiment you can run in hours or days (not a long project). Include the change, how you'll apply it, and how long it will run.
Estimate how big the impact would be on the loss if the experiment succeeds (1 = tiny, 10 = game-changer)
Rate how easy and low-risk the experiment is to run
1.0 10.0
Optional: compute Impact x Ease or another formula locally and enter the priority number to sort your list.
Quick check: data validated, owner assigned, experiment defined.
1.0 10.0
Use this field to record which losses you prioritized and why (e.g., 'Loss 1 selected: high impact, low effort; Loss 2 deferred: requires capital spend').
Record the short experiments you run against prioritized losses. Keep entries concise and evidence-focused.
YYYY-MM-DD
Reference the loss slot name
If we do X, then Y will happen because...
How you will run the experiment, sample size, duration, controls
Quantifiable success criteria (e.g., reduce changeover by >= 6 minutes or reduce scrap by 50%)
Record follow-ups, required approvals, training, or items requiring deeper investigation.
Is the content confidential or restricted to this team?
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.