Ariadne – a new chapter for Modell Aachen and orgavision!
Discover Ariadne
Quality management exists in every company, always: Wherever products are created, services are rendered, customer requirements are met, and processes are designed, quality is managed. Consciously or unconsciously, systematically or incidentally.
The difference, therefore, is not whether a company practices quality management – but how quality management is understood, organized, and lived.
In some companies, QM is deeply embedded in the organization; in others, it is primarily visible as a separate department. Still others only consciously perceive quality management when an audit is due, a certificate needs to be renewed, or a problem escalates.
Connected to this is the question of how employees in quality management are positioned: Are they seen as administrators of documents? As a control authority? Or as people who help the company systematically improve quality in daily operations?
Precisely this perception determines what impact quality management can have.
In practice, there are many forms of quality management. Small companies organize QM differently from large organizations, production companies set different priorities than service providers. And the role of the QM department also heavily depends on its maturity level, history, and corporate culture.
Nevertheless, many forms can be broken down into three basic archetypes.
Here, quality management is primarily understood as a necessary duty. The QM department is tasked with displaying certificates, preparing for audits, and maintaining documents for the next inspection.
The management system exists. But it doesn't live.
Typically, quality management operates detached from daily work. Documents are maintained because an audit is due. Processes are described because a standard requires it. Employees view documentation as an annoying extra task – and not as a help for their daily work.
The outcome is clear: The potential of quality management remains untapped.
If QM only surfaces just before an audit, its impact also ceases with the audit. The company meets requirements but doesn't improve systematically. It documents, but it doesn't manage.
Here, the company has understood that quality management can be more than mere compliance. QM should not just document, but also ensure quality. That sounds like progress, and it is.
A problem arises when quality management is held directly responsible for process quality.
Because QM personnel do not carry out most processes themselves. They don't sell, produce, develop, procure, or manage every customer contact. Nevertheless, it is often expected that they ensure process quality, prevent deviations, and drive improvements.
This creates an imbalance.
Departments delegate responsibility. The QM department is supposed to control, monitor, and, if necessary, issue warnings. Quality management becomes the quality police. Instead of working together on better processes, an adversarial dynamic emerges. Here are the people doing the actual work – and there are the QM staff, imposing requirements.
This leads to unrealistic expectations: The QM department is overwhelmed, departments feel scrutinized, and the desired impact is not achieved.
Here, quality management is understood as the targeted management of all activities that contribute to product and process quality – and not as the department that solely generates quality. Responsibility for good processes remains where the processes are carried out: in the departments. The role of QM is to provide guidance, offer methods, and ensure transparency and improvements.
QMRs thus become service providers for employees and managers. They help the company work better. They create structures where knowledge is accessible, processes are understood, and improvement happens systematically, not by chance.
The most important metric then isn't: Audit passed, but: Quality improvement.
And the management system is the most important tool for this.
If a company understands quality management as a quality driver, the next question immediately arises: Which management system supports this role?
Because these can also be interpreted very differently. Some are mere document collections, some ambitious integration projects. And some are actually what they should be: the sum of all a company's operating rules.
Again, three typical forms can be distinguished here.
The initial instinct of many companies is understandable: each specialized topic gets its own system.
Quality management has its QMS, information security its ISMS. Occupational safety, environmental management, data protection, or risk management come with their own structures, documents, responsibilities, and perspectives.
At first glance, this seems orderly. Each topic is clearly defined, each standard has its place.
In practice, however, this creates silos:
· The same content is recorded multiple times.
· Processes are viewed from different perspectives.
· Responsibilities, risks, requirements, and evidence are spread across various systems.
Eventually, no one knows which representation actually describes reality.
This not only weakens the effectiveness of the management system but also the role of QM as a driver of quality. Because anyone who wants to improve quality needs a complete picture. A purely specialized perspective is not enough for this.
The next step is often the call for an Integrated Management System.
Fundamentally correct: specialized systems should not exist in parallel if they already overlap in day-to-day business. Quality management, information security, compliance, risk, and process management often view the same processes from different perspectives.
However, many Integrated Management Systems stop halfway and form a parallel world to the organization. The structure does not follow reality but an artificial order. The documentation is integrated, but not effective. Employees don't relate to it. Managers do not use the system for steering. Processes remain abstract. Although everything is in one system, no real impact is created in daily operations.
An effective management system does not start with specialized systems. It starts with the reality of the company.
It should be the sum of all operating rules by which a company actually operates. Not abstract documentation detached from daily work, but a living representation of the processes in practice.
Processes are the foundation for this.
Because processes are where quality originates. It's where customer requirements are understood, information is processed, decisions are made, risks are managed, and results are generated. The ideal foundation for a management system!
When processes are central, different expert perspectives can be effectively integrated. A process description then not only shows how work is done. It also shows which quality requirements apply, which risks need to be considered, which information security aspects are relevant, which roles are involved, and what documentation is generated.
This creates a unified picture from many individual expert viewpoints.
And this is precisely where impact is created:
· Employees use the management system because it helps them in their daily work.
· Managers use it because it provides guidance.
· QM uses it because improvement becomes visible and manageable.
Companies don't need to reinvent quality management – but they must decide what impact they expect.
True impact, however, only arises when QM empowers the company to systematically improve quality.
This impact is not seen in audits, but in daily operations:
· When employees know how a process works.
· When they understand which rules apply.
· When suggestions for improvement emerge where the work actually happens.
· When risks are not assessed in isolation, but within the context of value creation.
This requires a different understanding of QM: Not bureaucracy or control, but empowerment. Only then does the management system evolve into the tool it should be. Not an audit archive, no parallel world. But the living sum of all the company's operating rules – supported by a management system that is truly integrated, process-oriented, and close to daily operations.
The first step is an honest look at where your company currently stands and how quality management is being used today.
A good first indicator for this: the access figures for your management system – overall and from individual departments. Do employees from sales, development, production, purchasing, service, or administration regularly access processes, guidelines, and rules? Or is the system primarily used by QMs?
If a management system is to help in daily operations, it must also be used in daily operations. Access figures therefore often show very quickly whether the system is part of daily work or merely remains documentation for audits.
Just as important is looking ahead: How do you want to see and use quality management in the future? As a function that secures certificates, as an authority that monitors processes? Or as a driver that helps the company systematically improve quality in everyday operations?
These answers lead to the next step. Check whether your management system truly reflects daily work or if it exists alongsidereality. Look at your processes, not your documents first. And evaluate whether your rules truly help people in their daily work to produce better quality.
This is exactly where we come in:
Ariadne helps companies reposition quality management, align management systems with lived reality, and turn documentation into real impact.
Contact us. Together, we'll find out how your management system can transform from a mandatory exercise into a driver of quality!
Sign in to get in touch with Carsten directly.
We are happy to provide you with inspiring content, current events and news.
