In the first article of this series, I raised a simple question:
If an organization measures quality, does it necessarily know its quality?
The answer is not as obvious as it may seem.
A measurement gives us a representation of what is happening in a process. But before that representation can influence the process, it must pass through several stages.
⬇︎ Something happens.
⬇︎ It becomes observable.
⬇︎ An observation is converted into data.
⬇︎ The data is interpreted.
⬇︎ The interpretation is communicated.
⬇︎ A decision is made.
⬇︎ An action is taken.
Only then can the process change.
This chain often appears seamless when it is presented in a dashboard, a report, or a management system. In practice, however, every transition creates a possibility of losing, distorting, or misinterpreting information.
A process event is not yet data
Quality begins with something that happens in a real process.
A material changes its characteristics. Equipment begins to operate differently. A customer encounters a problem. An employee compensates for an unstable procedure. A delay appears between two stages of production.
But not everything that affects quality is automatically observed.
Some changes are too small to be detected by the existing measurement system. Others are noticed by employees but are not recorded. Some are visible only when several events are considered together.
This creates the first gap:
What happens in the process may be broader than what the organization is able to observe.
The absence of a recorded deviation does not always mean that the process is stable. It may simply mean that the relevant change is not currently being captured.
Data is not yet interpretation
Suppose the change is detected and recorded.
A sensor produces a value. A customer submits a complaint. An audit identifies a nonconformity. A dashboard shows that an indicator has moved outside its expected range.
The organization now has data. But the data still requires interpretation.
➥ Is the change significant or temporary?
➥ Is it the result of a local incident or a systemic problem?
➥ Is the indicator showing a cause, a consequence, or only a correlation?
➥ Should the organization react immediately, continue observing, or investigate further?
The same value can lead to different conclusions depending on context, experience, and access to additional information.
This means that interpretation is not simply an automatic property of data. It is an organizational activity.
Interpretation is not yet shared understanding
A specialist may understand what the data means.
An experienced operator may recognize a familiar pattern. An engineer may connect the deviation with an earlier change in equipment settings. A quality manager may identify a recurring issue across several reports.
But individual understanding does not automatically become organizational understanding.
➡︎ The explanation may remain within one department.
➡︎ It may be communicated in technical language that decision-makers interpret differently.
➡︎ It may contradict an existing KPI or an accepted management narrative.
➡︎ It may arrive too late.
➡︎ Or it may simply never reach the person who has the authority to act.
This is a critical point.
An organization may possess the required knowledge somewhere within its structure and still fail to use it.
In such cases, the problem is not necessarily a lack of expertise. It is the inability to connect distributed expertise with the decision-making process.
A decision is not yet an effective action
Even when the problem is understood, the next step is not automatic.
Management may approve a corrective action, change a procedure, introduce an additional control, retrain employees, replace a supplier, or modify equipment settings.
➥ But does the action address the underlying cause?
➥ Or does it only improve the visible indicator?
A company may reduce the number of reported defects by changing inspection rules. It may improve delivery statistics by redefining the starting point of measurement. It may decrease the number of complaints without removing the customer problem.
➥ The reported result improves.
➥. The underlying quality may not.
This is why an action cannot be evaluated only by whether the indicator moves in the desired direction. It must also be connected back to the actual state of the process.
Where does the chain break?
The distance between measurement and management is therefore not one single gap.
It consists of several possible breaks:
- a relevant process event is not observed;
- an observation is not recorded correctly;
- the data is interpreted without sufficient context;
- expert understanding is not shared;
- information does not reach the appropriate decision-maker;
- the selected action does not address the real cause;
- the outcome is evaluated through an indicator that no longer represents the process accurately.
Any one of these breaks may prevent the organization from moving from visibility to control.
And the more complex the business system becomes, the more difficult it is to assume that this chain will work automatically.
➡︎ More sensors do not solve communication problems.
➡︎ More dashboards do not guarantee correct interpretation.
➡︎ More analytics do not ensure that a decision will be made.
➡︎ And more corrective actions do not necessarily mean that the process is becoming more manageable.
The overlooked part of quality management
Quality management often focuses on the beginning and the end of this chain.
At the beginning, organizations invest in measurement: indicators, data collection, monitoring, audits, and analytical systems.
At the end, they focus on action: corrective measures, improvement projects, process changes, and management decisions.
But what happens between these two points may be equally important.
➥ How does an observation become meaningful?
➥ How does an individual interpretation become shared organizational knowledge?
➥ How does that knowledge become a justified decision?
➥ And how does the organization determine whether the decision changed the real quality of the process?
These questions suggest that the effectiveness of quality management depends not only on the ability to measure and act.
It also depends on the organization’s ability to preserve meaning as information moves through the system.
Perhaps the main challenge is not simply to collect more data or make decisions faster.
Perhaps it is to ensure that what happens in the process can be observed, correctly interpreted, shared, and transformed into an action that actually affects quality.
Because between measurement and management, information must become understanding.
And understanding must become action.