Improvement Coaching Rubric for Supervisors

Why this rubric matters

Supervisors often want quick fixes: solve the problem, close the ticket, keep the line moving. That’s understandable — but it limits your team’s ability to solve new problems without you. This rubric helps supervisors shift from doing to developing: run short, consistent coaching interactions that grow problem-solving capability and make improvements stick.

What you’ll get

A simple four-level coaching rubric (observe, ask, guide, teach), sample scripts you can adapt to the shop floor, three role-play scenarios to practice, a 30‑day micro-plan for building a habit, and quick measures to know whether coaching is working.

The four-level coaching rubric

Use these levels to decide how to show up in a coaching interaction. Think of them as a spectrum from low to high ownership by the coach. The goal is to spend most interactions in the Ask/Guide space so teams develop ownership.

Observe

When to use: initial awareness, safety, or when you’re collecting facts before a coaching conversation.

• Coach behaviors: quietly watch, take notes, avoid immediate judgment, record facts.
• Sample actions: time the operation, note sequence of steps, capture error frequency.
• Indicator of need: recurring issue with unclear cause; team unaware of the pattern.

Ask

When to use: help the team reflect and surface root causes without giving the solution.

• Coach behaviors: ask open questions, listen, encourage the team to propose hypotheses and next steps.
• Sample questions (scripts):
  • "What happened from your point of view? Walk me through it."
  • "What did you expect to happen? What actually happened?"
  • "What do you think is the smallest change we could try to test that idea?"
• Indicator of success: team generates at least one plausible testable idea and agrees on who will try it.

Guide

When to use: the team needs help framing experiments, choosing measures, or identifying risks—but you still keep ownership with the team.

• Coach behaviors: suggest framing, offer a short checklist, propose simple metrics, help design an experiment—don’t hand down solutions.
• Sample prompts/scripts:
  • "If we want to see whether X is the problem, what could we measure for one shift?"
  • "Try this small test and report back in two shifts. What will you measure?"
• Indicator of success: a clear experiment with a small scope, owner, timebox, and metric.

Teach

When to use: introduce a new method, tool, or concept that the team doesn’t know (e.g., basic 5S step, simple SPC idea, or a safety lockout step).

• Coach behaviors: give a concise demonstration, explain rationale, observe practice, and confirm understanding.
• Sample script:
  • "Here’s a five-minute demo of the checklist. Watch me, then you try. I’ll give feedback on two things I want you to keep doing and one to improve."
• Indicator of success: team can repeat the step reliably and explain why it matters.

Sample role‑play scenarios (practice scripts)

Run these in 10–15 minute practice sessions with a peer so coaching moves become habits.

1. Scenario: Frequent minor stoppages at a machine.

   Goal: Use Ask → Guide. Start by asking the operator to describe the stoppage pattern, avoid suggesting a fix, help them design a one-shift test (e.g., record stops and what changed immediately before each stop).

2. Scenario: New operator struggles with part orientation causing defects.

   Goal: Observe → Teach. Observe the task, demonstrate the correct orientation, then have the operator repeat while you look for two positive behaviors and one correction.

3. Scenario: Team tried a Kaizen but gains faded.

   Goal: Ask → Guide. Ask the team what changed after implementation, identify handoff or standard work gaps, and co-design a one-week sustainment checklist owned by the team.

30‑day micro‑plan to build coaching habits

Run short consistent behaviors. Aim for 5–10 focused coaching interactions per week.

1. Week 1 — Observe & Ask:
   • Days 1–3: Spend 10 minutes each day observing a process and taking factual notes.
   • Days 4–7: Hold three 5–10 minute Ask-style coaching conversations using the sample questions. Capture one test idea from each conversation.
2. Week 2 — Guide:
   • Run two experiments with the team. Help them design measures and timeboxes. Follow up on day 3 and day 7.
3. Week 3 — Teach and Sustain:
   • Identify one repeatable skill to teach (5–10 minutes). Confirm competency by observing practice and having the team demonstrate.
4. Week 4 — Reflect & Scale:
   • Review all tests and outcomes with the team. Decide which changes to standardize into daily checks or standard work.

Quick coaching checklist (use on the floor)

• Did I observe first (facts only)?
• Did I ask open questions and listen at least 60% of the time?
• Did the team propose the next step or test?
• Is there a named owner and timebox for the test?
• Did I avoid giving a full solution unless safety or regulatory risk required it?

Suggested measures to track progress

• Coaching interactions per supervisor per week (target: 5–10).
• % of interactions ending with a team-owned experiment or next action.
• Follow-up completion rate within agreed timebox.
• Number of improvements standardized into the team’s standard work per month.

Common pitfalls and how to avoid them

• Micromanaging: If you find yourself doing the work, step back and ask a question that hands the choice back to the team.
• Too much teaching: Reserve Teach for clear skill gaps. Otherwise, favor Ask or Guide.
• Infrequent follow-up: Schedule short follow-ups during the original conversation so experiments don’t die.

Next steps and capability ideas

To make this guide operational, consider adding:

• A simple Coaching Log form (date, operator, problem, rubric level used, agreed test, owner, timebox, outcome) so supervisors can track interactions and improvements.
• A dashboard that aggregates coaching frequency, follow-up rate, and improvements standardized as standard work.
• A short peer practice routine where supervisors run 15-minute role-plays weekly.

These additions turn good intent into persistent capability: the data helps leaders coach better, spot where managers need practice, and celebrate learning wins.

Use this rubric as a living tool — adapt the scripts to your language, keep experiments small, and celebrate when the team owns the next step.