Daily Kaizen does not need a complicated form. It needs a simple questioning routine that helps supervisors see the gap, coach the team, and take the next small step.
Quick Answer
The five daily Kaizen questions are: what should be happening now, what is actually happening, what is blocking the team, what small action can we test, and what did we learn. Used consistently, they move supervisors from firefighting to coaching and practical improvement.
Many supervisors are promoted because they are reliable, technically strong, and willing to take responsibility. Then they are expected to lead improvement with very little routine to follow. They are told to support Kaizen, sustain 5S, reduce downtime, improve output, and motivate the team. But during a live shift, those instructions are too broad to be useful.
What supervisors need is a simple habit. A short questioning routine that can be used at the line, during a problem, without turning every issue into a meeting.
Why Questions Beat Instructions
When a supervisor gives instructions too quickly, the team may follow the order but miss the learning. The same problem then returns because nobody understood the process condition that created it.
Good questions slow the reaction just enough to see the real obstacle. They also build ownership. Instead of the supervisor becoming the only problem solver, the supervisor becomes the person who helps the team think clearly about the work.
Question 1: What Should Be Happening Now?
This question defines the expected condition. Without it, every problem discussion becomes subjective. One person says the line is okay. Another says it is behind. A manager says output is too low. Nobody is comparing against the same standard.
The answer should be specific enough to observe. For example: "By 10:00 a.m., we should have completed 200 units, Line 1 should be running at 48 seconds per cycle, and material for the next two hours should already be staged."
Question 2: What Is Actually Happening?
This brings the discussion back to the floor. Not what the report says last week. Not what the supervisor thinks usually happens. What is happening now?
The answer should come from observation. Count the output. Watch the cycle. Look at the queue. Check the rejected parts. Ask the operator to show the difficulty. Daily Kaizen becomes weak when it is based on memory and opinion.
Question 3: What Is Blocking the Team?
This question separates symptoms from obstacles. "We are behind target" is not an obstacle. It is the result. "The operator waits 20 seconds every cycle for label printing" is an obstacle. "The inspection decision is delayed because the sample tray is not clearly identified" is an obstacle.
Supervisors should push for one clear obstacle at a time. When the team lists ten reasons, nothing moves. When the team agrees on the next obstacle, Kaizen becomes manageable.
| Weak answer | Better answer | Why it helps |
|---|---|---|
| Manpower issue | Packing needs two people from 9:00 to 11:00 because carton changeover overlaps with peak output | Shows when and where the gap occurs |
| Machine problem | Sealer temperature drops after 40 minutes and creates rework | Points to a testable condition |
| Operator mistake | The left/right part orientation is not visually obvious at loading point | Focuses on process design |
| Quality slow | First-piece approval waits because the sample tag does not show priority | Identifies the decision delay |
Question 4: What Small Action Can We Test?
The action should be small enough to try quickly and safe enough that it will not create a bigger problem. This is not the time to design a full project plan. It is the time to take the next sensible step and learn from it.
Examples: move a tool closer for one shift, test a temporary visual mark, change the material staging sequence for one product family, or check whether the defect happens after a specific machine condition.
Question 5: What Did We Learn?
This is the question most factories skip. After the action is taken, the supervisor should return and compare expectation with result. Did output improve? Did waiting reduce? Did the defect disappear? Did a new problem appear?
If the test worked, the next step is to stabilise it. If it did not work, the team still learned something about the process. That learning should guide the next action, not trigger blame or abandonment.
Turning Questions Into a Habit
The five questions are simple. The difficulty is consistency. Supervisors need practice, coaching, and a management system that values learning before blame. Otherwise, the routine disappears when the line gets busy.
This is why supervisor capability matters in lean implementation. Tools like 5S, standard work, OEE, and problem solving only hold when supervisors know how to guide daily behaviour. For many factories, developing that habit is the real starting point for sustainable Kaizen.