A technician reports the same defect for the third time. The supervisor is under pressure to meet a production target. Does the supervisor thank the employee for raising the concern and investigate what is happening? Or does the employee learn that it's better not to bring up problems when production is behind schedule?

That interaction can tell you a lot about an organization's quality culture. The newly revised ISO 9001:2026 standard puts greater emphasis on quality culture, ethical behavior, and leadership accountability. That's a worthwhile development, but it raises a practical question: How would you know whether your organization actually has a strong quality culture?

Having a quality policy is one thing. Having a management system that consistently supports quality and improvement is another.

What's New in ISO 9001:2026?

The International Organization for Standardization published ISO 9001:2026 on September 16, replacing the 2015 edition. This isn't a complete overhaul of the standard. As ISO explains in its summary of the revisions, the new edition reinforces several important expectations concerning leadership, employee awareness, and continual improvement.

Clause 5.1 strengthens the emphasis on leaders promoting quality culture and ethical behavior. Clause 7.3 adds emphasis on employee awareness of those expectations, while Clause 6.1 more clearly distinguishes managing risks from pursuing opportunities.

These changes reinforce something Lean practitioners have been saying for years: quality isn't just the responsibility of a department. It depends on how people work together, how managers lead, and what happens when problems are discovered. Putting quality culture into a standard doesn't automatically create one, of course. That's still up to management.

What Happens When Someone Identifies a Quality Problem?

One way to evaluate an organization's quality culture is to follow a real problem from identification through resolution. Consider a manufacturing employee who notices recurring defects or a healthcare employee who identifies something that could delay patient care. What happens after they raise the concern? I'd want to know whether the problem was acknowledged, whether someone took responsibility for investigating it, and whether the employee remained involved or informed.

A strong quality culture doesn't mean every employee suggestion gets implemented or every problem gets fixed the same day. Sometimes an idea isn't feasible, or the problem is more complicated than it first appears. Sometimes management has to prioritize a more pressing risk. But employees should be able to expect a thoughtful response, even when immediate action isn't possible.

In a previous KaiNexus article about measuring continuous improvement culture, I argued that the time between an employee raising a problem and receiving a meaningful response can be especially revealing. For evaluating quality culture more broadly, I'd go further. Was the problem investigated? What was decided? Was an effective countermeasure implemented, and how did the organization verify the results? That tells us more than whether someone filled out the appropriate form.

Quality problems become especially difficult when organizations face competing pressures. Imagine that a production team discovers a potential defect shortly before an important shipment. The supervisor knows that stopping production could hurt the department's performance numbers. Does the management system support stopping to investigate, or does the employee feel pressure to keep production moving and hope the defect doesn't become a customer problem?

A quality policy probably says the organization prioritizes quality. Most do. But what do leaders actually reward? What gets discussed in performance reviews, and how do managers react when employees identify problems that threaten delivery targets? These questions can't be answered by reading a policy. They require examining actual decisions and behavior.

The same tensions arise in healthcare, where staff might recognize a safety concern but feel pressure to maintain patient throughput. A strong quality culture requires leaders to manage these competing priorities. It doesn't make the trade-offs disappear.

Are Employees Improving the Work, or Just Following Procedures?

Standardized work and process discipline are essential to quality management. But standardization shouldn't mean employees are expected to follow procedures without questioning whether they could be improved. The people doing the work often recognize problems and opportunities that aren't immediately visible to management.

Maybe a procedure includes an unnecessary step. Maybe equipment could be arranged differently to reduce errors, or a handoff between departments repeatedly creates delays. An effective continuous improvement system gives employees a way to identify these opportunities, participate in testing changes, and help develop improved standards.

I'd look for evidence that employees across different roles, shifts, and departments are participating. But I'd be careful about how that participation is measured. A high number of submitted suggestions doesn't necessarily indicate a strong improvement culture. Some organizations establish idea quotas that encourage employees to submit suggestions simply to meet a requirement.

Likewise, low participation in one department doesn't necessarily mean employees don't care. Perhaps they don't have time, supervisors aren't responding, or the improvement process creates more work than it removes. Instead of simply ranking departments by their number of suggestions, I'd want to understand the conditions that make participation easier or harder.

The revised standard's clearer emphasis on opportunities is relevant here, too. Employees shouldn't have to wait for a defect, customer complaint, or audit finding before suggesting an improvement. A process might meet all its quality requirements while still containing unnecessary work or opportunities to make the job safer and easier.

Are Improvements Producing Better Results?

Another useful test of quality culture is what happens after an improvement is marked complete. Organizations often track activity: projects completed, corrective actions closed, employees trained, or Kaizen events conducted. Those measures have their place, but completed activity isn't the same as improved performance.

If a team changes a process to reduce errors, what happened to the error rate? If employees redesign a workflow to shorten turnaround time, did the time actually decrease? And did the improvement last? Ideally, teams establish a baseline before making changes and continue measuring afterward. They should understand normal process variation so they don't mistake every favorable data point for evidence of improvement.

Sometimes a countermeasure doesn't work as expected. That's useful information, especially if the organization learns from the result and adjusts its approach. A quality culture should support learning from unsuccessful experiments rather than encouraging teams to declare success prematurely. I'd be concerned if nearly every reported improvement was described as successful without evidence to support those claims.

Try Following Three Actual Improvement Opportunities

Here's a practical exercise for a leadership team or quality management review. Choose three examples from recent months: a quality problem that was successfully resolved, an improvement opportunity that's still in progress or encountering obstacles, and a concern or suggestion that the organization decided not to act on.

For each example, examine the history from the employee's initial observation through the management response and subsequent decisions. Who raised the issue? What happened next? Who was involved in deciding what to do, and what support was provided? How was the decision communicated, and what evidence shows whether the outcome was effective?

For the rejected or deferred suggestion, pay particular attention to whether the employee received an explanation. A respectful response doesn't always mean saying yes, but employees should understand why a decision was made. An explanation also creates an opportunity for employees to share information management might have overlooked.

I'd recommend talking directly with the people involved rather than relying entirely on records or dashboards. The documentation might tell you that a concern was closed, while the employee might tell you that the underlying problem continues. That's worth investigating. A closed record doesn't necessarily mean a resolved problem.

This exercise isn't a specific ISO 9001:2026 audit requirement. It's a practical way for leaders to examine how their quality management system functions, including how it handles situations that don't go according to plan.

Quality Culture Is Built Between Audits

The revised ISO standard gives organizations another reason to look beyond policies and procedures. But the benefits of a strong quality culture aren't limited to certified organizations. Every organization needs people who recognize problems, feel comfortable raising concerns, participate in improvement, and receive support from their leaders.

Improvement management systems can help by making problems visible, tracking decisions, clarifying ownership, and documenting results. KaiNexus customers use digital improvement systems to support these activities. Other organizations use huddle boards, spreadsheets, and other approaches. Whatever tools you use, their effectiveness depends on the management practices around them.

A system can show that an employee raised a concern, but it can't guarantee that a supervisor responds constructively. A dashboard can show that an improvement was completed without proving that performance improved. These are reasons to examine how the tools are being used, rather than assuming that adopting them demonstrates a strong culture.

Rather than asking only whether employees know the organization's quality policy, I'd encourage leaders to ask what employees experience when they identify a problem or suggest an improvement. Then look at what actually happened. That's where I'd start assessing the quality culture.