Every South African knows the phrase “school fees.” Not the tidy debit order kind with a statement and a due date, but the painful kind. The lesson you paid for because you did not know better yet. The mistake that arrived with a little invoice attached. The moment life looked at you and said, “Sharp. Now you know.”
In business, school fees show up as refunds, returns, replacements, damaged parcels, low reviews, awkward apologies, admin time, and the kind of customer message that makes your stomach quietly leave the room before you finish reading it.
Some school fees are unavoidable. Every seller, vendor, maker, manufacturer, reseller, and importer will pay a few. That is part of learning. You launch the product. The customer uses it differently than expected. A supplier changes a detail without warning. A product page that looked clear at midnight suddenly becomes a treasure map in daylight.
Ok, ja, well, no fine. That is business.
But paying school fees twice for the same mistake? That is where Customer Obsession starts clearing its throat.
Because the first time a buyer complains, the business may have discovered a problem. The second time, it may have discovered a pattern. The third time, my friend, the problem has moved in, unpacked, and started using your Wi-Fi.
That is where Amazon’s Leadership Principle of Customer Obsession becomes useful through a Six Sigma lens. Customer Obsession is not only about responding quickly, apologising warmly, or recovering the individual order. It is about learning from customer pain fast enough that the same pain does not keep returning with a new order number and fresh attitude.
A review is not only feedback from yesterday’s customer. In a marketplace, it becomes evidence for tomorrow’s buyer. Returns, refund reasons, low ratings, repeated questions, and support messages are not admin clutter. They are the places where the business leaves fingerprints. They show where expectation, process, product, fulfilment, or communication may be leaving a mark the next customer can see.
That does not mean every complaint deserves a full investigation with a whiteboard, a committee, and someone bringing muffins to soften the mood. Before you investigate, sort the signal. One isolated incident may need recovery. A repeated pattern needs root-cause work. A strategic warning needs a bigger conversation about the promise itself.
That small distinction matters. Not every bad review deserves a full investigation, and not every refund means the business model is on fire. One loud review may need recovery. A repeated pattern needs investigation. A strategic warning needs leadership attention.
Ask why before you buy another bandage
That is the sorting step before the fixing step. Through Six Sigma, the spotlight here belongs to the 5 Whys.
The 5 Whys is beautifully simple. When something goes wrong, you ask “why?” until you move past the visible symptom and reach a more useful cause. It does not mean you must literally ask why exactly five times while staring at a whiteboard like a detective in a low-budget procedural. Sometimes you need three. Sometimes you need seven. The point is not the number. The point is that you do not stop at the first answer.
The first answer is usually the one wearing a disguise.
This matters because sellers often jump from complaint to solution too quickly. A customer says “late delivery”, so the business promises faster delivery. A customer says “bad quality”, so the business changes suppliers. A customer says “wrong item”, so the business blames the picker. Sometimes those actions are correct. Often they are expensive guesses wearing business shoes.
5 Whys slows the panic down.
Three familiar places the same mistake hides
Let us keep it practical with three familiar marketplace problems.
A customer says, “My order arrived damaged.” The easy answer is, “The courier was rough.” Maybe. But if you stop there, the courier becomes the villain, the refund becomes the band-aid, and the next parcel goes out wearing the same weak protection and a brave little prayer.
Ask why.
Why did the order arrive damaged? Because the box was crushed in transit.
Why did a crushed box damage the item? Because the product had no internal protection.
Why was there no internal protection? Because the packaging step focused on presentation, not handling.
Why did we design packaging for presentation only? Because we tested how it looked, not how it travelled.
Now the cause is clearer. The issue is not only courier behaviour. It is packaging design that did not account for the route the product actually takes. The improvement is no longer “shout at the courier louder.” The improvement is “test the packaging before the customer does it for us.”
A second customer says, “This is not what I ordered.” The easy answer is, “They selected the wrong option.” Maybe they did. Buyers skim. People shop while distracted. Someone is comparing prices, checking payday maths, and answering three family messages at the same time. But if the wrong-option issue keeps returning, the seller needs to look closer.
Why did the customer receive the wrong item? Because they selected the wrong variation.
Why did they select the wrong variation? Because the variation names looked too similar.
Why were the names too similar? Because the listing used internal product codes instead of customer language.
Why did we use internal product codes? Because they made sense to us.
There it is. The buyer did not simply choose badly. The business made choosing correctly harder than it needed to be. The control may be as simple as rewriting variation names, adding a comparison photo, or making the difference impossible to miss before checkout.
A third customer says, “Delivery took too long.” The easy answer is, “Logistics are slow.” Sometimes, yes. South African delivery has enough plot twists to qualify for its own drama series. But if people repeatedly chase updates, the real issue may not be speed. It may be silence.
Why did the customer complain about slow delivery? Because they did not know where the parcel was.
Why did they not know? Because tracking had not updated after handoff.
Why did they chase the seller? Because there was no proactive update when the tracking went quiet.
Why was there no proactive update? Because there was no trigger for courier silence.
Suddenly the improvement is not “make every delivery faster”, which may be expensive or impossible. The improvement is “tell the customer what is happening before doubt starts doing laps around the WhatsApp group.”
That is the power of 5 Whys. It turns emotional smoke into a root-cause trail.
For South African businesses, this is especially useful because many sellers operate without a full quality department, expensive analytics suite, or formal improvement team. You may have a laptop, two shelves, a courier account, a folding table, and a system that still lives partly in your head. That does not disqualify you from disciplined improvement. It simply means the tool must be light enough to use in the real world.
Log the defect before memory eats the evidence
That is where a small defect log helps.
A defect log is simply a place where you record recurring pain before it disappears into memory. It does not need to be fancy. Capture the customer-facing issue, the product or order type, the broad category, the cost in money, time, or trust, and the most likely root cause once you have asked why properly. Do not log only the emotion. Log the missed expectation.
That last sentence is important. “Angry customer” is not useful enough. “Customer expected delivery update before chasing” is useful. “Bad review” is not useful enough. “Customer expected product to be larger based on photo” is useful. “Return requested” is not useful enough. “Customer selected wrong variation because options were unclear” is useful.
A polished public reply may protect the moment. A changed process protects the future.
Rework is expensive in ways a bank statement does not always show. A refund hurts once. A recurring defect creates extra messages, extra checking, extra packing, extra apologies, and extra stress. Before long, the owner is not running the business; the owner is running after the same failure wearing different order numbers.
Customer Obsession through a Six Sigma lens says: stop chasing the shoe. Find the footprint.
After Pareto, this is the next logical move. Pareto helped you identify the biggest bucket of customer pain. Maybe most issues came from listing truth. Maybe stock and fulfilment accuracy were causing the drama. Maybe packaging and communication kept winning the unhappy trophy. Once you know the biggest bucket, 5 Whys helps you ask why that bucket keeps filling.
Pareto tells you where to look. 5 Whys tells you what to ask. A small control turns the lesson into maturity.
The practical exercise is simple. Choose one recurring problem from the last month. Not twenty. Not the entire business. One. Pick the issue that costs the most money, trust, or time. Write down the customer-facing complaint in plain language. Then ask why until the cause becomes something your operation can act on.
Be careful here. A useful root cause is not “customers are difficult”, “couriers are useless”, or “people do not read”. Those may feel satisfying for three seconds, but they do not help you improve. A useful cause points to something you can change, control, clarify, test, measure, or escalate.
The better the cause, the better the fix. This is where customer obsession becomes more than service recovery. It becomes learning discipline. You are not only asking, “How do we make this customer feel better today?” You are asking, “How do we prevent tomorrow’s customer from feeling the same pain?”
Hustle fixes the order. Maturity fixes the reason the order needed fixing.
That does not mean becoming stiff, corporate, or allergic to personality. It means protecting the good stuff. The maker pride. The vendor ambition. The manufacturer discipline. The local confidence that says, “We can do this properly, not just passionately.”
Once you find the cause, build one small control. Not a revolution. A control. Test the packaging. Rename the confusing variation. Create a courier-silence update trigger. One repeated issue. One root cause. One practical control that stops the problem from strolling back in with a new invoice.
Without the control, the business has not really learned. It has only felt pain, paid the refund, said sorry, and carried on with the same weak process in a slightly more tired outfit.
That is an expensive rerun.
Customer Obsession asks for something better. It asks the business to respect customer pain enough to learn from it. It asks sellers not to treat recurring complaints as personal attacks or annoying interruptions, but as lessons that have already been paid for. It asks vendors and manufacturers to spot defects early, before scale gives them a bigger stage and better lighting.
The goal is not perfection. No business gets there. Parcels will still go missing. Customers will still misunderstand. Suppliers will still treat delivery dates like friendly suggestions. Life will still arrive with plot twists and a clipboard.
But the repeat failure? The known one? The already-paid-for one? That one deserves attention. Because the first time, it may be school fees. The second time, it is a reminder. The third time, it is your process asking why you are not listening.
So do not pay school fees twice for the same mistake. Log it. Ask why. Find the cause. Build the control.
That is how customer pain becomes business intelligence. That is how local sellers raise the standard without losing soul.
This is a personal thought piece, written from my own customer experience and process improvement perspective. It draws on publicly available information and reflects my own views.