Back in 1998 Fahey & Prusak produced a list 11 Deadly sins in knowledge management. John Bordeaux in a comment to my earlier post of Knowledge Management and Sin, reminded me and kindly found me an on line list. I've had them in my must blog folder for a bit and started to play with them in preparation for a presentation here in Atlanta yesterday, and for next week when I am teaching a four lecture series to the honors programme in KM at the University of Pretoria. For those interested the outline of the lecture series can be found
here.
It was interesting to go back the best part of a decade and think about the changes which had happened and apply a little bit of retrospective coherence with a dusting of polemic ...
| The Sin | My Commentary |
| Not developing a working definition of knowledge | I'm not at all sure about this one. There has been too time wasted on listservs and in organisations trying to produce a definition when 3000 years of philosophy has not achieved one. I think what we need is to define the difference between what it means to manage knowledge and what it means to manage information. I normally use the example of a taxi driver and map to illustrate the difference. I mean a London taxi driver here, with the knowledge and all that implies. People get that and you can then avoid the K and I words. Instead you simply ask: Is this a problem for a map, or a problem for a taxi driver? Defining knowledge is the sin, not avoiding it |
| Emphasizing knowledge stock to the detriment of knowledge flow | This was prophetic. Everyone had put all their effort into knowledge as a thing; making tacit knowledge explicit. In consequence we have had a decade of pain and it largely hasn't worked. In contrast techniques such as social network stimulation focus on creating connectivity between people to allow knowledge to flow, rather than worrying about the knowledge itself. Get the channels right and that is most of the battle. Generally if people have a working relationship, ideally a trusted one then in the context of need they will help each other without the need for direction, structure or technology. |
| Viewing knowledge as existing predominantly outside the heads of individuals | Yes sort of, right to emphasise the human element, but some people took it too far and said all knowledge was in the heads of individuals when a lot of knowledge only exists as a result of their interaction; it a property of the system rather than an aggregate of individual properties. The emphasis on individuals is also dangerous in KM, it tends to social atomism. Better to think in terms of teams, crews and identity. Concepts that were not advanced in 1998, but these days complexity theory would allow us to change the text of this sin substantially. |
| Not understanding that a fundamental intermediate purpose of managing knowledge is to create shared context | 100% on, knowledge management is about creating shared context so that information can flow. Without shared context there is no information, its all noise. This one deserved a lot more attention than it got |
| Paying little heed to the role and importance of tacit knowledge | Correct in the context of a world divided into tacit and explicit knowledge, but we have moved on from that. It was never a helpful split as it focused on the container rather than the thing contained. An over focus on explicit knowledge continues, but its better to think about experience and narrative, along with content. |
| Disentangling knowledge from its uses | Another 100%, knowledge is all about action, making decisions creating innovative ideas. It is always contextual and is by necessarily entangled and messy |
| Downplaying thinking and reasoning | Yep, and the anti-intellectualism of many a company continues to be a problem. In a modern changing world we need sophisticated executives, able to handle a concept, test a theory and apply novel ideas for competitive advantage or simply for survival. Bland consensus never helps, neither does the application of simplistic consultancy recipes and attempts to make things practical, in the sense of doing something familiar (which is the normal meaning). These are all the enemies of KM |
| Focusing on the past and the present and not on the future | Another good one and one which could be applied to a lot more than KM. From complexity theory we get the idea of retrospective coherence, and the simple statement that hindsight does not lead to foresight. The future is uncertain, replete with possibilities. Knowledge as a strategic tool can take us there, informed but not controlled by the past. |
| Failing to recognize the importance of experimentation | Too many organisations go for fail-safe design rather than safe-fail experimentation. In a KM system there are no right answers, although there are several wrong ones! In 1998 the technology enabled but did not encourage experimentation. Now we have social computing and there is no reason for other than a low cost experimental entry into KM |
| Substituting technological contact for human interface | I think this one is 50-50 but that is with the benefit of time. Some technological interfaces (for example blogs) have a high human contact without the need for direct contact. Facebook and Twitter create intimacy. None of these were around in 1998 but I think if they had been this sin would have been written differently |
| Seeking to develop direct measures of knowledge | Again this one was correct at the time, and is still correct if people want to use the unbalanced score card or explicit outcome based targets. The most stupid is to count hits on a web site. However ten years later we now have some novel ways (quantitative material supported by rich narrative for example) which offer the possibility of measuring the impact, if not the outcome of knowledge applcations |
Overall its impressive how the list has stood up. Its been interesting reviewing it, if briefly. All comments appreciated!
Comments (8)
It's really nice to see a list like this. You convey these key ideas deceptively well and consistently, without over complicating them (which can be tricky :p). Thanks Dave.
While I am still learning the details, most of the concepts here seem intuitively right to me. I'm not quite clear on what technological contact is though. Could someone expand a bit please?
Posted by Glenn | July 11, 2007 3:51 AM
Posted on July 11, 2007 03:51
A really nice commentary Dave, I have blogged on it today. My only thought on your response to the first sin is that I have always taken that to mean developing a common working understanding of what KM means to the given organisation.
As you know, I have little patience for the definition debates, but I do believe it is important for an organisation to figure out and explain what KM means/should mean for the organisation - we usually help our clients encapsulate this at the end of a KM strategy exercise into a KM vision statement that explains what KM means for the organisation, and what's important about the KM activity that will follow.
So maybe "working definition" is a little too strong and misleading, but "common understanding" should be less sinful, surely?
Posted by Patrick Lambe
|
July 11, 2007 7:18 AM
Posted on July 11, 2007 07:18
Thanks Glen and Patrick.
Glen - my interpretation of technological contact is when people link via a virtual environment rather than face to face or over a telephone.
Patrick - I agree on understanding, its why I referenced the taxi driver and the map story which I should have elaborated. I will do that at some stage in the future
Posted by Dave Snowden
|
July 11, 2007 11:27 AM
Posted on July 11, 2007 11:27
Thanks for a timely flashback to timeless issues, Dave. To pick but one, I think the stance that knowledge is "all about action", provides an escape from the whole "Viewing knowledge as existing predominantly outside the heads of individuals" issue. The focus on behaviour lets us view knowledge as an aspect of the currently acting system, be it a person, an organization or a country - rather than a constituent part of it.
If you accept that, it follows that viewing knowledge as located inside or outside the brain is neither right nor wrong, but simply a red herring, a quasi-issue, a counter-productive trap. Instead, we can look into the processes and determinants of those behaviour patterns that interest us, and the fruitful question of how to cultivate these.
Posted by Gunnar J. Coll | July 11, 2007 2:45 PM
Posted on July 11, 2007 14:45
Hi --
Seems no one has the courage to ponder why these are STILL sins. Frankly, it vicious cycle of KM. KM people are co-dependent enablers; they are fearful risk managers. Hence, they continuously perpetuate their myths and commit mortal sins. Any normal disipline would have 'new' sins after a decade.
The KM doctor is very ill.
Also, the axe-grinding on social atomism is a nuisance. "Viewing knowledge as existing predominantly outside the heads of individuals" IS about the collective intelligence, about collaborative knowledge, value networks, narrative and information markets.
After all, it does not read:
"Viewing knowledge as existing predominantly outside the head of an individual."
Please, we are suitably warned of atomism, but it is starting to interfere with critical complex properties of markets, networks. It is making the ‘cognitive-edge’ rather dull.
Cheers,
-j
Posted by John T. Maloney | July 12, 2007 3:52 PM
Posted on July 12, 2007 15:52
John, while I have concerns about KM I am not prepared to support the stereotyping above. I think a similar list could be produced for most management movements (including value networks) and at least the list came from KM itself.
As to social atomism - we have an ideological disagreement here as we both know. My view is that it is critical to sharpening the edge
Posted by Dave Snowden
|
July 12, 2007 6:22 PM
Posted on July 12, 2007 18:22
Hi --
Failure to examine oneself, one’s craft and profession, is what perpetuates these sins.
Stereotype is not pejorative. Look at Corporate IT. Their job is risk management. The do it very well for the most part. They fall down when trying to create or lead any sort of business strategy. It is why there has been an enormous migration of strategic and tactical ICT into business units, away from the controlling influences of IT. In short, IT as a strategic change agent has been a failure. That’s fine, workable, a fact of life.
Sadly, KM has adopted this model and is perpetually sinning.
Look, in the KM era of Prusak, Stewart, Fahey, JS Brown, etc., KM was iconoclastic. The KM archetype was leadership!
A decade ago the 11 Sins were telegraphing the eventual demise of KM. For heaven sake, go to a KM conference, the people there are secretaries, retirees, administrators, librarians – they are not leaders. They are knowledge apparatchiks. These roles are important and honorable; it is just not KM…
Yes, it is encouraging that the list came from KM, but it was a generation ago, before the huge intellectual and professional flight from KM.
BTW, the duality of the collective AND the individual originates from Hayek, e.g., “It is with respect to this that practically every individual has some advantage over all others because he possesses unique information of which beneficial use might be made, but of which use can be made only if the decisions depending on it are left to him or are made with his active co-operation.” Social atomism is a red herring and unworthy polemic.
Finally, it is not good to be glib about so-called ‘management movements’ whatever those are. That's what got us in the mess of BPR for example.
BTW, belated thanks for the list, your comments and reply.
Cordially,
-j
Posted by John T. Maloney | July 13, 2007 1:24 AM
Posted on July 13, 2007 01:24
Excellent commentary. I think the idea of an "11 Deadly Sins" is a perfectly useful way of stimulating a directed dialog (multilog?) on this subject. The London cabbie with the "knowledge" vs. a map is a very useful analogy. One equally useful for the technology KM often finds it self in is an experienced local driver vs. MapQuest or similar mapping programs using GIS-like databases. The latter may know the apparent shortest route in terms of distance but not the fastest or least stressful and programs such as those do not (yet) allow for commentary or alternative routings by users (i.e., the network).
The only other thing I would note is that KM has been confounded (not necessarily by this community) with ICT. It is important to stress that KM long precedes the Internet and the computer (hence all those librarians and secretaries and consultants). Technology has vastly ramped up the capability of knowledge networks to solve/manage problems the way that pre-modern KM networks did (and still do) but on a potentially vastly larger scale. But it would be a tragedy for Km to be ghetto-ized into simply a "branch" of ICT.
Posted by Jim Tarrant | July 16, 2007 10:02 PM
Posted on July 16, 2007 22:02