|
Srikantaiah, T. Kanti & Koenig, Michael E.D. (Eds.). Knowledge management in practice: connections and context. Medford, NJ: Information Today, Inc., 2008. xxii, 519, [2] pp. ISBN 978-1-57387-312-3 $59.50 (ASIST members $47.60)In general, I'm in agreement with the view of the editor of this organ that whenever the term 'knowledge management' is used, it is likely to be describing something other than the management of knowledge, which even proponents of the concept such as Davenport and Prusak agree is impossible. I was intrigued, therefore, when asked to review this rather weighty volume as to precisely what the various authors have in mind when they imagine a 'practice' of knowledge management. The editors certainly try to guide us through the maze, providing not only a table of contents, showing twenty-six chapters in eight parts, but also a 'roadmap', which turns out not to be any kind of 'map' at all, but simply another, alternative list of what the book deals with. The advantage of this broad categorization of topics is that a chapter can appear in more than one place, so that Chapter 17, for example, appears under 'Education and training', 'KM Audits', 'Knowledge preservation', and 'Taxonomies, ontologies, and metadata', whereas it can only be listed once in the contents list. This is a rather novel approach to listing the contents of a work and could be used more widely. However, let us move on to the content itself to seek what the practice of knowledge management actually involves. The first four chapters are all by the editors and constitute an introductory polemic arguing the case for knowledge management as an organizational practice. Part I proper is labelled 'Identifying the knowledge' and presents three chapters. The first of these illustrates the fundamental problem of knowledge management: Mahesh and Suresh argue that direct transfer of knowledge from one person to another is possible. To say that this misunderstands the communication process is an understatement. Certainly, I may speak to another person who knows something about a problem I face but all that person can do is to tell me something; in other words, s/he can transmit a message, which is based upon what s/he knows, but before I can incorporate it in my personal knowledge, I must be able to understand the message, interpret it, and incorporate it into what I already know about the problem area. In other words, knowledge is not 'transferred' - information about what is known is transferred and 'knowledge' is re-created through my own understanding of that message. It may be convenient to describe this process as 'knowledge transfer' but the concept cannot stand up to analysis and is of no value scientifically. Throughout the book, this inability to distinguish between 'knowledge' as a personal construct and the 'information' content of messages (oral, written, graphic, etc.) recurs again and again. For example, Chapter 12 is about creating search systems using taxonomies and ontologies (i.e., classification schemes of one kind or another), which are designed to search what? 'Knowledge repositories', perhaps? Well, if such repositories are simply collections of electronic documents of one kind or another, yes; because these search systems, using approaches that have been familiar to information retrieval for decades, are designed to do just that. In other words, they are information retrieval systems. Quite why this is touted as a 'knowledge management' practice is somewhat bewildering. In another part of the jungle, Rossion describes a 'knowledge management approach' to the long-term preservation of 'knowledge'. What does this turn out to be? I will quote: [One of the key issues was] ...the dissemination but yet disconnection of the different pieces of knowledge generated during a research project; that situation leads to a wide range of unstructured data and documents, often in paper format, stored in personal folders and categorized according to personal classification schemes. Ah! Knowledge then, under this description is 'data and documents' - 'different pieces of knowledge'. I could go on, but it is evident that the proponents of 'knowledge management' are simply seeking to embrace the whole of library and information practice under a different term. Everything is here from document management systems to meta-data, from classification schemes to indexes of expertise (now renamed 'knowledge audits'. Will this attempt be successful? I doubt it. Anyone who has worked in the information field for any length of time will recognize much of what is here as old wine in new bottles and it is not surprising that a number of the papers deal with 'knowledge management' initiatives that fail. Is the volume of value to anyone? Yes, I think it is, as long as you do the internal translation from the language of 'knowledge management' to the language of information practice there is much here of interest—although often not for the reasons the authors imagine. Alexander G. Kelly
|