Volume 23, Chapter 3
Lessons Learned and the Mistake Log
Definition
An early mistake at MANIAC MINDZ, a mismeasured order that reached a customer, went unreported for weeks out of fear of blame. The same underlying process gap caused a second, nearly identical mistake before anyone addressed it.
A mistake log (or lessons-learned log) is a running, blame-free record of what went wrong and what changed as a result, the same discipline behind Volume 10's risk response cycle and Volume 14's defect log, generalized to every part of the business.
Why did the exact same mistake happen twice? Because the first time, fear of blame kept it hidden, and a hidden mistake can't be traced to its cause or fixed, it can only wait to happen again. A mistake log only works if reporting it honestly feels safer than staying quiet.
A mistake that's hidden out of fear of blame teaches the business nothing and will likely happen again. A mistake that's logged, honestly, without punishing whoever reports it, becomes exactly the kind of "lessons learned" input Volume 10's risk cycle feeds back into prevention.
What a Good Entry Includes
| Element | Blame-Focused (Wrong) | Lessons-Learned (Right) |
|---|---|---|
| Focus | Who is at fault | What happened and why |
| Root cause | Rarely investigated past "human error" | Traced to a system, training, or process gap |
| Outcome | Punishment, or nothing | A specific, documented change |
A mistake log exists to change a system, not to punish a person. The moment it becomes about blame, people stop reporting honestly, and the business loses its earliest warning of a repeatable problem.
Why Feeling Safe to Report Matters Here
A mistake log only works if people trust that reporting a mistake honestly won't be used against them personally. This isn't a soft nicety, it's the entire mechanism: a hidden mistake teaches nothing and often repeats; a logged one, traced to its root cause, usually gets fixed for good.
Example Story: The Mistake That Was Hidden, and the One That Wasn't
Here's the full version of the hidden-mismeasurement story from the start of this chapter.
An early mistake at MANIAC MINDZ, a mismeasured order that reached a customer, went unreported for weeks out of fear of blame. The same underlying process gap caused a second, nearly identical mistake before anyone addressed it.
Two mistakes. One real cause. Only the second one got fixed. After introducing an explicitly blame-free mistake log, a very similar error was reported the same day it happened; tracing it to its root cause (an ambiguous measurement instruction, not carelessness) led to a clarified process that prevented a third occurrence entirely.
Across Industries
Every trade eventually finds a mistake that looks like carelessness but is actually a process gap.
| Business | A Logged Lesson |
|---|---|
| Golden Crust Bakery | A batch spoiled due to an unclear storage instruction, not staff carelessness |
| Rapid Auto Works | A repeat return of the same fault, traced to an incomplete fault-finding checklist |
| Precision Print & Press | A colour mismatch traced to a monitor with the wrong colour settings, not operator error |
Common Mistakes
Ends honest reporting immediately, see the example story's first, hidden mistake.
"A mistake happened" without "why" produces no actual prevention.
A lesson identified but never actually put into practice will simply repeat.
Quiz Yourself
Practice Exercise
Start a Mistake Log this week. Log the next genuine mistake, yours or anyone's, focused entirely on root cause and system fix, with no blame attached.
Quick Summary
Quick Summary
- A mistake log is blame-free by design, its purpose is fixing systems, not punishing people.
- Every entry should trace to a root cause and result in a specific, followed-through change.
- Volume 23 complete. Next, Volume 24: Succession Planning covers what happens if the owner can't run things tomorrow.