Implementing a Quality Management System Without Trying to Fix Everything at Once

Dr Tendai Pfidze

21 August 2026

Implementing a Quality Management System (QMS) can seem daunting, especially in a medium-sized or large organization. There may be hundreds of processes, numerous departments, existing policies, and a long list of problems that could potentially be addressed.

This can create the impression that implementing a QMS means documenting everything from the beginning: mapping every process, writing every SOP, defining every indicator and fixing every problem.

A more practical approach is to build the QMS around what the organization is trying to achieve, the risks that could prevent it from getting there, and a continuous cycle of improvement.

Rather than trying to perfect the entire organization at once, the organization can establish the foundations of its QMS and progressively improve priority areas through successive Plan-Do-Check-Act (PDCA) cycles.

This is consistent with ISO 9001:2015, which emphasizes the process approach, PDCA and risk-based thinking as interconnected concepts within a quality management system (International Organization for Standardization [ISO], 2015).

Start With the Organization, Not the SOPs

Before asking what procedures do we need?, a better question is:

What is this organization trying to achieve?

Quality management should support organizational strategy, not exist as a separate administrative system.

The organization first needs to understand its context: its customers, stakeholders, internal strengths and weaknesses, external environment, regulatory requirements and other factors that may affect its success. A SWOT analysis is one possible tool for doing this.

From this understanding, leadership can determine organizational objectives.

These might include reducing customer complaints, improving patient safety, increasing productivity, reducing operating costs, improving delivery reliability or improving customer retention.

These objectives give quality improvement a purpose.

This broadly reflects the structure of ISO 9001:2015, which addresses the context of the organization in Clause 4, leadership in Clause 5 and planning in Clause 6.

Move From Objectives to Risks

Once the objectives are understood, the next question is:

What could prevent us from achieving them?

This introduces risk-based thinking.

Suppose a healthcare organization's objective is to reduce preventable maternal mortality. Potential risks could include delayed recognition of deteriorating patients, inadequate emergency blood availability, delayed escalation, medicine shortages or inadequate staff competencies.

The organization may not be able to tackle all these issues at once.

Risk assessment therefore helps prioritize what needs attention first. High-priority risks can then inform the first set of QMS objectives.

The logic becomes:

This creates a clear line of sight between operational quality-improvement work and what genuinely matters to the organization.

You Do Not Have to Fix Everything in the First Cycle

This is where PDCA becomes especially useful.

Instead of trying to redesign every process simultaneously, the organization can select a manageable number of high-priority areas for the first cycle.

Perhaps there are four major risks that need immediate attention.

Then another cycle begins.

ISO guidance recognizes that PDCA can be applied to individual processes as well as the management system as a whole (ISO, 2015).

This means QMS implementation itself can be iterative. The organization establishes the necessary foundations while progressively improving and controlling more of its processes over time.

Avoid Random Quality Improvement Projects

One danger in quality management is activity without strategic relevance.

Organizations can easily accumulate improvement projects because they are visible or easy to implement: a 5S exercise here, an SOP rewrite there, a few new indicators somewhere else.

Each activity may have value, but the important question is:

Why are we doing this?

Quality initiatives should ultimately relate to organizational risks, customer requirements, strategic objectives or identified opportunities for improvement.

Research among Indian SMEs supports this broader view. Bagodi et al. (2021) identified employee, process, customer and financial performance as interconnected dimensions of business performance, with employee factors having important effects on processes and customer outcomes.

The same study found that organizations may know individual quality tools without having strong quality-management capability. Some firms failed to recognize the long-term opportunity losses associated with weak QMS implementation, while resource constraints and overdependence on a few managers also limited implementation.

This highlights an important distinction:

Using quality tools is not the same as having a functioning quality management system.

A QMS Is Not a Documentation Competition

Another common mistake is allowing the QMS to become mainly a documentation exercise.

The question gradually changes from:

Are our processes producing the results we need?

to:

Do we have a procedure for this?

Documentation is important. SOPs, work instructions and controlled information can reduce variability and improve consistency.

But documentation is a means, not the ultimate purpose of quality management.

Neighbors (2026) found that standardization and controlled documentation were important in QMS implementation, but effective implementation required more than documents. Leadership, governance, employee involvement and continual improvement were also necessary.

The better question is therefore:

Does this process require documented information to ensure that it is consistently understood, executed and controlled?

Sometimes the answer is yes.

But documenting a poor process simply gives you a well-documented poor process.

Quality Management Must Be Top-Down and Bottom-Up

Quality management cannot be purely top-down.

Leadership must establish direction, communicate priorities, allocate resources and create an environment where improvement is possible.

Neighbors (2026) identified five important strategies associated with successful QMS implementation: leadership commitment, communication, standardization, employee involvement and data-driven decision-making.

Leadership therefore needs to do more than say that quality is important.

It must make quality possible.

That includes providing equipment, training, information, authority and, importantly, time.

Employees cannot reasonably be expected to run improvement projects while carrying the same workload and receiving no additional support.

Research in a South African educational setting similarly highlighted time, administrative burden, training and access to resources as important QMS implementation issues.

Resources therefore include more than money. They include time, competence, information, equipment and leadership support.

At the same time, improvement cannot come only from management.

The people performing day-to-day work often understand operational problems best. They see delays, rework, equipment failures, duplicate forms, customer complaints and policies that do not work well in practice.

These employees should therefore understand basic quality-management principles and be empowered to participate in improving their own processes.

Neighbors (2026) found that involving employees in problem-solving, audits and quality initiatives increased ownership and adherence to QMS requirements.

Ratter (2025) similarly emphasizes that continual improvement requires employee participation.

A useful division of responsibility is therefore:

Measure What Matters

Improvement also requires evidence.

If an organization claims that a process has improved, it should be able to demonstrate what changed.

This does not mean measuring everything.

Measures should show whether the intervention is moving the organization toward the objective that justified the work in the first place.

Bagodi et al. (2021) argue that organizational performance should not be judged using financial measures alone. Process, employee and customer indicators are also important.

This matters because financial results are often lagging indicators.

A quality intervention may first lead to fewer defects, shorter waiting times, better employee performance or fewer customer complaints before financial results become visible.

ISO 9001:2015 therefore includes monitoring, measurement, analysis, evaluation, internal audit and management review before its requirements on improvement.

Then Begin the Next Cycle

After completing the first set of improvement initiatives, the organization should ask:

That becomes the next PDCA cycle.

Over time, the organization expands from a manageable number of high-priority areas toward a broader and more mature management system.

The organization is not trying to become perfect in one project.

It is building the capability to repeatedly identify what matters, understand what threatens it, improve the relevant processes, learn from the results and do it again.

The QMS Is Not the Goal

Perhaps the most important point is that the QMS itself is not the ultimate objective.

Bandlerová et al. (2025) make this distinction clearly in their study of public administration: the QMS is not the ultimate goal; the real goal is the quality of organizational outputs, services and stakeholder satisfaction.

A hospital does not exist to produce excellent QMS documentation. It exists to provide safe, effective healthcare.

A school does not exist to complete quality forms. It exists to educate.

A manufacturer does not exist to pass audits. It exists to reliably create products customers value.

The system exists to help the organization perform better.

That is why QMS implementation should begin with organizational objectives, move through risks and priorities, translate those priorities into process-level improvements, empower employees, measure results and continually repeat the cycle.

Perhaps the most practical way to implement a system built around PDCA is to use PDCA to implement the system itself.

That is how a QMS stops being a collection of documents and becomes part of how the organization is managed.

References