Most organizations today measure quality through a growing set of indicators: defects, complaints, deviations, delivery times, process stability, customer satisfaction, audit findings, equipment failures, and many others.

The logic appears obvious:

  • If quality is measured, it becomes visible.
  • If it is visible, it can be understood.
  • If it is understood, it can be managed.

But is this sequence always true?

Consider a simple example.

A company reports that its defect rate increased from 2.8% to 3.7%.

  • The data exists.
  • The dashboard has been updated.
  • The deviation is visible.

But what exactly does the organization know?

It knows that the indicator has changed. But does it know why the defect rate increased? Does it know whether the increase is caused by one recurring problem or several unrelated factors? Does it know whether the source is equipment, materials, process design, employee actions, workload, supplier variation, or something else?

The number tells us that something has changed.

But the number itself does not explain what happened.

Visibility is not the same as understanding

Modern organizations have become increasingly capable of making processes visible. Sensors collect data continuously, dashboards present performance in real time, business intelligence systems combine information from different sources, and analytical tools identify anomalies, patterns, and correlations.

AI systems can even generate explanations and recommendations.

This creates an impressive level of visibility.

But visibility and understanding are not necessarily the same thing.

An organization may know that defects increased, customer satisfaction declined, delivery times became longer, or equipment downtime is growing. Yet it may still not know why these changes are happening, which interpretation should be trusted, or what decision should follow.

This creates an important distinction:

Having data about quality is not necessarily the same as knowing quality.

The same data, different levels of understanding

Imagine two companies with almost identical quality dashboards.

They measure similar indicators, use similar software, and receive similar reports. Both can see that a certain process is deteriorating.

But their responses are very different.

The first company quickly connects the data with operational knowledge, identifies the cause, and adjusts the process.

The second company holds meetings, requests additional reports, adds new indicators, and launches corrective initiatives — but still struggles to understand what is actually happening.

  • Both companies have data.
  • Both can see the problem.
  • But they do not know the problem equally well.

The difference may lie not in the amount of information available, but in the organization’s ability to interpret what it sees.

More measurement does not automatically mean more knowledge

This is not an argument against measurement.

Measurement is essential.

But perhaps we have become too comfortable with the assumption that once something is measured, it is already known.

It may not be.

A process can be visible without being understood. A problem can appear on a dashboard without becoming clear to the organization. And a company can accumulate more and more quality data while still remaining uncertain about the quality itself.

So perhaps the first question should not be:

How much do we measure?

But rather:

When can we say that an organization truly knows its quality?

That is the question I would like to explore in this series.