I responded to a post over at Brint.com. For those of you who don't frequent Brint, here's a peak:
Posted by Jim Nash on February 17, 2004 at 02:15:44:
We are in the process of designing knowledge management systems that have self-adaptive capacities for adapting to the changing business environment. We are facing a tension of extremes between our technical KMS architects and behavioral specialists. While the technical experts are pushing the artificial intelligence and expert systems agenda, the behavioral specialists are pitching Senge's organizational learning and soft systems thinking. Has anyone faced a similar situation in any other organization. How did you resolve this deadlock. All suggestions welcome. Thank you in advance. - Jim
---- Response ----
There is no resolution. You’re going to need both the techies and the behavioral specialists. It’s important, however, to realize why you need them. Let’s start with the techies.
Expert systems and case based reasoning tools are great for what they do: provide answers to known questions. These tools were developed for rote problem solving environments such as call centers and service departments. They are effective due to the nature of the information they contain and the types of answers they provide. The questions are all related to a canonical literature without discursive interpretations. It’s difficult, for example, to argue with information like the service recommendations for a 1987 Nissan Stanza. Although the users often have to seek hard-to-find information they are generally searching for known information. Expert systems and CBR tools merely afford a better way of accessing the information.
While service writers are rarely called on to create novel new information or synthesize disparate sources of information, a number of other professions are. Engineers, for example, have a wide variety of tools for creating physical artifacts such as machines, buildings, and micro-chips. While information management systems may make it easier for engineers to find documents that have already been created, the core of their work exists in the act of actually creating those documents. The same logic applies to most professions. While expert systems may not radically improve this creative process, organizational learning principles may.
The real trick is to create systems that enable these two epistemic communities—known item recallers and professional creators—to work together. They work in different ways; they have radically different vocabularies; And they use different internal power and discourse structures, etc. Indeed, it is almost impossible for a system to bridge this gap due to the polysemity and heterogeneity of their documentary practices. Without common vocabulary and usage any information retrieval system (such as CBR) is shot regardless of how well it indexes or cross references information. It’s all apples and oranges.
I realize this advice doesn’t really move you toward your goal of resolving the deadlock between techies and behaviorists. My only recommendation is to look at the most fundamental aspects of knowledge organization and ensure that they’re baked into your initiative. I suggest looking beyond the recent decade of KM-mania to the deep dark historiography of knowledge practices, particularly to the earliest common reference tools that were developed: directories, encyclopedias, thesauri, and dictionaries.
Regardless of the whether you adopt a behavioral or technical solution, be sure you can span your epistemic communities and attain the goals of the most primitive information systems. Can your solution allow people to find the people they need (like directories)? Get condensed repackaged information about aspects of their world of which they are ignorant (like encyclopedias)? Decipher the polysemous and heterogeneous language of their peers (like dictionaries)? Understand the dendritic relationships between words and concepts (like thesauri)? If you’re really keen, extend your thinking to those other dusty ancestors of KM like card catalogues and archives! Just stick with the basics.
I hope this helps. Feel free to drop me an email if you have questions or ideas.