We use mission statements, leadership principles, and quality policies to define our culture and to shape how we work. But while these documents are impressive on paper, they often remain too vague for action and fail under real-world pressure.
|
ADVERTISEMENT |
Why is there such a gap between what we aspire to and what we actually do? I’ve looked into this question through the lens of quality policy. But this applies to any workplace policy.
The cost of paper compliance
History gives us painful reminders of what happens when quality policies exist on paper but aren’t lived in practice. In 1986, NASA’s own requirements clearly stated that the shuttle should not launch in low temperatures. The engineers raised concerns about the O-rings, but under schedule pressure and poor decision-making, the launch went ahead. The tragic result was the Challenger disaster.
The quality policy is a core requirement across major quality standards (ISO 9001, IATF 16949, AS9100, and FDA QSR). While wording differs, the intent is always the same: Leadership must define a policy that fits the organization’s purpose, guides objectives, commits to compliance and continual improvement, and is understood at every level.
On paper, the standards make the quality policy the most important document. Organizations fall short because they fail to translate policy into daily behavior. It’s easy to write “customer focus,” but what does that mean to an engineer, a manager making a trade-off, or an operator on the floor?
The certification trap
To make it worse, the wider system of certification puts more focus on checking for the presence of documents or procedures rather than the observable behaviors showcasing quality. Why? Because behavior is much harder to verify, especially when it must trace back to the quality policy. Audits can create false confidence when they focus on paper trails and ignore behaviors. There are big opportunities for improvement in this area by strengthening behavioral audit capability and moving from documents to behaviors and mindset. In my view, this is a critical step and will be the topic of another essay.
There are countless stories across industries of audits where employees struggled to recall the quality policy. The reductive response was often to laminate the statement and distribute it so people could memorize it. That may satisfy the auditor, but it does little to build real understanding or change behavior. I’ve seen audits where an operator pulls a laminated card from their pocket, reads the policy aloud, and the box gets checked—with no one asking whether they have ever stopped a shipment because of it.
Turning words into behavior
The challenge is to turn words into consistent behavior. This requires using simple, easy-to-understand language, setting clear expectations, enforcing them, and connecting every document and standard operating procedure (SOP) to the quality policy. This is hard work, and there are no shortcuts.
The behaviors linked to the quality policy must be made tangible in instructions, SOPs, and specifications. These documents shouldn’t just outline steps; they should reinforce behavior as well. Good behaviors need to be recognized and rewarded. Poor behaviors must be detected, documented, and corrected. This reinforcement must be built into the system through team recognition, performance reviews, and clear accountability.
This piece is often missed or overlooked in audits, which tend to rely on checklists, KPI dashboards, or paper compliance rather than behavioral evidence.
No organization should call itself customer-focused if management consistently prioritizes speed over quality or lowers the bar to avoid costs and delivery misses. Most organizations can be “audit ready,” train people to repeat the policy, and pass. But missed deliveries, recalls, and regulatory escalations will always tell the real story.
Customer focus in practice
Here are some tangible examples of how customer focus can be embedded into practice.
Supplier parts: No incoming part is released without verification, and any exception goes through a defined concession and documented procedure.
Process change: No change is implemented without review, validation, and approval—with clear accountability for sign-off.
Traceability: Documentation and traceability are never bypassed, even under schedule pressure.
Leadership modeling: Leaders demonstrate commitment by rejecting a profitable but noncompliant batch.
Empowerment: Management publicly celebrates an employee who stopped a launch or shipment due to a policy concern.
The same goes for continual improvement, another core element of major quality standards. It will not happen unless people can speak freely, share ideas, and challenge weak practices without fear.
This is where quality becomes real. Not on the wall. Not in a slide deck. Not in a workshop. But in the way work gets done every day. Culture is built when policies are lived through daily practice, reinforced with accountability, and modeled without compromise by leadership.
The ‘North Star’ quality policy
Now, how can you incorporate these ideas into your quality policy and avoid the pitfalls? First, sit with your leadership and define what your key terms and goals mean to your organization. Then, translate them into simple and clear language for every level. Finding the right words and language will require discussion with different parts of your organization to ensure the language is universal and a good fit. This sounds simple, but it will be difficult because the quality policy must remain brief and serve as a North Star. Leadership must be prepared to live every word written here. If the policy fails at the top, it will collapse on the shop floor. It should be written so every person in your organization can easily internalize it and immediately understand what’s expected. Below, I have attempted to create a quality policy with these steps in mind.
Our standard
• We ensure that all work we do is safe and meets all applicable requirements.
• If the work’s not done right, we don’t pass it on.
• If we’re unsure, we stop and ask.
Our commitments
• Integrity: We must tell the truth in our records and words, even when the news is bad.
• Clarity: We make sure the requirements are clear before we begin our work.
• Resources: Management will provide the time, tools, training, and support needed to do the job right.
• Customer focus: We don’t hide problems to protect our schedules or internal metrics, because we never shift the cost or risk to our customers.
• Continual improvement: We fix the causes of problems instead of blaming people, and we constantly look for better ways to work while meeting all customer, legal, regulatory, and other applicable requirements.
Your rights and authority
• The right to stop: Anyone has the authority to stop work if they believe quality or safety is at risk, or if the instructions are unclear.
• Psychological safety: No one will be penalized for raising a concern in good faith, even if it later turns out to be a false alarm.
• Ownership: Every person owns the quality of their own work. Management owns and is responsible for the systems that support that work.
Our accountability
We live this policy by setting clear quality objectives at every level, reviewing them regularly, and ensuring everyone knows where we stand.
The next time you look at your quality policy, ask yourself: How is that policy actually considered in business decisions at your level? What happens if a decision contradicts it? If your quality policy doesn’t automatically come to mind during daily tasks, and it doesn’t change behavior under pressure, it’s just a decoration.

