OEE Loss Prioritization Canvas — Frontline Worksheet
A practical, ready-to-use canvas to capture top availability, performance, and quality losses, estimate business impact, score quick-win potential, and create an owner-led experiment plan.
OEE Loss Prioritization Canvas — Frontline Worksheet
Use this canvas at the line, in a huddle, or during a rapid kaizen to capture the highest-value OEE losses and choose which to test first. The canvas helps teams estimate impact, check measurement confidence, surface root-cause hypotheses, and commit to a small experiment with an owner and success criteria.
How to use
- Collect candidate losses from operators, shift logs, downtime trackers, and quality reports.
- For each loss, estimate Frequency and Duration using the best available data (operator logs, machine counters, or reasonable observation). Record measurement confidence.
- Estimate Business Impact in minutes lost per day or units lost per shift (use a conservative estimate if data is uncertain).
- Score Quick-Win potential (how easy/fast to test and likely to reduce loss) and Evidence Confidence.
- Prioritize by a simple Priority Score (example formula below), pick top 1–3 to run rapid experiments, assign an owner and deadline, and define success criteria.
Canvas fields (table)
Fill one row per loss. Keep entries short — you can expand in a linked experiment plan.
| Loss # | Loss description | Type | Frequency | Avg duration / impact | Estimated business impact (min/day or units/day) | Measurement confidence (1–5) | Root-cause hypotheses | Required countermeasures (short) | Quick-win score (1–5) | Owner | Experiment plan & success criteria |
|---|---|---|---|---|---|---|---|---|---|---|---|
| 1 | Example: Changeover delays on line A | Availability | 2 per shift | Avg 12 min | 24 min/day | 4 | missing tools, untrained helper | pre-stage tools, one-point lessons | 4 | Shift lead — Maria | Test pre-staging on 1 shift for 5 days; success = reduce avg changeover to < 8 min (33% drop) |
| 2 | (blank) | (select Availability/Performance/Quality) | (e.g., 3/day) | (e.g., 6 min) | (calculate) | (1–5) | (hypotheses) | (countermeasures) | (1–5) | (owner) | (experiment plan) |
Scoring & prioritization
Keep scoring simple so teams can decide and act. Example approach:
- Impact score (1–10): translate the business impact into a 1–10 scale. For example, rank losses by minutes/day or units/day relative to other captured losses.
- Quick-win score (1–5): how easy and fast is a low-risk test? 5 = very easy, can test in one shift with local resources. 1 = requires capital or long lead time.
- Confidence (1–5): how reliable is the measurement or observation? Low confidence means you may need a short validation step before a full experiment.
- Priority score (example) = Impact score × Quick-win score × (Confidence / 5). Use this to rank items — higher is better.
When to validate measurement first
If Confidence ≤ 2, plan a quick measurement check (one shift of focused observation or a short data pull) before committing resources. Low-confidence items often look big but may not be the right place to spend scarce improvement time.
Experiment plan (simple template)
- Objective: What are we trying to change and by how much?
- Hypothesis: If we do X, then Y will improve by Z within N shifts.
- Test steps: List clear, short steps the operator/owner will run.
- Data collection: What to measure, who records it, and when (before/during/after).
- Success criteria: Quantitative threshold or qualitative outcome that signals success.
- Owner & timeline: Who runs the test and deadline for results.
- Next action: If success → standardize; if partial → iterate; if no effect → capture learnings and re-prioritize.
Common prioritization mistakes (avoid these)
- Chasing the loudest complaint rather than the largest measurable impact.
- Prioritizing low-impact items with high visibility that demotivate teams when little progress occurs.
- Running big corrective projects before validating measurement or hypotheses.
- Ignoring operator input about feasibility and sustainment.
Suggested immediate next steps
- Run a 30-minute huddle to capture 6–10 candidate losses using the canvas.
- Estimate impact and confidence for each; compute priority scores and pick the top 1–2 to test this week.
- Assign owners, write a one-paragraph experiment plan, and schedule a short follow-up to review results and decide whether to standardize.
Where this canvas fits in a toolkit
This worksheet is a frontline tool for quickly translating OEE insight into actionable experiments. For a broader toolkit, pair it with:
- Standard experiment report template
- Short measurement validation checklist
- Visual dashboard for before/after results
- Operator-facing one-point lessons and standard work
Example image search phrase
oee losses whiteboard
Notes for facilitators
Keep the session tight and operator-led. The goal is measurable learning, not perfect root-cause analysis. Rapid, small experiments that prove (or disprove) hypotheses build momentum.
Discussion
Comments and conversation will live here.