The Most Expensive Sentence in Business

“I know what the problem is.”

It sounds decisive. It feels efficient. And in business, that kind of certainty can be dangerously expensive. Confidence and clarity do get things moving. It helps the owner make the call, the team respond under pressure, and the business keep going when the printer, the courier and the Wi-Fi all decide to audition for villain of the week.

But confidence becomes expensive when it arrives before understanding. That is when the operation starts fixing shadows.

The WhatsApp messages are spicy. The customer is annoyed. The team is defensive. Someone has already said, “We just need a better system,” which is often business language for “I am tired and would like software to absorb my feelings.”

The issue seems obvious. Deliveries are late. Customers are confused. Staff are careless. So the business jumps. It changes the courier, rewrites the message template, or buys a tool. Then someone holds a meeting where everyone agrees to “communicate better”, which is often where weak process goes to wear perfume.

For a few days, things feel better. Then the same wobble returns wearing a different hat.

This is where Amazon’s Leadership Principle of Dive Deep becomes useful.

Dive Deep is not about disappearing into data caves until the business forgets what sunlight looks like. And thankfully it is also not about making every issue a research project with a 47-tab spreadsheet and a committee called “Task Team: Phase One”. Small businesses do not have time for that kind of ceremonial paperwork.

But Dive Deep is also not optional. Because a fast solution built on weak understanding can create a cleaner-looking version of the same mess.

I keep saying it because it is true. South African businesses are very good at making a plan. We have had practice. But sometimes the plan is a plaster on a plumbing leak. It helps for five minutes, then the wall starts bubbling again.

Dive Deep asks for a different kind of discipline. Before the new tool, before the voice note, before the WhatsApp group gets renamed “OPERATIONS FINAL”, before the owner decides the team needs training, pause and ask: what are we actually looking at?

Symptoms are loud. Problems are quieter.

That sounds simple. It is not. Most businesses are surrounded by symptoms. Complaints. Delays. Returns. Rework. Escalations. Questions. Missed handovers. Frustrated staff. Confused buyers. Stock that swears it was there yesterday.

Symptoms are loud. Problems are quieter. A customer saying “your service is bad” is a symptom. The failure point might be unclear delivery expectations, weak stock visibility, or a handoff gap between sales and fulfilment.

A team saying “customers do not read” is a symptom. The operating gap might be that the listing is unclear, the important detail is buried, or the business is using different versions of the truth across the website, WhatsApp and marketplace page.

An owner saying “staff keep making mistakes” is a symptom. The real friction might be poor training, lookalike stock, or a process that depends on memory and bravery.

Dive Deep is the pause that stops the team from punishing the symptom while the real failure point quietly makes tea in the corner.

It also asks leaders to be sceptical when the story and the signals do not match. If the numbers say returns are stable, but the frontline keeps hearing the same complaint, look closer. If one angry customer makes the issue feel enormous, but the data shows it happened twice in six months, look closer. If the dashboard looks tidy, but the team is doing hidden rework every afternoon, look closer. Neither the anecdote nor the metric gets to be king without being tested.

A fast solution built on weak understanding can create a cleaner-looking version of the same mess.

Use DMAIC as a backbone, not a costume

This is where DMAIC gives us a useful backbone.

Define. Measure. Analyse. Improve. Control.

The “I” is Improve, the part everyone wants to sprint towards. Improve feels productive. Improve buys the tool, changes the form, updates the rule, moves the shelf, rewrites the message and gives everyone that lovely feeling of doing something. But if Define is weak, Measure is messy and Analyse is skipped, Improve becomes a lucky guess in business shoes.

Dive Deep keeps DMAIC honest.

Define asks what issue we are solving, where it starts and ends, who is affected, and why it matters.

Measure asks what evidence we have beyond the loudest complaint or the owner’s Monday mood.

Analyse asks what may be driving the pattern, not what we wish were driving it because that would be easier to repair.

Improve asks what change addresses the cause, not just the noise.

Control asks how we keep the improvement from evaporating the minute everyone gets busy again.

That is the grown-up rhythm. Not because every seller, maker, service provider or entrepreneur needs to become a Six Sigma professor with a laser pointer and a suspicious love of acronyms. But because every business needs a way to slow down long enough to stop making expensive guesses.

Take a Problem Framing Pause

A simple tool for this is a Problem Framing Pause. Think of it as the business version of the old rugby scrum rhythm: touch, pause, engage. Touch the issue first. Get close enough to understand what is actually happening. Pause before the shove. Do not let urgency, irritation or confidence push the team straight into a solution. Then engage. Act with enough understanding that the improvement has a fighting chance.

Nothing fancy. No corporate theatre. Just a short thinking discipline before action.

