There is a fantasy version of e-commerce where everything behaves. The listing is accurate, the stock is ready, the printer works, the courier arrives on time, the customer reads the delivery information, the gate code works, and somewhere in the distance a unicorn signs the proof of delivery with a glitter pen.
Then there is South Africa.
Here, the business may be brilliant, the product may be beautiful, and the customer may be ready to buy, but the journey between “order placed” and “parcel received” has its own personality. The courier window moves. Load-shedding arrives with the timing of a soap-opera villain. The supplier says “tomorrow” with the confidence of someone who has never been formally introduced to a calendar.
This is not a reason to lower the standard. It is a reason to design better.
That is the real meaning of “think global, act local” for South African sellers, vendors, makers, manufacturers, resellers, and importers. Global standards still matter. Customers still want clear communication, safe packaging, accurate products, fair returns, and a business that behaves like it knows where the parcel is. But local execution has to account for local friction. Customer Obsession cannot live in theory. It has to survive the road.
Through a Six Sigma lens, this is where we stop admiring the product page and start looking at the full order flow. The question is no longer only, “What does the customer want?” The sharper question is, “What could prevent the customer from receiving what they were promised?”
Map the promise before you blame the pothole
That is where SIPOC becomes useful.
SIPOC sounds like the kind of acronym that escaped from a business school lecture and hid in a consulting deck, but for a seller, it is really just a simple map of how the promise travels. It helps you see the path from the people and inputs you depend on, through the work you do, to the thing the customer finally receives.
The Supplier is anyone or anything you depend on before you can keep the promise: your manufacturer, importer, packaging supplier, courier, stock system, platform data, or your own production capacity. The Input is what must be correct before the order can move: stock count, product images, dimensions, labels, materials, pricing, packaging, delivery address, and variation selection. The Process is what happens from click to delivery: pick, pack, label, dispatch, courier handoff, tracking update, delivery attempt, return path, and support touchpoint. The Output is what the customer actually receives: the item, the condition it arrives in, the timing, the message trail, and the confidence that the business is in control. The Customer is not only “the buyer” on a report. It is the person waiting, gifting, using, installing, wearing, eating, reselling, or explaining the late parcel to someone else.
That is SIPOC in plain clothes.
It is not complicated. It is simply the act of asking, “Who helps us keep the promise, what do we need to get right, what steps does the order travel through, what lands at the end, and who feels the result?”
For customer-obsessed businesses, this matters because the buyer does not experience your operation as separate departments. They do not separate supplier delay from seller communication, packaging damage from courier handling, or unclear product images from their own disappointment. They experience the whole thing as one story: “I paid, I waited, I received, and I decided whether I trust you.”
That may feel unfair, especially when parts of the chain sit outside your direct control. But ownership does not mean pretending you control every road, depot, driver, scan, supplier, gate, or power schedule. Ownership means understanding the chain well enough to reduce avoidable disappointment.
The three potholes I would look for first are simple: delivery communication, packaging and product condition, and expectation clarity. Not because these are the only risks, but because they are the ones that most often turn uncertainty into distrust.
Delivery communication is the first pothole because silence makes customers suspicious. When the tracking goes quiet, when the delay is unexplained, or when the next step is unclear, the customer starts writing their own story. In that story, the parcel is lost, the seller is avoiding them, and the business may or may not exist behind the nice product photos. The CTQ here may not be “fastest delivery”. It may be “the customer knows what is happening before they feel forced to chase.”
Packaging and product condition are the second pothole because the customer does not care that the parcel looked perfect on your packing table. They care how it arrived. A fragile item must be packed for the actual journey, not the fantasy journey. If the product repeatedly arrives bent, leaking, scuffed, crushed, or looking like it lost an argument with a conveyor belt, the CTQ is not “pretty packaging”. It is “the item arrives in the condition promised.”
Expectation clarity is the third pothole because many disappointments are born before payment. If the image hides scale, the variation names confuse the buyer, the inclusions are vague, or the budget item is described with premium energy, the customer may buy one story and receive another. The CTQ here is “the customer understands what they are buying before they pay.”
These three potholes are not glamorous, but glamour is overrated when the review says “never again”.
This is where Article 2’s CTQ conversation becomes practical. A CTQ written nicely in a notebook means very little if the process cannot carry it. If the CTQ is “accurate delivery communication”, then the order flow must show when updates are sent, who sends them, what happens when a delay occurs, and when the customer gets a next step. If the CTQ is “item arrives undamaged”, then packaging must be tested against the real courier journey, not admired under soft lighting. If the CTQ is “customer understands the product”, then the listing, images, sizing, inclusions, and use-case guidance must all tell the same honest story.
The CTQ tells you what matters. The process tells you whether you can deliver it.
South African businesses already know friction. We do not need someone in a linen blazer to explain volatility to us while pointing at a triangle diagram. We know month-end pressure, supplier gaps, payment caution, courier delays, power cuts, and customers who send “Hi” as a complete message before vanishing like a magician with data issues.
Knowing the friction is not the same as designing for it
But knowing friction is not the same as designing for it.
The dangerous phrase is “we will make a plan.” It is part of our national genius, yes, but it can also become a hiding place. Making a plan is wonderful when the unexpected happens once. It is less wonderful when the same unexpected thing happens every week and the business keeps calling it a surprise. At that point, it is no longer surprise. It is a process with commitment issues.
Customer Obsession asks us to turn local knowledge into local design. If customers repeatedly chase delivery updates, do not only reply faster; fix the point where the silence begins. If fragile items keep arriving damaged, do not only apologise better; test the packaging against the trip it actually takes. If buyers misunderstand what is included, do not only blame them for not reading; make the listing harder to misread.
That is the shift from hustle to operating maturity.
Hustle says, “We fixed that order.” Operating maturity asks, “Why did that order need fixing?” Hustle says, “Customers always ask this.” Operating maturity asks, “Why are we making them ask?” Hustle says, “That is just how things work here.” Operating maturity asks, “Then how do we design for how things work here?”
That last question is where the work begins.
For South African entrepreneurs, this is not about becoming stiff, bland, or corporate. It is not about sanding away the humour, warmth, grit, craft, and personality that make local businesses compelling. It is about making the good stuff travel better. A product with local soul deserves a process with enough backbone to carry it.
If you want to apply this practically, choose one product and map the real journey using SIPOC. Start with the suppliers and inputs you depend on. Then map the steps from click to delivery. Then look at what the customer actually receives, not only physically, but emotionally: clarity, confidence, frustration, doubt, relief, or trust. Finally, ask who is affected when the promise wobbles.
Now mark the three places where trust is most likely to crack. Is it delivery communication, packaging condition, or expectation clarity? Choose one control for each. Add a better delay message. Strengthen a packaging test. Add a scale photo. Separate budget from premium products more clearly. Create a dispatch checklist. Confirm stock before promotions. Build one small control that stops the same problem from strolling back in with a new invoice.
Those marks are not failures. They are your potholes. And once you know where the potholes are, you can stop pretending the road is smooth.
That is how global standards become local capability. Not through imitation. Through translation. The customer does not need your business to be perfect. Most reasonable customers know that things go wrong, especially in a country where even the electricity likes to keep us humble. What they need is clarity, honesty, and the sense that someone designed the journey with reality in mind.
Customer Obsession is not pretending there are no potholes. It is packing properly because you know they are there.
And for any South African business hoping to grow in a marketplace environment, that may be the difference between a once-off sale and a customer who comes back, not because nothing ever went wrong, but because the business handled the journey like it had walked the road before.
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.