Book 15 with TomBy Dr Tom Hitchcock, founder of Mr Purple (LinkedIn)
Learning from mistakes in business sounds sensible until the same mistake arrives for its third lap, wearing a fresh hat and carrying another invoice. Most owners do not lack intelligence or effort. The real problem is that a mistake gets discussed, perhaps apologised for, then returned to the wild without changing the system that helped create it.
Mistakeology offers a more useful response. It treats a mistake as information about how work actually happens. The aim is not to remove accountability. It is to replace blame, vague promises and heroic memory with a better way of working.
Learning from mistakes in business without blame
Blame feels decisive, but it usually makes a business less curious. People protect themselves, details go missing and the official story becomes tidier than the truth. A blameless review asks a sharper question: what conditions made this outcome possible?
That does not mean nobody owns their choices. Accountability still matters. The distinction is simple. Blame looks for a person to carry the discomfort. Accountability identifies who will improve the work, by when, and how everyone will know it worked.
Start a review with four facts:
- What did we expect to happen?
- What actually happened?
- Where did the two paths separate?
- What made the wrong path look reasonable at the time?
The last question is especially useful. Good people rarely wake up eager to create chaos before lunch. They act using the information, pressure, tools and habits around them. Understand those conditions and you can improve them.
Separate the event from the pattern
One error can be a slip. A repeated error is usually a system speaking rather loudly.
Imagine that a client handover is missed. The tempting response is, “Be more careful next time.” That is not a system. It is a wish wearing office clothes. Look for the pattern beneath the event. Was ownership unclear? Did the task live in an inbox rather than the team workflow? Was there no visible due date? Did two people each assume the other person had it?
A useful review maps five elements:
- Trigger: What started the work?
- Owner: Who was responsible for moving it forward?
- Method: Where was the process recorded?
- Check: What should have revealed that it was drifting?
- Recovery: How quickly could the team correct it?
If any answer is fuzzy, you have found a place to strengthen. The mistake is no longer merely an unpleasant memory. It is a signpost.
Run a twenty minute Mistakeology review
A review should be short enough to happen and useful enough to change something. Endless analysis can become another hiding place. Try this simple format with the people closest to the work.
Describe the facts
Keep this free from motives and character judgements. “The proposal went out with the old scope” is a fact. “Nobody cares about quality” is a story, and not a particularly helpful one.
Find the earliest useful intervention
Do not focus only on the final failure. Ask where a small check could have changed the outcome. Earlier interventions are usually cheaper, calmer and easier to repeat.
Choose one system change
A good action changes the environment. Add a checklist, clarify a decision right, simplify a form, create a visible owner or remove a confusing duplicate step. Avoid a grand collection of twelve improvements that nobody remembers.
Name the proof
Decide how you will know the change works. The proof might be that the next five handovers include a named owner and completion check. It should be observable, not a warm feeling.
Build systems people will actually use
The cleverest process is worthless if it lives in a document nobody opens. Better systems fit the rhythm of real work.
Use these tests before introducing a change:
- Visible: Can the person doing the work see the next step?
- Owned: Is one person clearly responsible?
- Light: Is the process simpler than relying on memory?
- Timely: Does the check happen before the damage is done?
- Reviewable: Can the team tell whether the change helped?
For small businesses, this matters because complexity has a cost. A seven page procedure may look impressive while quietly being ignored. A short checklist attached to the task can be far more powerful.
This is part of the thinking behind Mistakeology: mistakes are not trophies and they are not shameful secrets. They are raw material for better decisions, provided we examine them honestly.
Make improvement a leadership habit
Leaders set the emotional weather around mistakes. If every problem triggers anger, people learn to delay bad news. If every problem receives a shrug, standards drift. The useful middle is calm curiosity followed by clear action.
Three habits help:
- Thank people for raising a problem early.
- Discuss the process before judging the person.
- Return to the agreed change and check the result.
The third habit is where many reviews vanish. A meeting ends, everyone feels wiser, then the business resumes its usual shape. Put the check date into the normal meeting rhythm. If the change worked, keep it. If it added friction without improving the result, adjust it. Mistakeology is not about defending the first solution. It is about learning faster than the problem repeats.
Turn the next mistake into an asset
You do not need a dramatic failure to begin. Pick one recurring irritation that wastes time, causes rework or leaves ownership cloudy. Review the facts, identify the earliest useful intervention and change one part of the system. Then check whether it worked.
If you would like a practical outside view, book a 15 minute call with Tom. Bring one stubborn mistake. We will look for the system hiding underneath it.
Common questions
What is Mistakeology?
Mistakeology is a practical discipline for examining mistakes without shame, finding the conditions behind them and turning the learning into better decisions and systems.
Does a blameless review remove accountability?
No. It replaces personal blame with clear ownership of the improvement, a due date and observable proof that the change worked.
How soon should a team review a mistake?
Review it while the facts are still clear and the people closest to the work can contribute. Keep the discussion calm, factual and focused on one useful system change.
What if the same mistake keeps happening?
Treat repetition as evidence that the earlier response did not change the working environment. Revisit ownership, visibility, timing and the checks that should reveal drift.