/ Supervisor course
0 / 5
Progress saved on this device
KF·CS-01 · 22 min · Module 1 of 5

The shift, before it starts

A shift run well is decided before the line moves. This module shows you how to stand up your shift from the ranked queue so you walk the floor knowing where the loss is, what already has an owner, and what is still open.

Read the queue top-down, by dollars

Open the ranked findings queue before your pre-shift walk. KaizenFlow orders findings by verified or estimated dollar impact, not by recency or severity color. Your job is to read top-down and stop where the money stops mattering for one shift. The top three to five findings are your shift agenda; everything below is awareness, not action.

For each finding at the top, note three things: which station and reason code it ties to, whether it is a recurring loss or a one-off, and what the live tiles (OEE, downtime, scrap) say about it right now. If a finding is high-dollar but the station is already running clean this shift, it moves to watch, not work.

  • Sort by impact, read top-down, stop where the dollars stop.
  • Tag each top finding: station, reason code, recurring vs one-off.
  • Cross-check the live tile before committing it to the shift agenda.

Separate owned from open

Every finding is in one of three states: owned (someone is on it), open (no owner yet), or carried (handed from the prior shift). Your first accountability move is to make the open set as small as possible before the huddle, not during it.

Check the handoff notes from the outgoing supervisor against the queue. A carried finding with no closure note is still open — treat it that way. Do not assume a finding moved just because a shift passed. You are standing up the shift to know exactly what is unowned the moment the crew arrives, so the huddle assigns rather than discovers.

Key takeaway

Walk in already knowing your top three by dollars, who owns them, and what is still open — the huddle assigns work, it should not discover it.

Try it: stand up the shift · hands-on

You arrive 20 minutes before crew. The ranked queue shows a $4,200/wk recurring changeover loss at Station 3 (no owner), a $900/wk one-off scrap spike at Station 7 (owned, fix verified last shift), and a $3,100/wk recurring micro-stop pattern at Station 1 carried from two shifts ago with no closure note.

What do you do first?

Quick check

How does the KaizenFlow findings queue rank items by default?