Blog

The answer tells me almost everything I need to know.

In some organizations, the answer comes back quickly and confidently: "The quality department is responsible for that." In others, the answer is slower, they think about it and sometimes they mention that the operators do quality, others that quality starts with the designers, having a robust design, but normally, finance, HR, IT, they stay quiet or indicate that it is quality function responsibility. However, there is a group of people outside of Quality department (Engineering, Operations, Maintenance....)  that when asked, they make a pause and answer that they do quality. That pause, that collective ownership, is one of the most reliable signals of a genuine quality culture I have encountered in three decades of the quality world.

Philip Crosby's insight cuts right to the heart of why that distinction matters so much.

Two Organizations, One Question

Imagine two companies. Both have ISO-certified quality management systems. Both pass their customer audits. Both have quality departments with trained professionals, documented procedures, and established metrics.

In the first company, quality is a function. It sits in a department, managed by people with quality titles, governed by a set of procedures that everyone else is expected to follow. When something goes wrong, the quality department gets called. When an audit approaches, the quality department leads the preparation. Quality is important here but it belongs to someone specific.

In the second company, quality is an identity. The manufacturing engineer who catches a potential failure mode in a design review does not think of themselves as doing the quality department's job. They think of themselves as doing their job. The procurement manager who pushes back on a low-cost supplier because of quality risk does not need to escalate to quality for permission. It is simply part of how they make decisions.

Both companies have quality. Only one of them is a quality organization.

Crosby's distinction  "the fabric" versus "part of the fabric" is the line between those two companies. And crossing that line is one of the hardest, most consequential things a quality leader can do.

How Culture Gets Built and How It Gets Revealed

Quality culture is not declared. It is not launched in a town hall or embedded in a mission statement or written in the Quality Policy. It is built slowly, through thousands of small decisions, and it is revealed under pressure. It is through people behavior, through their attitudes, through discipline.

The real test of a quality culture is not what happens during an audit or a customer visit. It is what happens the week after an audit closes, when the customer is not there. It is what happens when a shipment is late and someone has to decide whether to send parts that are borderline acceptable. It is what happens when a team discovers a process gap that no customer has noticed yet and has to decide whether to fix it now or wait.

In a compliance culture, those decisions get made based on what is required. In a quality culture, they get made based on what is right. That difference is the fabric Crosby was describing.

Building it requires three things that no procedure can mandate:

1) Leadership that models the standard. Culture follows behavior at the top. When leaders visibly hold the quality standard, especially when it is inconvenient, especially when it costs time or money, they communicate that the standard is real. When they compromise it quietly, everyone notices. Culture is downstream of leadership behavior, not leadership messaging.

2) Accountability that is consistent, not selective. Nothing erodes a quality culture faster than watching standards applied unevenly — enforced on the shop floor but quietly waived in the boardroom, applied to suppliers but not to internal teams, required during audits but optional in between. Consistency is credibility. Without it, the culture learns that quality is situational.

3) Recognition that reinforces the right behavior. What gets celebrated gets repeated. If your organization only recognizes output — units shipped, revenue booked, problems solved — but never recognizes the engineer who caught a risk before it became a problem, or the operator who stopped the line to prevent a defect, you are signaling what actually matters. Recognition is one of the most underused tools in quality culture building.

The Structural Shift

At some point in a quality leader's career, the most important work stops being about systems and starts being about culture. You can design a perfect quality management system and still have a quality problem if the culture does not sustain it. The system is the skeleton. Culture is what makes it move.

I have seen organizations with mature, well-documented quality systems that produced mediocre results because the culture treated the system as a compliance burden rather than a way of working. And I have seen organizations with simpler systems that outperformed on quality, because everyone in the building genuinely cared about the outcome.

The system matters. But it is not enough on its own.

Crosby understood that the ultimate competitive advantage in quality is not a better procedure. It is an organization where quality is not something people do because they are required to. It is something they do because it is who they are.

That is a quality culture. And building one is the most important work a quality leader will ever do. Quality is everyone's responsibility. 

Is quality the fabric of your organization — or part of it? The difference is worth reflecting on.

by Alma Catarino

#Quality, #QualityMindset, 

Once a process is clearly defined, you can measure it. Once you can measure it, you can improve it. Once you can improve it and document the improvement, you can scale it. That is the path from people-dependent quality to true quality excellence, a system strong enough to sustain performance regardless of who is in the room.

