Mistake-Once Process Library
Convert every solved operating problem into a reusable process
- Difficulty
- Easy
- Time to result
- ~ongoing to results
- Steps
- 5
- Confidence
- 98%
The Mistake-Once Process Library turns operating experience into a durable system. Whenever a meaningful issue appears, the operator solves it, records the solution, and converts that response into a process that can be retrieved the next time a similar issue occurs. The value compounds across years: common problems stop requiring fresh invention, employees receive consistent guidance, and the owner's judgment becomes available beyond the original conversation. Williamson describes thirteen years of mistakes that were only made once because each answer became a process. The framework also corrects the belief that every client's situation is unique. Many apparently bespoke problems belong to recurring classes, so the business can preserve a standard evidence-based response while still checking whether the current case differs in a material way.
Origin
Williamson describes how he and his business partner accumulated processes by recording solutions to problems encountered over thirteen years of operating.
Core principles
- 01Recurring business problems are rarely unique
- 02A solved problem should become organizational memory
- 03Written processes prevent repeated mistakes
- 04Accumulated solutions make future decisions faster
How to run it
- 1
Capture the issue
Write down the operating problem while its details and consequences are still clear.
Pro tip Describe the trigger and observable symptoms, not only the complaint.
- 2
Resolve the case
Apply a solution and verify that it addresses the actual problem.
Pro tip Keep the evidence that showed the fix worked.
Watch out Do not standardize an unverified guess.
- 3
Write the process
Convert the successful response into clear actions another person can follow.
Pro tip Include the conditions under which the process applies.
- 4
Retrieve before reinventing
When a similar issue returns, check the library and apply the existing process before creating a new answer.
Pro tip Classify the problem by mechanism rather than by the customer's wording.
Watch out Confirm that the current case is materially similar before reusing the process.
- 5
Update from exceptions
Revise the process when a new case exposes a missing condition or a better solution.
In the wild
Williamson says that he and Darren are not inherently exceptional at business, but have spent thirteen years making mistakes once and creating a process for each recurring situation.
→ Few later problems require an entirely new response.
Common mistakes
Leaving the solution in one person's head
An undocumented answer disappears from the organization when the original operator is absent.
Treating every case as unique
Surface differences can obscure a standard underlying problem that the business has already solved.
Is it for you?
Best for
It is best for small businesses accumulating recurring customer, staff, and delivery issues.
Not ideal for
It is not ideal for genuinely novel crises where an old process would conceal important differences.
From the transcript
“as you encounter particular issues write down your solution that you gave to those issues”
“were not actually that good at business but we've made 13 years of mistakes that we only made once”
“now we have a process for there's very rarely very very rarely that I come up against”
From the episode
Business Principles 101 - #083