In the previous articles, I examined several limits of measurement: the difference between data and knowledge, the effects of excessive measurement, and the existence of latent quality beyond formal observation.

These arguments lead to a more fundamental distinction:

Measured quality and known quality are not the same state of quality.

In the Quality Knownness framework, quality can be considered not only by its actual condition, but also by its epistemic status: how far the organization has progressed in making that quality sufficiently identifiable, evidenced, interpreted, and established as a basis for management.

Measurement is therefore an important transition, but not the final one.

Measured Quality

Measured quality exists when relevant characteristics of a process, product, or outcome are represented through observable evidence.

At this stage, something about quality has become empirically accessible.

But measurability tells us primarily that a phenomenon can be observed and represented. It does not yet tell us what that phenomenon means.

A measured deviation may be real while its significance remains uncertain. The same observed change can point to different underlying conditions depending on process configuration, timing, dependencies, or changes in the operating environment.

Measurement establishes evidence.

It does not automatically establish knowledge.

Known Quality

Within the Quality Knownness framework:

Known quality is a state in which available evidence has been sufficiently identified, interpreted, and connected with the functioning of the process to provide a justified basis for managerial judgement.

This does not imply complete knowledge.

Complete knowledge is rarely possible in organizational systems.

Knownness is better understood as the degree to which the condition of quality has become sufficiently established and interpretable for management to make a reasoned judgement about it.

The transition from measured to known quality is therefore an epistemic transition.

The question changes from:

Can this quality characteristic be observed and represented?

to:

What can the organization legitimately conclude about the state of quality from what it has established?

That distinction is central to Quality Knownness.

What Makes Quality Known?

Evidence alone is insufficient because measured characteristics do not possess managerial meaning independently of the system in which they occur.

They require interpretation.

Interpretation connects empirical evidence with an explanation of what the observed condition may represent.

But interpretation itself is not enough if it remains individual, unstable, or disconnected from the wider organizational understanding of the process.

For quality to become known at the organizational level, that understanding must become sufficiently robust to be retained, communicated, challenged, and used beyond a single observation or a single expert judgement.

This introduces another important element of Quality Knownness: institutionalization.

A quality condition is not fully known organizationally simply because one specialist understands it.

The organization must be capable of preserving and using that understanding.

Measurability is Not Knownness

This distinction explains why measurability and knownness should not be treated as the same dimension.

An organization can have high measurability and relatively low knownness.

It may observe many characteristics of a process without developing a coherent understanding of what they collectively say about quality.

The opposite is also possible.

Some characteristics may have low formal measurability but relatively high knownness because experienced specialists understand recurring patterns, process dependencies, or weak signals that have not yet been fully formalized.

In the broader Quality Knownness model, these are different properties:

M — Measurability: the extent to which quality can be empirically observed and represented.

K — Knownness: the extent to which quality has become identified, evidenced, interpreted, and sufficiently established for managerial judgement.

A movement from M > 0, K ≈ 0 toward M > 0, K > 0 is therefore not simply an increase in information.

It is a change in the status of quality as an object of management.

Why the Distinction Matters

Most quality-management methods require some prior degree of knownness about what is being analysed, controlled, or improved.

  • Statistical Process Control helps identify patterns in process behaviour.
  • Root Cause Analysis structures the search for causes.
  • FMEA supports the analysis of potential failures and their effects.
  • Six Sigma provides methods for reducing variation and improving process performance.

These methods do not become unnecessary within the Quality Knownness framework.

The distinction is different.

Quality Knownness examines the epistemic condition in which such methods are being applied.

It asks:

How well is this quality actually known before we decide how to manage it?

This matters because the choice of what to analyse, what to control, what to improve, and even what to leave unchanged depends on the quality of the underlying organizational understanding.

That is why the transition from measured quality to known quality is important.

Measurement makes quality empirically accessible.

Knownness makes it managerially intelligible.

The issue is therefore not whether organizations should measure more or less.

It is whether what has been measured has become sufficiently understood and established to become known quality.

In the next article, I will move from this transition to the structure of Quality Knownness itself and examine the four basic states of quality: Potential, Measured, Known, and Managed. Together, they describe how the status of quality changes as an organization moves from possibility to evidence, from evidence to knowledge, and from knowledge to action.