I have seen this in world-class manufacturing environments. I have seen it in engineering teams with decades of experience. I have seen it in mom-pop shops. The capability is real. The output is excellent. But the knowledge lives in a person, not in a system. And knowledge that lives only in a person is knowledge that has not yet been fully understood.
Deming's insight is that true understanding, the kind that can be taught, transferred, measured, and improved, requires the ability to articulate what you are doing as a sequence of defined steps with known inputs and expected outputs. If you cannot do that, you are executing on intuition and experience. Both are valuable. Very true, but neither is sustainable, scalable, or improvable in the way that a documented, understood process is.

When work is understood as a process, four things happen — all of them worth pursuing.

Variation becomes visible and actionable. A defined process gives you a baseline. And a baseline is the most powerful quality tool you have, because it turns noise into signal. When every team member follows a common standard, differences in output become meaningful data rather than unexplained randomness. You can see where the process drifts, catch it early, and correct it before it reaches the customer. What was once invisible becomes a dashboard.

Improvement becomes intentional. A defined process is the starting point for every meaningful improvement. Once the steps are clear, you can test changes, isolate variables, and know with confidence whether what you did actually made things better. Kaizen, DMAIC, designed experiments; all of them require a documented current state to push off from. When the process is written down and understood, improvement stops being a hope and becomes a discipline.

Knowledge stays in the organization. One of the most valuable things a quality leader can do is convert individual expertise into institutional knowledge. When a process is documented well enough that anyone can learn it, the organization has made a permanent investment in its own capability. People will always come and go, but a well-defined process means their knowledge stays behind, ready for the next person, and the one after that.

Training becomes a foundation. When a new team member joins and a clear process exists, onboarding becomes consistent, confident, and fast. They are not relying on whoever has time to show them, or hoping that the person training them remembers every step. They are learning from the organization's best-known method and because the process is defined, any gap they surface becomes an opportunity to make the documentation even better.

Describing something as a process is not the same as writing a procedure. A procedure is a document. A process is a way of thinking about work.

Process thinking means being able to answer, for any work activity:

• What are the inputs? What must be true at the start for this to succeed?

• What are the steps? In what sequence, under what conditions?

• What are the outputs? How do we know when the process has worked?

• What are the failure modes? Where is this process most likely to go wrong, and how would we know?

• What can be measured? What data tells us whether this process is performing as intended?

These questions sound simple. But asking them rigorously about work that has been done "the same way for years" almost always surfaces gaps, assumptions, and undocumented variations that no one had formally acknowledged.

The discipline of process thinking is not bureaucracy. It is the opposite of bureaucracy, it is the pursuit of genuine understanding over comfortable habit.

by Alma Catarino

After more than thirty years in this field, it is the belief that has never left me, not as a motivational phrase, but as a lived, tested, professional conviction.

I have never walked into a process that could not be improved. Not once. I have walked into processes that were award-winning. Processes that had survived for decades without a significant quality escape. Processes that teams were deeply proud of and rightfully so. And in every single one of them, there was something that could be done faster, with less variation, at lower cost, or with greater reliability.

This is not a criticism of those processes or the people who built them. It is the most hopeful idea in quality management: nothing is ever truly finished, which means nothing is ever truly stuck.

The Danger of "Good Enough"

In every organization or team, this conversation happens at some point. A process has been stable for a while. The metrics look acceptable. The customer is not complaining. And someone says some version of: "Let's not fix what isn't broken."

I understand the impulse. Stability is hard-won in manufacturing environments. Unnecessary change introduces risk. There is real wisdom in not disrupting a well-functioning system without good reason.

But there is a difference between *protecting stability* and “mistaking stability for optimality.” A process that is not generating complaints right now is not necessarily the best version of that process. It may simply be generating waste quietly, in the form of rework that has become normalized, variation that has been absorbed into wide tolerances, or inefficiency that has been accepted because it has always been there.

The philosophy that everything is perfectible does not mean everything needs to be changed immediately. It means we never stop asking whether there is a better way. The question is always open. The process is always in progress.

What Continuous Improvement Actually Requires: Quality Mindset

The concept of continuous improvement (For example, kaizen, in the Toyota Production System tradition) is widely understood in quality circles. But understanding it as a concept and living it as a discipline are two different things.

