Today I was looking into quantum-related topics in emerging transportation technologies and data analysis, and I came across the word “quantize.” That sent me down a small rabbit hole! I thought I knew what “quantify” is, but “quantize” was less clear, so I paused to sort out the difference.

There is a small distinction in language that becomes important once you start thinking more carefully about data and systems: quantify and quantize sound related, but they describe two very different ideas:

To quantify something is simply to measure it. In engineering, this is something we almost always do. We quantify traffic volumes, speeds, delays, crash frequencies, etc. The question is always about magnitude. How much? How many? Quantification assumes the underlying phenomenon can be measured and expressed as a value.

Quantize is different. It is not about measurement, but about how something exists or how we choose to represent it. In physics, quantization refers to a property of the system itself. Some properties do not change smoothly across a continuous range. Instead, they can only take discrete specific values, like steps on a staircase rather than a ramp. A classic example in physics is the energy of an electron in an atom. The electron cannot have just any energy level; it can only exist at certain energy levels. It does not move smoothly between them. Instead, it transitions between them by absorbing or emitting a specific amount of energy, which corresponds to the gap between levels. This is why those levels are discrete, because only certain values are possible. These possibilities are determined by the system’s governing equations and constraints (for example, solutions to the Schrödinger equation for the atom). The electron moves between these system-defined energy levels in steps.

This is not an idea that was introduced as a modeling convenience, meaning it was not a simplification chosen by scientists to make calculations easier. Instead, it came from experiments that did not match continuous assumptions used in classical physics and forced a different interpretation of how these systems actually behave. In this context, saying something is quantized means the discreteness is built into the system itself, not imposed from the outside. The system naturally operates in fixed increments, even if those increments are very small.

In engineering, the same word is used differently. Here, quantization is something we do. A continuous signal is recorded in discrete steps. For example, time flows continuously, but when we record it in seconds or minutes, we are choosing a resolution and ignoring smaller variations. Speeds can vary continuously as well, but when we round them to whole numbers or bins, we again reduce that continuity into manageable increments. Similarly, analog signals such as voltage or sensor readings are converted into digital values through sampling and quantization, where only certain levels are stored. This is different from both the physical idea of quantization and from quantification. Here, we are not discovering that the signal exists in discrete packets like light (photons). We are not simply measuring it (as in quantification). Instead, we are intentionally converting a continuous signal into a discrete representation so it can be stored, processed, and analyzed. This is not a statement about reality, but about representation. We impose limits on precision to make data usable.

This creates two meanings that are easy to mix. In one case, quantization is a discovered constraint of nature. In the other, it is a practical decision to approximate continuity.

Back to quantification now, before closing this out. Quantifying does not change the structure of what we are observing. It simply assigns a value to it. When we measure speed, volume, or delay, we are trying to record the actual value of something that already exists, as closely as our tools allow. Even when we round or simplify those values, the intent is still to represent magnitude, not to redefine how the system behaves. This is where the difference becomes clearer. Quantification works within a system as it is. Quantization, depending on the context, either describes how the system is fundamentally structured (in physics) or how we choose to represent it (in engineering). The distinction is simple and useful.

Quantify is about measuring. Quantize is about structure or representation.

There you go! I know I will probably need to come back and read this again myself in a few weeks. Not the easiest concept to keep straight.