Every MSME owner has experienced this. A problem surfaces — rejection spikes, a delivery is missed, absenteeism disrupts a shift. You step in, address it, resolve it. Things stabilise. And then, two or three months later, the same problem is back. Sometimes worse.
The natural response is frustration with people. Why are they not learning? Why does this keep happening? But the question worth asking first is a different one: was the problem ever actually closed — or was it only suppressed?
“Solving a problem and closing a problem are two different things. Most businesses are very good at the first. Almost none have a system for the second.”
When a problem surfaces on the floor, the instinct is to fix the immediate symptom. Rejection is high — rework it and move on. A delivery was missed — expedite the next one and apologise to the customer. A machine broke down — repair it and resume production.
These are solutions. But they are not closures. A closure requires answering three questions that most businesses never formally ask:
Without answers to these three questions, every "solution" is just a delay. The same conditions that caused the problem the first time are still present. The problem will return.
In a fast-moving MSME environment, there is always pressure to move forward. When something breaks, the priority is to get production running again — not to analyse why it broke. Analysis feels slow. Action feels productive.
The result is a business that spends enormous energy fighting the same fires, repeatedly, across years. The firefighters become very skilled. But the factory never stops burning.
There is also a structural issue: in most MSME businesses, there is no assigned owner for problem closure. Everyone is responsible for production. No one is specifically responsible for ensuring that a problem, once addressed, does not return. Without ownership, follow-through disappears.
A closure system does not need to be complicated. In most businesses, it can be built around three practical elements:
When this system exists and is consistently used, recurring problems become visible immediately. If the same issue appears in the log twice, it signals that the first closure action did not work — and prompts a deeper analysis before it becomes a third occurrence.
The visible cost is rework, delays, and customer complaints. But the hidden cost is larger: the energy your management team expends re-solving problems they have already solved. Every hour spent on a recurring problem is an hour not spent on improvement, on growth, on building capability.
Recurring problems are not a sign of a bad team. They are a sign of a system that has not been built yet. The team is doing what the system allows them to do — which is respond, not prevent.
Build the system. The recurring problems will stop recurring.