
By: Dr Hafez Mohamed Farid Hamed
School of Business
International Academy of Engineering and Media Science, Egypt
hafez.mohammed.farid@iaems.edu.eg
Experience does not teach automatically. Two people can make the same error. One changes how she works. The other repeats it a year later. The difference is not always intelligence. Often it is whether the error was examined or only explained.
This article looks at why mistakes repeat and how a short, honest review can interrupt the pattern.
Why we skip the review
Reviewing a mistake is uncomfortable. It can feel like admitting failure. It is easier to say “that was unusual” or “it was the customer’s fault” and move on.
Some of these explanations may be partly true. But when we rely on them too quickly, we stop looking. An excuse protects how we feel for a while. It does not prevent the next error.
There is also a time problem. After a mistake, we are busy repairing it. When things calm down, the next task is waiting, and the review never happens.
Look at the system, not only the person
A small business owner sends a quote with the wrong delivery date. The customer complains, she apologises, corrects it and moves on. Two months later she makes the same error with another customer. (Hypothetical.) She treated the first problem as an event, not as information, so nothing about how she prepared quotes had changed.
In many organisations, a useful starting question after an error is not “Who made it?” but “What allowed it to happen?” Often several things combine: unclear instructions, rushed deadlines, a missing check, a confusing form.
This does not remove personal responsibility. You still own your decisions. But a review that looks only at personal failure tends to end with “be more careful”, which is rarely a plan. A review that looks at the process can lead to something concrete, such as a checklist or a second pair of eyes.
A simple review in four questions
You can do this in fifteen minutes with a notebook.
What happened? Describe the facts in order, without judgment. When did it start? What did you do? What was the result?
Why did it happen? Ask “why” several times, going from the surface to the cause. “The date was wrong.” Why? “I copied it from an old quote.” Why? “I had no template with the date field highlighted.” The last answer is something you can fix.
What did we do well? Even in a poor outcome, something may have worked, such as how quickly you responded to the customer. Keep it, and record it.
What will we change? Choose one or two actions, with a date and a person responsible. If you work alone, the person is you.
Watch for common traps
Several habits make reviews less useful.
Hindsight bias. Once you know the outcome, it feels as if it was obvious. Try to remember what information you actually had at the time.
Single cause thinking. Most problems have more than one contributing factor. If you find only one, ask whether you have stopped too early.
Over-correcting. A single mistake does not always justify a major change. If the error was rare and cheap, a small adjustment may be enough. If it was costly or has happened before, look more closely.
Blame, of yourself or others. Blame closes the conversation. Questions keep it open.
Look for patterns over time
One mistake is an event. Several similar mistakes are a pattern. Keep a short log, not a long diary. For each notable error: date, what happened, main cause, action taken. After a few months, read it through. You may notice that many problems come from the same source, such as rushing at the end of the week or skipping a check when you are confident.
A pattern points you to the most valuable fix. It also tells you where your attention is best spent, and prevents you from overreacting to a single day.
For teams and founders
If you work with others, make reviews safe. People will not report problems if they expect criticism. A leader can start by describing her own errors factually and focusing on what the team will change. Keep the review about the work and the process.
A founder who reviews each failed customer order, delayed delivery or refund request will start to see where the business loses money and trust. This is practical evidence that can guide decisions about suppliers, prices and processes.
Be careful not to review so much that you freeze. A review should lead to action within days, not a long document.
Keep it short
A review can fit on one page: what happened, why, what worked, what changes, and by when. If it takes much longer than fifteen minutes, it may be turning into a report that nobody acts on.
After any error that cost time, money or trust, try to complete one within a week. Every few months, read your recent reviews together and look for a shared cause.
A mistake you examine gives you information. One you only explain away may well return.
#CMA #Careers #hafezfarid #cmafasttrack