I have come to believe that the tools of continuous improvement: PDCA, DMAIC, kaizen events, value stream mapping are secondary to the mindset that drives them.

The quality mindset is this: the current state is not the final state. Whatever we are doing today can be done better tomorrow. And the work of finding that better way is not a burden on top of the job: it is the job.

This quality mindset changes how you walk a production floor. It changes how you run a review meeting. It changes how you respond when a process generates a defect — not with frustration that something went wrong, but with curiosity about what the defect is trying to tell you about a gap in the system.

After thirty years, I still find this the most energizing part of quality work. Every process I encounter is a puzzle that is not yet fully solved. Every metric that falls short of its potential is an invitation to understand something I do not yet understand. Every improvement, however small, is evidence that the philosophy is true.

Everything is perfectible. I have never found a reason to doubt it.

Let’s do the following reflection: What is a process in your organization, in your team, that everyone has accepted as "good enough"  but you suspect has more room to give? That might be where your next improvement lives.

by Alma Catarino

A defect escapes. A customer complains. Leadership responds by adding more inspection steps, more checkpoints, more sign-offs. The logic seems sound: if we catch more, we ship less bad product.

But Deming saw through this logic decades ago, and the organizations that truly understand quality have never forgotten his warning. Adding inspection does not create quality. It only reveals the quality that was already built in, or built out, long before the product ever reached the inspector's hands. Inspection is too late.

The Inspection Trap

Here is the uncomfortable truth about inspection: you pay for a process you do not fully trust.

Every time a product moves through an inspection station, the organization is admitting that the upstream process might have failed. And the more inspection you add, the more you are confessing that your process is unreliable, your inputs are inconsistent, and your controls are insufficient.

This is not to say inspection has no role. It does. In certain regulated industries, in safety-critical applications, in early-stage product development, inspection is essential and appropriate. But inspection as a substitute for process control is one of the most expensive actions a quality organization can make.

The cost is not just the labor of inspectors. It is the rework, the scrap, the customer escapes that slip through, the organizational mindset that says "someone else will catch it." That mindset is perhaps the most dangerous cost of all.

Where Quality Is Actually Made

If quality cannot be inspected into a product, where does it come from? It is built in long before the product reaches any checkpoint. Quality lives in:

The design phase: When engineers make choices about tolerances, materials, and specifications, they are determining the quality ceiling of everything that follows. A product designed with insufficient margin for manufacturing variation will generate defects regardless of how tightly it is inspected afterward.

·         The process planning:  When manufacturing engineers define how a product will be made (the sequence of operations, the tooling, the parameters) they are writing the quality story before a single part is produced. A process that is difficult to run consistently will produce inconsistent quality consistently.

·         The supplier selection and development process: The quality of incoming materials and components sets the floor for everything built on top of them. Organizations that underinvest in supplier quality development will spend far more downstream trying to inspect their way out of incoming variation.

·         The training and standardization of people: When operators understand not just what to do but why it matters, when they understand the downstream consequence of getting something wrong, they become the most powerful quality control system in the building. Not because they are inspecting their own work, but because they are committed to getting it right the first time.

By the time a product reaches an inspection point, all of these decisions have already been made. The inspector is simply measuring the outcome of choices made hours, days, or months earlier.

The Shift From Detection to Prevention

The most meaningful transformation I have seen quality organizations make is not the adoption of a new tool or standard. It is the shift in mindset from detection to prevention.

Detection mindset asks: “Did we catch the defect before it reached the customer?”

Prevention mindset asks: “Why did the defect occur, and how do we eliminate the conditions that allowed it to exist?”

These are fundamentally different questions, and they drive fundamentally different mindsets. A detection-focused organization invests in inspection capacity. A prevention-focused organization invests in process capability, root cause analysis, design robustness, and supplier development.

As W. Edwards Deming also taught us, the goal is to work on the system, not just the output of the system. Inspection measures the output. Prevention improves the system. And only an improved system produces sustainably improved output.

A Question Worth Asking Honestly

Here is a diagnostic I often ask to quality teams: look at where your organization spends its quality resources. Count the hours, the headcount, the budget. How much goes toward finding defects after they are made? How much goes toward preventing them from being made in the first place?

