The Welder Knows Something You Don't
Why the best ideas in your shop are already there — if you'll ask for them.

Walk through any industrial shop floor in Alberta and you'll find the same thing: a welder, a fabricator, a foreman, an operator — people who have spent years, sometimes decades, doing the work with their hands. They know the job. They know where it bogs down. They know what would make it faster, safer, or cheaper.
Most owners and operators don't ask them.
We assume the best ideas come from the top — from the office, the consultant, the leadership team. We assume the guy on the floor is there to execute, not to think. So we plan, we direct, we optimize from a distance — and we leave the most valuable intelligence in the building sitting in a hard hat we never engaged with.
W. Edwards Deming spent his career making the same point: people come to work wanting to do a good job. The system around them is usually what gets in the way. And the people closest to the system are the ones who can see it most clearly.
So why don't we ask them?
Years ago I was a young foreman on a roofing crew. I'd hired a kid — let's call him Ben. Hard worker, on time every day, always moving. Back then, that was my whole scorecard.
Ben's job was to tear off old roofing and throw it over the edge into the bin below. Heavy, repetitive, and — though I didn't think about it at the time — not particularly safe. One day he came up to me and said, "What if we built a chute? Guide the material straight into the bin."
My first thought was: Why didn't I think of that?
I told him to go ahead. He built it in under an hour. It saved us hours a day for the rest of the project. It was safer — nobody standing at the edge of the roof anymore. And here's the part I've never forgotten: Ben didn't ask for a raise. He didn't ask for credit. He just wanted to help, and helping made him feel good. Which made the whole crew feel good.
From that day forward, I made a rule for myself: I always ask.
It reminds me of a story I came across recently — Tobin Anderson, a college basketball coach who spent 25 years in tiny gyms at the Division II and III level before finally getting his shot at Division I. In his first tournament he knocked off a #1 seed in one of the greatest upsets in NCAA history. The lesson everyone took away was about persistence. But there's another one buried in it: talent isn't where you think it is. The brightest people aren't always under the brightest lights. Sometimes they're on the bench of a 200-seat gym. Sometimes they're on the back of a Harley with a welding hood in the truck.
The leaders I respect most all share one habit: they seek advice from the people closest to the work. Not as a performance. Not as an engagement exercise. As a discipline. Because they know that's where the real intelligence in the business lives.
If you want to build this into how you run, three things to try this week:
- Pick one person on your floor and ask them one question. Not "how's it going?" — that gets you nothing. Try: "If you could change one thing about how we do [specific task], what would it be?" Then shut up and listen.
- When someone gives you an idea, let them own it. Don't take it, polish it, and present it back as yours. Put them in charge of trying it. Ben building his own chute is what made it work — and what made him want to bring the next idea.
- Do it again next week. And the week after. One conversation is a gesture. A habit is a culture. The people on your floor will know the difference within a month.
Think about that math for a second. One new idea a week is over 50 a year. Even if only a quarter of them stick, that's a dozen improvements to safety, throughput, scrap, downtime, or process. How much margin would that put back on your P&L?
You are still the boss. You can still say no. But every time you ask, you give yourself a chance to see the business through a set of eyes that's closer to the work than yours will ever be.
That's not weakness. That's leverage.
One next step: Pick the person on your team you'd be least likely to ask for advice. Ask them anyway, this week. Tell me what happens.
Further Reading & References
On Deming's philosophy of the worker and the system
- W. Edwards Deming, Out of the Crisis (MIT Press, 1982). The foundational text. Deming's argument that "a bad system will beat a good person every time" — and that the system that people work in may account for 90 to 95 percent of performance — is the intellectual backbone of this article. Dense but worth it for any operator. InspiringQuotes.usInspiringQuotes.us
- W. Edwards Deming, The New Economics for Industry, Government, Education (MIT Press, 1993). A more accessible companion. Deming's "System of Profound Knowledge" framework is especially useful if you've ever felt your team had ideas but couldn't get them implemented.
- The Deming Institute — deming.org. Free articles, podcasts, and case studies on the 14 Points and the System of Profound Knowledge. A useful primer if you don't want to commit to a 500-page book.
On the Tobin Anderson story
- Anderson spent years coaching at the Division II and III levels, most recently leading St. Thomas Aquinas to seven straight Division II NCAA Tournaments before getting his first Division I job at Fairleigh Dickinson. In March 2023 the Knights — the shortest of the 363 Division I teams in the country — knocked off top-seeded Purdue 63-58 to become just the second No. 16 seed in history to win a March Madness game. Coverage in ESPN, CBS Sports, and CNN from March 17–18, 2023 if you want the full story. CBS SportsESPN
On talent, ideas, and frontline contribution
- Daniel Pink, Drive (Riverhead Books, 2009). Pink's autonomy/mastery/purpose framework is the modern-day complement to Deming. Useful for understanding why Ben built the chute without being asked to and didn't want a raise for it.
- Edgar Schein, Humble Inquiry (Berrett-Koehler, 2013). A short, practical book on the discipline of asking instead of telling. Directly applicable to the "shut up and listen" advice in this article.
- Toyota Production System / Kaizen literature. The "one idea a week" math at the end of this article isn't theoretical — it's the operating principle behind Toyota's continuous improvement system, which generates roughly one implemented suggestion per employee per month at scale.
