Following Russell Ackoff, systems thinkers like to equate wisdom with systems thinking. As Nikhil Sharma points out,
"the choice between Information and Knowledge is based on what the particular profession believes to be manageable".
When this is described as a hierarchy, this is essentially a status ranking. Wisdom (which is what I happen to have) is clearly superior to mere knowledge (which is what the rest of you might have, if you're lucky).
Here's an analogy for the so-called hierarchy of Data, Information, Knowledge and Wisdom (DIKW).
- Data = Flour
- Information = Bread
- Knowledge = A Recipe for Bread-and-Butter Pudding
- Wisdom = Only Eating A Small Portion
Note that Information isn't made solely from Data, Knowledge isn't made solely from Information, and Wisdom isn't made solely from Knowledge. See also my post on the Wisdom of the Tomato.
That's enough analogies. Let me now explain what I think is wrong with this so-called hierarchy.
Firstly, the term
hierarchyseems to imply that there are three similar relationships.
- between Data and Information
- between Information and Knowledge
- and between Knowledge and Wisdom
- Data before Information
- Information before Knowledge
- Knowledge before Wisdom
- Much more data than information
- Much more information than knowledge
- Tiny amounts of wisdom
But my objection to DIKW is not just that it isn't a valid hierarchy or pyramid, but it isn't even a valid schema. It encourages people to regard Data-Information-Knowledge-Wisdom as a fairly rigid classification scheme, and to enter into debates as to whether something counts as
knowledge. For example, people often argue that something only counts as
knowledge if it is in someone's head. I regard these debates as unhelpful and unproductive.
knowledge is the means by which we create information out of data. Meanwhile Tom Graves suggests we regard DIKW not as layers but as distinct dimensions in a concept-space.
But merely rearranging DIKW fails to address the most fundamental difficulty of DIKW, which is a naive epistemology that has been discredited since the Enlightenment. You don't simply build knowledge out of data. Knowledge develops through Judgement (Kant), Circular Epistemology and Dialectic (Hegel), Assimilation and Accommodation (Piaget), Conjecture and Refutation (Popper), Proof and Refutation (Lakatos), Languaging and Orientation (Maturana), and/or Mind (Bateson).
These thinkers share two things: firstly the rejection of the Aristotelian idea of
one-way traffic from data to knowledge, and secondly an insistence that data must be framed by knowledge. Thus we may validate knowledge by appealing to empirical evidence (data), but we only pick up data in the first place in accordance with our preconceptions and observation practices (knowledge). Meanwhile John Durham Peters suggests that
knowledge is not the gathering but the throwing away of information. Marvellous Clouds, p 318
Among other things, this explains why organizations struggle to accommodate (and respond effectively to) weak signals, and why they persistently fail to
connect the dots.
And if architects and engineers persist in trying to build information systems and knowledge management systems according to the DIKW schema, they will continue to fall short of supporting organizational intelligence properly.
For a longer and more thorough critique, see Ivo Velitchkov, Do We Still Worship The Knowledge Pyramid (May 2017)
Many other critiques are available ...
Gene Bellinger, Durval Castro and Anthony Mills, Data, Information, Knowledge, and Wisdom (Systems Thinking Wiki, 2004)
Tom Graves, Rethinking the DIKW Hierarchy (Nov 2012)
Patrick Lambe, From Data With Love (Feb 2010)
Nikhil Sharma, The Origins of the DIKW Hierarchy (23 Feb 2005)
Kathy Sierras, Moving up the wisdom hierarchy (23 April 2006)
Dave Snowden, Sense-making and Path-finding (March 2007)
Gordon Vala-Webb, The DIKW Pyramid Must Die (KM World, Oct 2012) - as reported by V Mary Abraham
David Weinberger, The Problem with the Data-Information-Knowledge-Wisdom Hierarchy (HBR, 2 February 2020)
DIKW Model (KM4dev Wiki)
Related posts: Connecting the Dots (January 2010), Too Much Information (April 2010), Seeing is not observing (November 2012), Big Data and Organizational Intelligence (November 2018), An Alternative to the DIKW Pyramid (February 2020)
Updated 8 December 2012
More links added 01 March 2020
Also merging in some material originally written in May 2006.
Glad you dislike DIKW too. I liken the distinction to the distinction between different kinds of mechanical parts/systems:ReplyDelete
data: "atomic" parts, eg nuts, bolts, pipes, rails
information: complex parts, eg, hinges, pulleys, motors, engines
knowledge: complete mechanisms, eg, bicycles, cars, ovens, refrigerators
wisdom: complete systems, eg roads+gas stations+cars+repair shops
The boundaries among levels of aggregation and composition of mechanical systems are just as vague as those between DIKW.
They also beg the question, "What useful work do such distinctions accomplish?" IMO, neither set of distinctions does any useful work.