Most teams, if they are honest, will find the ratio heavily tilted toward detection. That is not a character flaw, it is a natural consequence of how quality problems present themselves. A defect found at inspection is visible and urgent. A process capability gap that has not yet caused a defect is invisible and easy to defer.

But the invisible gap is the more important problem. And addressing it is the work that separates organizations that are merely compliant from organizations that are genuinely excellent.

Inspection will always have a role. But it should be the last line of defense, not the primary strategy.

Build the quality in. It is the only way it gets there.

My last thought goes to the following question: Did this challenge how your organization thinks about inspection? Share it with your quality team.

by Alma Catarino

.......I have walked production floors, led audits, built quality systems from the ground up, and sat in rooms where organizations debated what went wrong after something already had. And in all that time, this quote by Henry Ford has never stopped being the most honest thing ever said about quality culture.

Not the most technical. Not the most sophisticated. The most honest.

Because the truth is this: you can have the most robust control plan ever written, the most comprehensive inspection protocol, the most meticulously documented quality management system — and still experience failures. Not because the system was wrong, but because quality never actually lived in the system to begin with.

The Illusion of the Audit-Ready Organization

There is a version of quality that organizations perform. It looks impeccable on paper. The binders are organized. The procedures are current. The corrective actions are closed on time. During a third-party audit, everything flows smoothly.

And then the auditors leave.

What happens in the hours, the shifts, the decisions that follow — that is where real quality is made or broken. The operator who skips a verification step because the line is behind schedule. The engineer who approves a deviation without fully documenting the risk. The manager who looks the other way because the shipment has to go out tonight.

None of those moments happen in front of an auditor. All of them determine quality outcomes.

This is what Ford understood intuitively: quality is not a performance for an audience. It is a set of standards you hold yourself to when no one would ever know the difference. And in a complex manufacturing or service environment, most of the decisions that determine quality are made exactly like that — quietly, in the moment, without a supervisor present.

Culture Does the Work Systems Cannot

I have seen this play out in two very different types of organizations.

In the first, quality is owned by the quality department. Everyone else cooperates with it — they fill out the forms, they attend the required training, they know what to do when the auditor is on the floor. But quality is fundamentally someone else's job. It lives in a department, not in the building.

In the second, quality is embedded. It is how people think about their work. An operator notices something slightly off in a part dimension and stops to investigate — not because a procedure tells them to, but because they genuinely do not want to pass a defect forward. A team leader flags a process drift before it becomes a nonconformance — not to avoid getting in trouble, but because catching it early is simply the right thing to do.

The difference between those two organizations is not documentation. It is culture. And culture is not something you can write into a procedure. It is built through leadership, through what gets rewarded, through what gets tolerated, and most importantly, through what leaders themselves model when no one is looking.

As Aristotle wrote: "Quality is not an act, it is a habit." Habits are formed by repetition, not by policy. They are reinforced by the environment, not by inspection.

What This Looks Like in Practice

Building a quality culture that holds up when no one is watching requires a deliberate shift in focus — from outputs to inputs, from detection to prevention, from compliance to commitment.

A few things I have seen work:

Make the standard the expectation, not the exception. When quality behavior is normalized — when doing it right is simply what people in this organization do — it stops requiring enforcement. People police themselves and each other, not out of fear, but out of shared identity.

Lead visibly by example. If a manager skips a step under pressure, the team learns that steps are optional under pressure. If a leader stops and does it right even when it costs time, the team learns that the standard is real. Culture follows behavior at the top.

Create safety around raising concerns. People will only speak up when they see something wrong if they trust that speaking up is valued. Organizations that punish messengers get silence. Silence is where defects grow.

Celebrate catching problems, not just preventing them. Recognize the operator who stopped the line. Acknowledge the engineer who escalated the deviation. Make it visible that doing the right thing matters here.

The Question Worth Asking

If your team ran their shifts for a full week with no supervisors, no audits, no external oversight — would the quality outcomes be different?

If the honest answer is yes, the gap is not in your system. It is in your culture. And that gap is closeable, but only through consistent, intentional leadership — not through adding another checkpoint.

Henry Ford said it in one sentence. It has taken me thirty years of practice to understand everything packed inside it.

Quality means doing it right when no one is looking. Everything else is just compliance.

by Alma Catarino
June 27, 2026