I often hear from manufacturing business owners:
“We solve one quality issue, but after some time, the same type of problem shows up in another product line. Mai kya karu?”
Welcome to this talk series Kya Karu, specially for business owners. I’m Nalin Mehta, and today we’ll talk about what’s really happening when quality problems keep returning across different products.
When defects keep repeating in different products, it is easy to blame operators, machines, or the quality team. But that is not usually the real issue.
Because if the same type of problem keeps coming back, even after discussions, meetings, and corrective actions, then the problem is usually bigger than one product.
So what is actually happening?
Let me break down what is really causing this, and more importantly, what you can do about it.
First, your business is fixing defects, but not root causes.
In many factories, when a quality issue happens, teams move quickly to solve the immediate problem.
Rejected parts are reworked.
Production is corrected.
Customer complaints are handled.
And everyone moves on.
But very little time is spent asking:
“Why did this happen in the first place?”
The same issue then quietly appears in another product because the underlying reason was never fixed.
Maybe operator training is weak.
Maybe process parameters are inconsistent.
Maybe vendor material variation was ignored.
The solution here is simple. Stop treating every quality issue as an isolated event.
Whenever a major issue happens, ask:
“Can this same reason create problems elsewhere?”
Make root cause analysis cross-functional, not product-specific. If one welding issue happened here, check other products using similar welding processes. If one machining tolerance failed, review similar operations across the plant.
Second, quality knowledge is staying with individuals, not systems.
In many manufacturing businesses, experienced people know how to avoid problems.
One supervisor knows a machine behaves differently in summer.
One operator knows which material batch creates trouble.
One quality person catches issues before dispatch.
But this knowledge stays in people’s heads.
So when shifts change, people move, or workload increases, mistakes return.
Nobody says this openly, but this happens far more often than most businesses realize.
Address it directly.
Turn practical learning into simple systems.
Create standard checks.
Update SOPs after every major issue.
Document what changed and why.
Good quality does not come from memory. It comes from repeatable processes.
Third, different departments are solving problems separately.
Production blames quality.
Quality blames procurement.
Procurement blames vendors.
And everyone solves only their piece of the problem.
But quality failures rarely happen because of one department alone.
A defect may start with raw material, worsen during production, and get missed during inspection.
When teams work in silos, the same issue finds a way to return.
The solution is to review recurring quality issues together.
Bring production, quality, maintenance, and procurement into the same discussion.
Instead of asking, “Who made the mistake?”
Ask, “Where did the system fail?”
That shift changes everything.
When quality problems keep returning across different products, the issue is usually weak root cause analysis, knowledge staying with individuals instead of systems, or departments solving problems separately. Fix causes, not symptoms. Build systems instead of depending on experience alone. And solve quality problems together, not department by department. When you do this, recurring defects reduce and consistency improves across the business.
Mai kya karu?
