I learned this inside plants; the classroom came later.

Every organization I have worked in was trying to be good at quality, and most of them had the documents to prove it.

That is the part that took me the better part of my career to understand properly: the quality manual is rarely the problem. The system on paper is usually reasonable (sometimes it is genuinely excellent), but many times it degrades anyway. Ownership blurs; the person who quietly held it together retires or moves on; corrective actions get closed without anyone verifying that they actually worked; auditing becomes a season on the calendar rather than a habit in the building. Nothing dramatic ever happens, which is exactly the problem, because the system simply stops describing how the place actually runs and no one notices until something breaks.

I have watched the reverse just as often: leadership commits genuinely to culture, invests real money in their people, and builds trust. However, if the underlying systems never catch up, the same defect recurs again, the same customer dissatisfaction happens again, and the people who were asked to care begin to understand that caring does not change the outcome. This is how a good culture sours, and in my experience this situation spreads more quickly than a bad one ever does, because the disappointment is sharper when people were told to expect better.

Both roads end in the same place: operational performance slides, the best people leave (they always have somewhere else to go), and the financials follow them out the door. The organization suffers. People stop caring.

The organizations that hold their gains build both quality systems and their underlying culture at once, rather than running culture as a new quarterly project and treating their quality systems as a project on a Gantt chart. Successful organizations bind these two elements together, with sustainment designed in from the beginning instead of bolted on after the consultant or auditor drives away. This idea is the whole thesis of my practice, and it is the reason I will not sell sustainment as a separate line item. I have seen this work and I have seen it fail: the money is on the table, and it is up to each organization to decide if they will go after it.

My foray into quality was in the regulated medical device sector, auditing to ISO 13485 and FDA requirements. Eventually I helped to lead a QMS migration project from a paper based system to an electronic one across twelve global business units, and it was eye-opening to see the similarities between these very different sites, scattered across the globe.

From there I spent several years in automotive, where the systems were good, the speed was fast, and excellence was the name of the game. Over the next decade I played a few roles: a Quality Engineer working on an ISO/TS to IATF transition; a Senior Quality and Continuous Improvement Engineer working on customer, internal, and supplier quality issues while tackling throughput problems; and a Quality Manager building up systems that either existed on paper only, or did not exist at all. I learned a great deal, and despite the different industries and product types, I saw the same common themes related to systems and culture.

The results that came out of that work are on the home page, and they are the kind of thing any buyer is entitled to ask for. What matters more here is where they came from: none of that performance came from writing a better procedure. It came from a system that people actually ran, with ownership that was real rather than assigned on an org chart, and with reinforcement mechanisms that endured after the project was completed.

Around COVID I was asked to teach at Ferris State University in their Quality Sciences and Manufacturing Engineering program. They say that you do not really understand a subject until you teach it, and that is very true: it reinforced my own understanding of the systems and tools, and it helped me enable students to put them to work the next day. I also learned a great deal from my students, and heard about the opportunities they saw in their own organizations; many of those themes led right back to systems and culture.

Teaching changed how I consult, because explaining a method clearly is a genuinely separate discipline from executing it, and most improvement work fails because people do not understand the why. Plenty of people can conduct a capability study; far fewer can make a shop floor supervisor care about what it shows him, in the language he already uses in his own cell. That translation is the most important thing a quality practitioner can do for their organization.

It is also why I build every engagement to transfer capability rather than to create dependence: if the improvement walks out the door when I do, then it was never an improvement at all, it was just a visit. I also teach quality for management, covering statistical concepts, quality tools, and why they matter.

Today I serve as Director of Quality and Continuous Improvement at a West Michigan manufacturer, and I am building this practice alongside that work. I truly believe that the next generation of workers in manufacturing are primed and want to build something; the question is whether employers can take advantage of that talent and create a sustainable business where everyone wins.