First, write the problem statement.

Not a complaint. Not a blame sentence. Not “the courier is useless” or “staff need to focus”. A proper problem statement says what is going wrong, where it is happening, who is affected, and how we know.

For example: “In the last three weeks, customers ordering Product A through WhatsApp have asked repeated sizing questions after payment, causing delays, order changes and refund requests.”

That is useful. It has a place, a product, a channel, a time period, an effect and evidence. Compare that to: “Customers are confused.” That may be true, but it is fog wearing shoes.

Second, name your first hypothesis.

A hypothesis is not the truth. It is your first best guess. Maybe the size guide is unclear. Maybe the sales message is incomplete. Maybe the photo creates the wrong expectation. The power of a hypothesis is that it can be tested. The danger is when the hypothesis sneaks into the boardroom wearing a crown and everyone starts treating it like a conclusion. “We think the size guide may be unclear” is useful. “The customer does not read” is lazy and usually expensive.

Third, set the scope.

This is where Dive Deep needs a leash. Because yes, you can investigate everything. The product. The supplier. The courier. The customer message. The website. The team. The platform. The weather. The economy. Mercury in retrograde. Your cousin’s advice from 2018. But not every question belongs in this investigation.

Scope protects the business from turning one issue into an archaeological dig. For this pass, are we looking at one product, one channel, one courier, one store, one week, one customer segment, one handoff or one return reason?

What are we not looking at right now? Out of scope is not denial. It is discipline. It says, “We may need to look there later, but not in this pass.”

Fourth, decide what evidence would help.

Not perfect evidence. Useful evidence. How often is the pattern showing up? When did it start? Which products, orders, channels or handoffs are involved? What changed recently? What does the team keep correcting? Where does the delay actually begin?

This could be a quick check sheet. A sample of customer messages. A walk through the packing process. The goal is not to drown the business in data. The goal is to stop arguing with anecdotes.

Fifth, decide when you know enough to act.

This is the part that saves Dive Deep from becoming Deep Dive and Then Drown. Some people jump to solutions too quickly. Others keep analysing because action feels risky. Both can hurt the business. A useful question is: What would be enough evidence to try a small improvement? Not a forever decision. Not a giant rebuild. A small, sensible test.

If most sizing confusion comes from one product page, improve that page. If returns spike when one supplier batch changes, inspect the batch before selling. If late dispatch starts before the courier arrives, fix the packing cut-off.

Dive Deep does not mean waiting until certainty arrives wearing a crown. It means understanding enough to make the next move less foolish. That is the balance South African entrepreneurs need. Move too fast, and you may repair the wrong thing. Move too slowly, and the defect keeps charging rent. The sweet spot is disciplined curiosity.

Why this matters for teams and trust

Pause. Frame the issue. Test the first hypothesis. Stay inside scope. Gather enough evidence. Then improve. This is respect for the operation, the team and the customer. Because every rushed solution creates its own shadow. A new rule can slow honest customers down. A new checklist can annoy the team if it does not address the real risk. A new tool can automate confusion.

The fix can become the next defect. Dive Deep helps prevent that.

It also protects people. When businesses do not understand failure points properly, people become the easiest target. The picker gets blamed. The customer service agent gets blamed. The courier gets blamed. The junior employee gets blamed. Sometimes blame is deserved, but often it is just the fastest available story.

A better operation asks: “What did the process make easy, and what did it make hard?” Dive Deep does not excuse poor work. It makes poor work easier to understand and prevent.

That is why this Leadership Principle underpins so many others. You cannot insist on high standards if you never look closely at where the standard breaks. You cannot earn trust if you only respond to the complaint and never study the pattern. You cannot invent and simplify if you simplify the wrong part. You cannot show ownership if you only own the noise, not the root of the failure.

Dive Deep is the quiet discipline underneath the louder virtues. It is the business saying: before we improve, let us understand. Not forever. Not as performance. Just enough to stop making the same mistake in a more expensive outfit.

Practical take-away

Before you solve the next recurring issue, take a Problem Framing Pause. Write one clear problem statement: what is going wrong, where, for whom, and how do you know? Name your first hypothesis, but do not marry it. Define the scope: what are you looking at now, and what are you leaving for later? Gather enough evidence to challenge or confirm your thinking. Then decide what small improvement is worth testing.

The goal is not to admire the issue until it gets a pension fund. The goal is to understand it well enough that your response has a fighting chance.

Here is your pressure test: where in your business are you already solving, changing, training or buying tools before you have properly defined the issue? And what would change if you paused long enough to understand the pattern before improving it?

This is a personal thought piece, written in my private capacity from my own customer experience and process improvement perspective. It draws on publicly available information and reflects my own views, not the views of my employer.