Most organisations working on change management and quality management introduce new procedures with the best of intentions. The procedures are well thought through, the documentation is in place, and the quality management system is accessible to everyone. Yet nothing changes. People carry on as before. The change quietly dies out, and after a while no one remembers that things were supposed to be different.
This is not a technical problem. It is a problem of change management in quality management — and it is far more common than most are willing to admit.
Why change management fails in quality management
The problem does not start with resistance to change
It is tempting to explain failed changes through resistance. Employees don’t want to change. They’re used to doing things their way. They don’t understand the importance of the quality management system.
But resistance is rarely the cause. It is the symptom.
When people don’t follow new procedures, it is most often because they never understood why the change was introduced. No one explained the connection. No one showed what would actually improve. The change arrived as a top-down directive — a new document in the quality management system, an email saying ‘from Monday, the following applies’ — and then it was up to each individual to find the meaning themselves.
It is rarely the employees who fail. It is the process surrounding the change that fails.
When change management stalls between leadership and practice
Why middle managers are critical in quality management
One of the most recognisable situations in larger organisations is the change that appears to succeed on the surface, but never quite reaches the front line. Leadership has decided. The quality manager has documented. The system is updated. And then, three months later, people on the floor are still working as before.
The reason is almost always the same: middle managers were not brought along.
Middle managers are the link between decision and practice. If they do not understand the change, have not had the time to communicate it, or are themselves uncertain whether it is right, they will not convey it with credibility. And employees follow their immediate manager, not a document in a quality management system.
John Kotter highlights precisely this in his work on change management: changes do not fail because they are poor, but because organisations skip the critical steps of building buy-in and communicating meaning. A decision is not the same as an implementation. A procedure is not the same as a practice.
Why documentation alone does not succeed in quality management
Documentation does not solve a buy-in problem
Here is an uncomfortable truth for many working in quality management: a well-documented system can actually make the problem worse.
Once the documentation is in place, it is easy to assume the job is done. The system is updated. The procedure has been approved and published. Employees have access. But that does not mean the system is being used.
The ADKAR model, developed by Prosci, describes five prerequisites for change to actually happen at the individual level: awareness, desire, knowledge, ability and reinforcement.
Most organisations focus almost exclusively on knowledge — that is, what employees should do. But if awareness and desire are not in place, knowledge will not lead to changed behaviour. People know what they should do, but do not do it.
When quality management is experienced as bureaucracy
Much of the resistance to quality management systems is not about laziness or reluctance. It is about perceived value.
When employees feel that quality management is primarily there to satisfy the auditor, to document for documentation’s sake, or to protect management, they will respond accordingly. They do what is required — nothing more.
This is not a problem with the employees. It is a sign that the quality management system is not embedded in everyday working life.
A quality management system that works in practice is characterised by the fact that it genuinely helps people in their work. The procedures are written for the user. The non-conformity system solves real problems. Management uses the system actively — not only at audit time.
When employees see that the system works, attitudes shift. Not because they are persuaded, but because they experience value.
The role of leadership in change management and quality management
Change management in quality management cannot be delegated away. It is not a project — it is an ongoing leadership responsibility.
Leaders who succeed in embedding quality management systems do certain things consistently. They use the system themselves. They refer to it in decisions. They follow up on non-conformities and improvements. And they give middle managers both the time and the responsibility to drive the change forward.
When leadership treats the quality management system as an administrative requirement, the rest of the organisation will do the same. When it is treated as a management tool, the way it is used changes too.
What distinguishes successful from unsuccessful change management in practice
The difference rarely lies in the system — but in how it is introduced and followed up.
An organisation introduces a new non-conformity system. An email is sent out with a link to the procedure. Two weeks later, three non-conformities have been logged, all from the same department. Six months later, the system has effectively been abandoned.
Another organisation introduces the same system. Middle managers are involved early. The first non-conformities are followed up promptly. Results are communicated back. Leadership uses the data actively in meetings. After a few months, the system is in use across the organisation.
The same system. Completely different outcomes. The difference is not the technology or the documentation. The difference is the change management surrounding the quality management.
Marte Sunde
Businesss Consultant