Comments
About Quality Policy
Excellent article.
Quality Policy drives quality culture.
Those on the shop floor, they must believe in doing it right all the time by following the approved procedures. As an auditor I take that as an indicator of the depth of quality culture in that organization.
Quality vs Ship Date
The worst offenders in policy making are the leaders who have decided that making an easy anagram solve all of the problems. too many rely on the work "Quality" or "Six Sigma." Then all the leader has to say is, "Just remember, our quality policy is "Six Sigma" and/or stick a bunch of posters up around their company explaining what the anagram means. Very few front-line workers could articulate that policy verbatim. This includes people actually working in quality. It ignores the fact that "quality" is not a department, it is an inherent characteristic of the product; It either has it or it doesn't. Training must begin today to educate the front line to understand the difference. This is also a failing in auditors' responsibility. Once confronted by a ubiquitous answer, they should press for more personal answers; "How do you affect quality in your job?" or even just "What does quality mean to you?"
What Becomes the ‘Real Policy’?
Strong perspective, Hossein - especially how policies collapse under real-world pressure. The Challenger example underscores how costly that gap can be.
I shared your views in this article with a colleague today, and we’d push this a step further: in many organizations, the issue isn’t lack of understanding - it’s that the system quietly rewards behavior that contradicts the policy. Over time, the “real policy” becomes whatever gets decisions approved under pressure.
This echoes Thomas L. Martin Jr.’s 'Hierarchiology' in his book 'Malice in Blunderland' - where intent degrades as it moves through layers.
From a TRIZ perspective, this is a classic contradiction: we want speed and efficiency, but not at the expense of quality and integrity. If that contradiction isn’t explicitly resolved, behavior will consistently default to the stronger pressure.
The examples you shared are powerful because they make policy observable in real decisions. The challenge is making those moments expected and repeatable, not exceptional.
Curious what you’ve seen work in practice: what system-level mechanisms ensure the policy survives contact with real-world pressure across layers?
Thanks for the thoughtful…
Thanks for the thoughtful feedback and for extending the argument. I was not familiar with the Hierarchiology reference, but it sounds relevant. I need to read that book.
On what I have seen work best to live the policy, a few mechanisms are quite important in my view.
The visibility of leadership reaction when someone raises a quality concern is very powerful. This is where quality culture is either built or damaged, depending on the leadership response. I do not expect management to be happy about every concern raised. There is always cost, delivery, and risk to balance. But leaders and middle managers can make or break whether the policy stays on paper or becomes reality through how they behave in those moments.
Clear rights and ownership when quality is at risk also matter. This sounds obvious, and it is often written in procedures, but under pressure it is not always clear. If ownership is vague, people may maneuver around the responsibility, especially when the decision is stressful or uncomfortable.
KPIs are also tricky. They can become biased toward green status, and sometimes they can even be gamed. KPIs need to be defined carefully and cross functionally, so they do not unintentionally reward the wrong behavior. This is easy to say, but extremely hard to implement.
Routine review of exceptions, waivers, and stop shipment decisions is also very effective. Often these are reviewed case by case, but when we look across them, patterns can emerge. Those patterns may reveal the culture we created, even if it was not the culture we intended to have.
Add new comment