Episode
41
Thu, 22 Oct 2026 12:00:00 +0000
Most business owners spend their days trying to keep production moving.
Brad Cairns did the opposite.
He shut his factory down.
Not for an hour. Not for an afternoon.
The “stop and fix” ultimately lasted eight days.
And for an operation doing roughly $30,000 per day in throughput, every day the machines remained silent came with very real pressure.
So why do it?
Brad's team manufactures MDF cabinet doors. Like many modern manufacturing operations, they track quality issues and defects.
One morning, Brad noticed a number on the company's quality dashboard that immediately caught his attention.
Glue squeeze-out: approximately $40,000.
Brad estimated that cost had accumulated over roughly 60 days.
The team wasn't ignoring the problem. They had been trying different things to address it. But the defect continued.
That created a bigger question:
At what point do you stop trying to work around a recurring problem and stop the process entirely so you can understand what's actually happening?
Brad decided they had reached that point.
One by one, the machines were turned off.
The factory went silent.
Brad has spent decades studying and practicing Lean manufacturing and the Toyota Production System.
The idea itself sounds straightforward: when there's a problem, stop the line, understand the problem, fix it and then restart.
Actually doing it is another matter.
Stopping production means confronting the immediate cost of downtime. Brad estimated his factory's throughput at around $30,000 per day.
That's precisely why the decision became such a powerful test of Lean thinking.
Instead of asking only what stopping would cost today, the team had to confront what repeatedly allowing the same problem to continue could cost over time.
The shutdown wasn't resolved with one brilliant idea.
It took eight days.
The team tested variables and examined the process in detail. As the days passed, Brad noticed an important change in how his people approached the problem.
They began relying less on opinions and more on data.
Instead of arguing about whose idea sounded right, they could test an idea and look at what actually happened.
That distinction eventually became one of the principles in Brad's “Red Team Code”:
Run experiments, not arguments.
Other principles included changing one variable at a time, measuring everything, fixing what's fundamentally wrong first, staying patient and solving the root cause rather than the symptom.
The experiment didn't just expose lessons about machinery.
It exposed lessons about people.
Brad described his team brainstorming, agreeing, disagreeing and learning how to have productive conflict.
Every morning, they communicated where the team was, where it was going and what it was doing so the rest of the company could understand what was happening.
The stop-and-fix was becoming a culture-building exercise.
Brad said that by around day six, the financial pressure was still very real. But after seeing what his team was getting from the process, his perspective changed dramatically.
The value was no longer limited to eliminating one defect.
The team was learning how to solve problems.
One of the most interesting outcomes was what happened after the team deeply studied the process.
Because they had tested so many settings and variables, they developed a much deeper understanding of the machine and its behavior.
They turned that knowledge into a troubleshooting flowchart.
If a particular defect appeared, the system could guide someone through what to check first, second and third.
That's a very different outcome from simply getting the machine working again.
The team was capturing knowledge.
Instead of depending entirely on one experienced person's intuition, they were building a repeatable process.
There's another lesson in Brad and Dominic's conversation that applies far beyond one machine.
Waste isn't always sitting on the shop floor.
It can begin upstream—in estimating, engineering, administration, cut lists and the information being sent into production.
If bad information repeatedly enters an efficient manufacturing system, the business can simply become very efficient at manufacturing mistakes.
That's why operational improvement isn't only about making machines move faster.
It's about improving the system that surrounds those machines.
Shutting down a factory for eight days isn't a prescription for every quality issue.
But Brad's story raises a valuable question:
What recurring problem have you become too accustomed to working around?
Many businesses develop extraordinary skill at compensating for problems.
People create workarounds. Experienced employees learn tricks. Managers build extra steps into the process. Rework becomes normal.
Eventually, the workaround becomes part of the operation.
Brad's experiment demonstrates another possibility: stop treating the symptom long enough to understand the root cause.
The immediate cost can be uncomfortable.
But so can paying for the same problem month after month.
Watch the full conversation between Dominic Rubino and Brad Cairns to hear the complete story behind the eight-day factory shutdown, the lessons it produced and the Red Team Code that emerged from the experience.
More about Brad Cairns:
Instagram: https://www.instagram.com/stolbek_machines/
Website: https://stolbek.ca/
Youtube: https://www.youtube.com/@stolbekmachines
Connect with Us:
.svg.webp)
