Point Kaizen

Point kaizen is the most common shape of continuous improvement on the shop floor. The scope is small on purpose: one workstation, one task, one local fix. An operator notices the calipers live three steps too far from the bench, moves them, and updates the standard work sheet. That is a point kaizen. Done well, a shop runs dozens or hundreds of them a year. They individually look unimpressive. They collectively transform the floor.

"Most lean wins look like nothing. They're a bin moved six inches, a checklist with one extra line."

How point kaizen works

Point kaizen has three characteristics that distinguish it from a project. Narrow scope: the change affects one workstation, one task, or one local area. Short cycle: the fix can be tested and locked in within hours or days, not weeks. Local authority: the operator or shift lead has the standing authority to make the change without escalating to management.

The mechanics are straightforward. An operator spots a small problem during their work. They suggest a change at the morning huddle or directly to the shift lead. If the change is uncontroversial and clearly local, it gets tried that day. If it works, the local standard work gets updated to reflect the new method. If it does not, the change is reversed and the team picks a different small experiment. The whole cycle is fast and visible.

The discipline that makes point kaizen productive at scale is the loop with standardization. Without a current standard, every local change is one person's opinion and the next shift undoes it. With the standard, the change becomes the new baseline, the next operator runs it the new way, and the gain holds. The relationship is symbiotic: standardization makes point kaizen durable, and point kaizen keeps the standard current.

The other discipline is keeping bureaucracy out. A point kaizen that requires a form, a manager review, and a quality sign-off is no longer a point kaizen. It has been moved into project work where the cycle is now weeks. The whole value of the format is that the loop from idea to change is hours. Add friction and you kill the format.

Where point kaizen fits on the shop floor

Imagine a 28-person electronics assembly shop running short-run jobs for a mix of small B2B brands. Output is acceptable but the floor feels chaotic. Tools wander between benches. Operators walk farther than they should. Setup at the wave-solder station takes longer than it has to.

A year of point kaizens would handle most of this. Week one, an operator puts shadow boards on the top 10 hand tools at each bench. Week two, the kitting cart moves three feet closer to the assembly bench. Week three, the wave-solder setup gets a new checklist that puts pre-heat at the start instead of the middle. Week six, the inspection bench gets a small fixture that holds parts at the right angle instead of letting operators eyeball them. None of these is a project. Each one is a point kaizen done by an operator or shift lead in a day or two.

After a year, the shop has 60 or 70 point kaizens behind it. Lead times have dropped 30 percent. The change is not from any single fix. It is from the accumulated effect of small local improvements that each took less than a week.

Common mistakes with point kaizen

• Treating it as the whole answer. Point kaizens polish each station while ignoring the gaps between stations. Flow kaizen is needed for the cross-process work.
• Adding bureaucracy. Forms and approvals kill the format. The fast loop from idea to change is what makes point kaizen valuable.
• No standardization underneath. Without a documented current method, every change is just an opinion and the next shift undoes it.
• Confusing it with suggestion submission. Suggesting an idea is not a point kaizen. The kaizen is the change actually being tested and folded into the standard.
• Picking too-easy targets forever. Point kaizen should still test things that might fail. A shop that only runs improvements certain to work is not really improving.

Point kaizen and related Lean tools

Point kaizen is the small local cousin of flow kaizen, which addresses whole value streams. Both are types of kaizen, the daily continuous improvement habit. Many point kaizens come out of a focused kaizen event, the short-duration workshop format that concentrates a team on one specific problem area. The diagnostic tool often used inside a point kaizen, especially when motion waste is the suspect, is the spaghetti diagram, which traces operator and material movement to reveal local waste.