How to Track Kaizen Savings: The Method That Actually Holds Up to Finance

"How much did our kaizens save last quarter?"

If your answer is "let me check with the operations team", you have a tracking problem — not a kaizen problem. We've seen plants generating 200+ ideas a year and unable to show Finance a single verified rupee.

Here's the method that actually works in Indian plants, and how to digitise it without becoming a Six Sigma cult.

The 4-stage funnel every kaizen should walk through

Stage 1 — Idea (anyone can submit)

Operator notices: "If we move the part bin closer to the assembly point, we save 15 seconds per cycle."

What you capture: title, description, photo (optional but ideal), estimated savings (rough), category (safety / quality / cost / productivity / ergonomics / environment).

Friction kills this stage. If submitting takes more than 60 seconds, you'll get one idea per quarter. Make it phone-first, voice-input-friendly.

Stage 2 — Approval (supervisor + plant lead)

Two-eyes review: does this make sense? Is the estimated saving plausible? Who's implementing it? When?

Rejection isn't bad. About 30% of ideas should be rejected — duplicates of existing work, technically infeasible, against current SOPs. Reject with reason; keep the operator motivated by acknowledging.

Stage 3 — Implementation (assigned owner, deadline, after-photo)

This is where most programs leak. Idea approved → silence → forgotten.

The fix: every approved kaizen gets an owner + a date. If the date slips, it auto-surfaces in the weekly review. If the after-photo isn't uploaded within 7 days of the deadline, an admin gets a nudge.

Stage 4 — Verification (savings confirmed, accepted by Finance)

This is the stage that turns "we did kaizen" into "we saved ₹X". And it's the stage most programs skip.

What verification looks like:

• Implementer captures the after-state (photo, video, or measurement)
• Plant manager OR finance designate reviews + confirms the actual saving
• If the original estimate was wrong, the verified number is what counts
• The verified savings get logged with a date stamp + the verifier's signature

For monthly savings (e.g. "saves ₹12k per month"), set up a recurring entry — Jan ₹12k, Feb ₹11k, Mar ₹13k. Don't extrapolate one month × 12. Months vary (shutdowns, overtime, shorter Februaries). Real numbers build CFO trust; estimates destroy it.

The Indian-plant pitfalls we see again and again

1. The "₹50 lakh saved!" theatre

Plant claims ₹50L in annualised savings. CFO asks for verification. Half the entries are double-counted (same improvement claimed by 2 people). A third are estimated, not verified. Real number: ₹8L.

Discipline: only count verified savings in CFO conversations. Estimated savings are a forecast, not a number.

2. No before-state, no proof

"This kaizen saves 20 seconds per cycle." Sounds great. What was the cycle time before? "Uh, I think 80 seconds?"

Discipline: every kaizen needs a baseline. If you don't measure before, you can't claim after.

3. The "supervisor's pet idea" problem

One supervisor submits 80% of ideas in their line. Half are bad. Approver rubber-stamps because the supervisor is senior.

Discipline: approval criteria, written down, applied uniformly. Better: blind approval — name hidden during review.

What to digitise (and what NOT to)

Digitise:

• The submission funnel (phone form, photo upload, voice input)
• The approval queue (supervisor / admin notifications)
• The implementation tracker (owner, due date, after-photo)
• The verification stamp (who, when, ₹ confirmed)
• The dashboard rollup (per zone, per category, per month)

Don't digitise (yet):

• Voting / "best kaizen" awards — runs on social pressure, not software
• Detailed before-after charts unless your team naturally lives in data
• Multi-level approval workflows — keeps it simple, 2 levels max

What we built

The kaizen module in LeanOS runs this 4-stage funnel for you. Approval gates, ownership, verification, monthly savings ledger (not naive ×12), CFO-grade per-period rollups.

One pilot — Factory ABC, auto-component plant in Pune, 200 employees — verified ₹15.7L in 90 days. Real verified rupees, not annualised theatre.

Calculate what your plant would track — uses our pilot benchmarks.