OEE Operator Coaching Script — 5‑Minute Frontline Guide

Purpose

This is a compact, repeatable coaching script designed for supervisors and coaches who need a five‑minute, operator‑centred conversation that focuses on measurable OEE gains. Use it on shift handover, during gemba, or after a significant stoppage. The script emphasizes brief data review, a focused root‑cause prompt, one small experiment, clear success criteria, and a follow‑up assignment.

Why this works

Short, consistent coaching keeps operators engaged, converts observations into rapid experiments, and prevents chasing superficial KPIs. The script purposely limits scope so the team can try one thing, measure it, and learn quickly.

Five‑minute script (ready phrasing)

1. Opening (0:00–0:30)

   “Thanks for a minute — I want to check one thing together so we can make this run easier. I’m focusing on quick wins we can test in one shift.”

2. Quick data review (0:30–1:30)

   Show the operator the three OEE components and a single short note on the top loss. Keep numbers simple and visual if possible.

   Script: “Right now your OEE is [X]%. Availability is [A]%, Performance is [P]%, Quality is [Q]%. The top loss this shift is [loss category — e.g., changeover/idle/rejects].”

3. Root‑cause prompt (1:30–2:30)

   Ask one open, non‑leading question to surface the operator’s view of the immediate cause.

   Script: “What do you think is the main reason for that loss right now? If there’s one small change that would help this run, what would it be?”

4. One experiment to try (2:30–3:30)

   Agree on a single, small experiment that the operator can do during the shift. Keep it time‑boxed and low risk.

   Script: “Let’s try this for the next [N hours / this shift]: [describe the single action]. It should take less than [time estimate] to apply and won’t stop production if it doesn’t work.”

5. Success criteria & measurement (3:30–4:15)

   Define exactly how you’ll judge success—use one numeric or observable sign.

   Script: “We’ll call it a success if Availability improves by > [X] min or Performance improves by > [Y]% or rejects fall by [Z] pieces in the next [time window]. If we don’t see that, we’ll stop and try the next idea.”

6. Follow‑up assignment and close (4:15–5:00)

   Assign who will record results and when to check back.

   Script: “Can you try that and note what changes? I’ll check back at [time] or at the next handover. If it helps, we’ll add it to standard work.”

Quick data card (use this during the conversation)

Fill these fields on a clip‑note or whiteboard to make the experiment measurable:

• Machine / Line:
• Date / Shift:
• Baseline OEE: [X]% (A: [A]% P: [P]% Q: [Q]%)
• Top loss category: [loss]
• Experiment (one sentence):
• Expected effect (numeric if possible):
• Success criteria & measurement window:
• Who records / follow‑up time:

Examples of short experiments

• Reduce tool changeover time: pre‑stage the top three parts on a cart and time the next changeover.
• Minimize micro‑stops: if sensor fouling causes brief stops, try a quick cleaning and watch the next hour for reduced micro‑stops.
• Improve feed reliability: confirm hopper level procedure and record whether hopper‑related stoppages drop.
• Quality catch point: move a visual check earlier in the flow for the next 50 parts to see if rejects drop.
• Operator ergonomics: try a small workstation adjustment to see if cycle time variability reduces.

Coaching tips — what to avoid

• Avoid giving a long diagnosis or dozens of suggestions. One experiment is enough.
• Do not use the conversation to blame. Coaching is about testing and learning, not punishment.
• Don’t accept vague success criteria — insist on a measurable sign of improvement or a quick step to stop the experiment.

What good follow‑up looks like

Follow up at the agreed time, review the recorded measurement, and either:

• Standardize the change if it produced measurable improvement (update standard work and share), or
• Scale or modify the experiment if partial improvement occurred, or
• Try a different small experiment if there was no benefit.

Short example dialogue

Supervisor: “Quick check — your OEE is 68% this shift; Availability 82%, Performance 88%, Quality 94%. I see the top loss is wait time in changeover. What one small change might cut a minute or two from that?”

Operator: “If I pre‑stage the dies on the cart, we could shave off set‑up time.”

Supervisor: “OK — try pre‑staging for the next changeover and I’ll check at 10:30. If setup time is down by at least 2 minutes, we keep it. Who will note the time?”

Quick checklist to print and keep on the floor

• 1‑minute opening: state purpose and focus on one thing.
• 30–60s data review: A / P / Q and top loss.
• 30–60s root‑cause prompt: ask operator’s view.
• 60s agree one experiment with measurement window.
• 30s assign follow‑up and close.

Notes on measurement and habit

Small experiments won’t always change OEE immediately. The goal is to create a steady cadence of experiments, measurement, and standardization. Record each trial so you can see which small fixes accumulate into measurable improvements.

If you want this as a fillable log or a checklist that stores responses automatically, this guide can be converted into an interactive form or a simple OEE experiment tracker that captures baseline numbers, experiment details, and results.