DIKW hierarchy
How raw data becomes information, knowledge, and wisdom, why the model has practical limits, and how to apply it in business intelligence contexts.
By the end of this module you will be able to:
- Apply the DIKW model to classify a real dataset scenario correctly
- Identify at least one substantive critique of the DIKW hierarchy
- Trace a business intelligence example through all four DIKW levels
Think about it
An airline holds 300 million flight records but cannot predict when a specific passenger will miss a connection — without the full DIKW chain.
A major European carrier collects over 300 million flight event records per year: departure times, gate changes, aircraft swaps, weather diversions, and fuel loads. At the data level, it has extraordinary coverage. Yet when a connecting passenger misses their onward flight due to a late inbound aircraft, the airline's ground crew often has no system-generated prompt to rebook them proactively. The data existed. The information was never assembled.
To predict a connection miss, the data layer must be transformed into information: this passenger, on this booking, connecting at this hub, with this inbound delay, has a 12-minute connection window against a 35-minute minimum. Knowledge adds the pattern: connection windows under 20 minutes at this hub have a 78% miss rate in wet weather. Wisdom applies judgement: rebook the passenger now, before the inbound lands, factoring in their status tier, the next available seat, and their final destination.
Each level in the DIKW hierarchy requires deliberate investment. Data systems are built routinely. The steps from data to wisdom are where airlines, hospitals, and governments consistently underinvest.
The DIKW pyramid and its four levels
The DIKW (Data, Information, Knowledge, Wisdom) model is the most widely cited framework for understanding the relationship between raw observations and actionable understanding. Russell Ackoff formalised it in 1989 in the Journal of Applied Systems Analysis. It arranges four concepts in a pyramid: data at the base, wisdom at the apex. Each level is created by processing or interpreting the level below it.
- Data is the raw layer. A blood pressure reading of 145 is a number. It has no clinical meaning without context.
- Information is the contextualised layer. "Patient Jane Smith, aged 62, recorded a systolic blood pressure of 145 mmHg at 09:15 on 3 June 2024, compared with her baseline of 128 mmHg" is information. It answers "what happened and to whom?"
- Knowledge is the interpretive layer. "A sustained systolic reading of 145 mmHg in a patient with this profile exceeds the NICE threshold for hypertension management review" is knowledge. It requires clinical rules, guidelines, and pattern recognition applied to information.
- Wisdom is the action layer. A GP weighing the reading, the patient's history, current medications, and patient preferences, and deciding to adjust treatment rather than wait, is exercising wisdom. It requires judgement, ethics, and context beyond the information alone.
With an understanding of the dikw pyramid and its four levels in place, the discussion can now turn to applying dikw in business intelligence, which builds directly on these foundations.
Applying DIKW in business intelligence
Business intelligence teams often use the DIKW hierarchy to communicate what their systems produce. A raw database export of transaction records is data. A dashboard aggregating those transactions into weekly revenue by region is information. A report identifying that the north-west region consistently underperforms on Tuesdays due to delivery scheduling is knowledge. An executive decision to change the Tuesday logistics contract is wisdom.
The DIKW model is descriptive, not a process model. It describes relationships between concepts; it does not specify how data becomes information in practice. Treating it as a workflow ("first collect data, then produce information, then extract knowledge") oversimplifies how analytical work actually happens. Discovery of knowledge often drives requirements for additional data collection; causality runs in both directions.
With an understanding of applying dikw in business intelligence in place, the discussion can now turn to critiques of dikw, which builds directly on these foundations.
“The DIKW hierarchy describes relationships between concepts, not a production process. The boundaries between levels are not sharp, and the transitions require human or computational effort that the model does not specify.”
Ackoff, R.L. (1989). From data to wisdom. Journal of Applied Systems Analysis, 16 - Section 2
“Where is the wisdom we have lost in knowledge? Where is the knowledge we have lost in information?”
T. S. Eliot, The Rock (1934) - Chorus I
Eliot anticipated the central challenge of the DIKW hierarchy decades before the information age: accumulating more data does not automatically produce understanding. Each level requires deliberate human effort to transform.
Critiques of DIKW
The DIKW model is influential but not unchallenged. Martin Frické published a rigorous critique in 2009 in the Journal of Information Science:
- The hierarchy is not clearly defined. The boundary between information and knowledge is fuzzy. Different authors draw it in different places.
- Wisdom is difficult to operationalise. It is a human capacity, not a data artefact. Including it in a data hierarchy risks conflating human cognition with information system design.
- The pyramid implies a linear flow. In practice, knowledge gaps often drive targeted data collection. A research team's prior knowledge determines which data is worth collecting at all.
- Data is not value-neutral. The model implies that data is objective and raw. But what is recorded, how it is labelled, and what is omitted are all choices shaped by values and assumptions.
Frické's critique has practical utility: start with the knowledge questions you need to answer, then identify what data is required to answer them. Don't build a data warehouse first and expect useful knowledge to emerge from it.
Common misconception
“Collecting more data first and analysing it later is the right approach to building knowledge.”
This 'data warehouse first, analysis later' approach assumes data has inherent value independent of use. Frické's 2009 critique is directly relevant: knowledge gaps should drive data collection, not the other way around. Data that is never contextualised or queried is simply a storage cost. Before collecting data, ask: what knowledge questions need to be answered? What information is needed to answer them? What data must be collected to produce that information? Working from the top of the pyramid down is more efficient than collecting from the bottom up.
A retailer has a database of 200 million purchase transactions spanning five years. A new analyst runs a query showing average spend per customer per month. A senior manager then uses that figure to decide whether to launch a loyalty programme. Map these four elements to the correct DIKW levels.
Key takeaways
- The DIKW hierarchy (Data, Information, Knowledge, Wisdom) describes how raw observations become actionable understanding through context, interpretation, and judgement. Ackoff formalised it in 1989.
- Each DIKW level requires active effort: context produces information, analysis produces knowledge, and situational judgement produces wisdom. The transitions are not automatic.
- The hierarchy has real limits (Frické, 2009): it implies linear flow that does not match analytical practice, and the boundary between levels is not precise. Wisdom cannot be stored or processed by machines.
- Practically: start with the knowledge questions you need to answer, then work down to identify what information and data are required. Building data warehouses without clear knowledge questions produces storage cost, not insight.
With the DIKW model as a thinking tool, you can trace how meaning builds from raw observations. The next module drops to the physical layer: how computers represent data as bits, bytes, and binary numbers. Understanding binary and units removes a common source of data engineering errors.
Standards and sources cited in this module
Ackoff, R.L. (1989). From data to wisdom. Journal of Applied Systems Analysis, 16
Original formulation of the DIKW hierarchy and its four levels.
Frické, M. (2009). The knowledge pyramid: a critique. Journal of Information Science
Rigorous academic critique: boundary ambiguity, non-linear flow, and the problem of wisdom as a data concept.
ISO/IEC 11179-1:2023: Data element concepts
Formal definitions aligned with DIKW base concepts for data and information.