A plant manager said something to me last month that I have not been able to stop thinking about. "We are going to wait for ISO 9001:2026," he said, "and use the transition to fix our culture problems."

I nodded politely. Inside, I was doing the math on how many millions of euros that approach would cost him before he realised his mistake.

Standards do not fix cultures. Cultures fix cultures. A standard gives you a framework, a structure, a set of requirements. It tells you what a functioning quality system looks like. It does not — cannot — make your organisation function. That is a human job, and it is done through daily decisions, not document updates.

The culture that eats compliance

I have audited plants that were textbook-compliant on paper and dysfunctional in practice. Perfect documentation. Impeccable training records. Beautifully maintained procedure manuals. And a shop floor where operators had stopped reporting problems because "nothing happens when we do." Where quality engineers spent their days formatting spreadsheets instead of solving problems. Where the management review meeting was a thirty-minute presentation of green dashboards followed by zero decisions.

Peter Drucker did not actually say "culture eats strategy for breakfast." But the observation holds regardless of attribution. Culture eats compliance for breakfast, lunch, and dinner. It eats your corrective action system. It eats your risk register. It eats your beautifully documented control plans and spits out rework reports.

You cannot audit your way into integrity. You cannot document your way into accountability. You cannot certify your way into giving a damn.

What a culture problem actually looks like

Let me be specific, because "culture" is one of those words that means nothing if you do not ground it in observable behaviour. Here are the symptoms I look for when I walk into a plant:

Problems are repeated. The same nonconformances appear month after month. The corrective action database is full of "operator error" findings that lead to "retrain operator" actions. Nobody asks why the system allowed the error in the first place.

Metrics are gamed. Scrap numbers magically improve right before the quarterly review. First-pass yield is calculated on processes that have been quietly reclassified. The dashboard is green; the reality is not.

Quality is a department, not a responsibility. Operators say "that is quality's job" when asked about process control. Engineering says "we designed it, quality needs to inspect it." Leadership says "we hit our numbers" without asking what had to be sacrificed to hit them.

Meetings produce no decisions. Management review is a status update, not a decision-making forum. Problems are presented, discussed, and tabled. Nothing is owned, nothing changes, and the next meeting reviews the same data with the same conclusions.

If you see two or more of these patterns, ISO 9001:2026 will not help you. A transition audit will generate findings. You will close them with corrective actions. The findings will recur in the next audit. The cycle will repeat until someone in leadership decides that the problem is not the standard — it is the organisation.

What actually fixes culture

I have seen culture turn around. It is not pretty, it is not fast, and it does not come from a document revision. It comes from a small number of leadership decisions, repeated consistently over time:

Visible accountability. When a problem occurs, the person responsible owns it publicly — not to be punished, but to be transparent. Problems are treated as system failures to be solved, not individual failures to be hidden.

Psychological safety. Operators who report problems are thanked, not blamed. Quality engineers who stop lines are supported, not pressured. The message, reinforced daily, is that catching problems early is valued more than shipping questionable product on time.

Follow-through. When a corrective action is assigned, it is completed and verified. When a management review decision is made, it is implemented. When a policy is written, it is enforced consistently — for everyone, including leadership.

Honest metrics. The dashboard reflects reality, including the uncomfortable parts. Bad news travels fast and is acted on. Good news is verified before it is celebrated.

None of this requires ISO 9001:2026. All of it is enabled or destroyed by the daily choices of leaders. The standard can support a healthy culture. It cannot create one.

Use the transition anyway

Here is my actual advice. Use the ISO 9001:2026 transition as a catalyst — not a solution. It gives you a legitimate reason to ask hard questions, revisit assumptions, and reset expectations. It creates a window where leadership attention is focused on quality, and that attention is the raw material of culture change.

But do not confuse the catalyst with the reaction. The standard is a tool. The work is human, behavioural, and daily. If you are not willing to do that work, no revision of any standard will save you. And if you are willing to do that work, you do not need to wait for 2026 to start.

Start tomorrow. Start at the next shift huddle. Start by asking the question nobody asks: what is one thing that is broken that we have all agreed to live with? Fix that one thing. Then fix the next. That is how culture is built — one uncomfortable conversation at a time.