In 2001, Doug Laney, an analyst at Gartner, wrote a research note titled "3D Data Management: Controlling Data Volume, Velocity, and Variety." The note was internal. It described three dimensions of the growing data management challenge. It was not meant to launch a framework. It launched a framework.
The "three Vs of big data" became the standard vocabulary for describing why data was getting harder to manage. The framework was simple enough to remember, flexible enough to extend. Over the following two decades, practitioners and researchers added more Vs — each naming a specific dimension of the challenge, each adding a word to the vocabulary.
The genius of the Vs is not their precision. It is their utility. They give engineers a shared language for diagnosing why a data project is struggling. Is the volume overwhelming the storage tier? Is the velocity exceeding the pipeline's throughput? Is the variety creating an unmanageable number of pipelines? Is the veracity undermining trust in the numbers? The Vs name the dimensions of difficulty. Naming them is the first step to managing them.
This series explores each V in depth. Each post asks: what does this V mean, why does it matter, what is the engineering constraint it imposes, and how do you respond?
- Data Volume — how much you have, and how much you can afford to keep
- Data Velocity — how fast data arrives, and how fast you must decide
- Data Variety — the diversity of formats, and the cost of integration
- Data Veracity — trustworthiness, and the gap between data and truth
- Data Value — the only V that justifies the platform's existence
- Data Variability — fluctuation over time, and why pipelines break
- Data Visualization — the bridge between data and decision
- Data Viscosity — resistance to movement, and technical debt in the supply chain
- Data Virality — how data usage spreads through people
- Data Volatility — the half-life of data value
The Vs are not a taxonomy. They are a diagnostic tool. When a data project is struggling, ask: which V is the problem? The answer points to the solution.
Reference: Doug Laney, "3D Data Management: Controlling Data Volume, Velocity, and Variety," Gartner, 2001.