You know what I keep hearing from manufacturing leaders?
“Humne fix kar diya tha yeh problem… meeting bhi ki, log bhi samjhe… but wahi rework phir se aa gaya. Mai kya karu?”
And that exhaustion is real. Because you did everything right. You identified the problem. You sat down with the team. You put a fix in place. And yet, a few weeks later, you’re looking at the same issue all over again.
Welcome to my talk series Kya Karu for business owners like you. I’m Nalin Mehta. Let’s get into it.
So what’s actually going on?
Most fixes feel complete in the meeting room. Someone explains what went wrong. Everyone nods. A corrective action is written down. And then everyone goes back to work.
But the rework comes back. Because the fix never actually changed anything at the ground level.
Let’s understand why.
The most common fix in manufacturing is a conversation. “Yeh galat hua, aage dhyan rakhna.” And that conversation is genuine. But a conversation without a system change is not a fix. It’s a reminder. And reminders fade.
A month later, the same pressure is back. The same shortcuts look tempting. And the rework returns.
Now let’s look at a second pattern.
Sometimes a fix is implemented, but only for the person who made the error. The rest of the team never hears about it. So the same mistake gets made by someone else, in a different shift, on a different line.
The fix existed. It just never traveled.
And then there is a third pattern.
The root cause was identified incorrectly. The team fixed the symptom, not the source. The defect looked like a machining issue, so the machine was recalibrated. But the actual cause was an incoming material variation that nobody checked. The machine runs perfectly. The rework continues.
So why do fixes fail to stick?
Because most corrective actions stop at the what and never get to the why. Because changes are communicated verbally instead of being built into the process. Because accountability ends after the meeting, with no follow-up to check if the fix is actually working.
So what do you change?
First, separate the immediate fix from the permanent fix.
When rework happens, deal with the immediate problem first. Contain it. Then separately, investigate the root cause properly. These are two different conversations and they need two different actions.
Most teams do the first and skip the second. That is why the problem returns.
Second, change the process, not just the person.
If your fix is “tell the operator to be more careful,” it will not last. Ask instead: what in the process allowed this error to happen? Can we add a check? Can we mistake-proof this step? Can we change the sequence?
A process change outlasts any individual instruction.
Third, document the fix and make it visible.
Once a root cause is confirmed and a corrective action is decided, it needs to live somewhere permanent. An updated work instruction. A revised checklist. A new inspection point.
Not in the minutes of a meeting that nobody reads again.
Fourth, close the loop with a follow-up check.
Two weeks after a fix is implemented, go back and verify. Is the rework still happening? Has the frequency reduced? Is the fix being followed consistently?
Without this step, you will never know if the fix actually worked or just delayed the problem.
Fifth, share learnings across all shifts and lines.
Every rework investigation is a learning opportunity. Once a fix is confirmed, share it with every team that could face the same issue. A short briefing. An updated instruction. Anything that ensures the knowledge travels.
What one shift learns should not stay with one shift.
Rework that keeps repeating is not a discipline problem. It is a systems problem.
The goal is not to find someone to blame. The goal is to build a process that makes the same mistake difficult to repeat.
Fix the system. The results will follow.
I hope this was useful. Stay connected, there’s a lot more coming in this series.
