Case study · US · Industrial
Industrial-Equipment Plant
$320k/yr verified savings · 92% audit participation
The results
Weekly walks plus the forklift traffic redesign cut OSHA recordables 38% year over year.
Weld-cell kaizens and faster closure of process defects took scrap cost down 29%.
Less rework and fewer material-damage delays shortened average order lead time 22%.
Finance-verified kaizen ledger; every line links to the defect or A3 that produced it.
Sustained weekly participation across 22 zones, and floor turnover down four points.
“I asked for last year's verified savings and got three weeks of spreadsheet archaeology. This year I asked again and watched my plant manager answer from his phone in the hallway.”
The starting point
The plant builds material-handling equipment across 240,000 sq ft. It had run continuous-improvement programs for a decade — kaizen events, idea boards, a lean consultant every couple of years. Each wave produced a burst of sticky notes and a binder of A3s, then faded. Nobody could say which ideas were implemented, which savings were real, or why the same forklift-damage problem starred in three consecutive kaizen events.
When a new VP of Operations arrived, her first question was simple: 'Show me last year's improvement savings, verified by finance.' The answer took three weeks to assemble and nobody fully believed the number.
What changed, step by step
One connected loop: audit, defect, fix, root cause, kaizen, standard, recognition. Open any step to see what it did at this plant.
Step 1 · Audit · 5SFrom annual event to weekly habit
The team stood up 22 zones across fabrication, weld, paint, and assembly. Supervisors walk weekly; the walk is twelve minutes with a phone, and coverage is tracked, so 'we audited the plant' means every zone, every week — not the two zones near the office. Participation hit 92% by month two and stayed.
Step 2 · DefectsThe forklift problem finally showed its shape
With every ding, leak, and near-miss photographed into one board, the AI's repeat-detection did what three kaizen events had not: it showed that 60% of rack damage clustered on two aisles during shift change. The problem was never 'careless drivers' — it was a traffic pattern.
Step 3 · Fix-PlanOwners and due-dates instead of action-item lists
Fix-plans are drafted by AI from the defect photo and history, then assigned with a due date and a required after-photo. The Friday 'open actions' spreadsheet died; the board is the meeting. Median closure time fell from 31 days to 8.
Step 4 · Root cause · A3One A3 ended a decade of forklift kaizens
The traffic-pattern insight became a proper A3: fishbone across the 6Ms, a 5-Why thread into Method, and a countermeasure set — one-way aisles at shift change, a staged handoff zone, floor markings. Verified over eight weeks: rack damage down 70%, and the problem has not returned in a year. It was the plant's first A3 that ended with 'standardized' instead of 'binder'.
Step 5 · Kaizen · savingsThe VP's question now takes one click
Every idea moves idea → approved → implemented → verified, and the verification step belongs to finance, not the lean team. The ledger shows $320,000 a year in verified savings — scrap reduction in weld, packaging reuse, and the forklift-damage elimination are the biggest lines. The number is believed because each line links to its evidence.
Step 6 · OPL → Skill matrixStandards that train the next hire automatically
Closed A3s produce one-point lessons; OPLs route to exactly the roles they affect, and acknowledgement updates the skill matrix. New forklift operators now onboard against the traffic-pattern OPL on day one — the countermeasure teaches itself to every future hire.
Step 7 · LeaderboardRecognition the floor actually checks
Points for walks, closures, verified ideas; a podium, rising stars, and recent wins. The weekly all-hands starts with the wins feed — before-and-after photos of what the crews fixed. Turnover on the floor fell four points year over year; exit interviews stopped mentioning 'nobody listens'.
More case studies
All 9 →Illustrative deployment story: a composite of typical LeanOS rollouts; company and names are fictional.