correlate Rotating Header Image

Still a major pain point…Knowledge Management

Quite often we discuss the technology solutions that surround us: entity extraction, text mining, discovery, etc. However, in the midst of all the technology speak, it is easy to lose sight of user and customer problems. What are people trying to solve? What is their pain point? That is what is important, not the technology. The technology is a means to an end. (Disclaimer: I love technology, I simply believe that it should be used to solve a problem, not for its own individual sake.)

There are lots of write-ups about knowledge management being dead. I won’t link to them all, simply do a Google search on “knowledge management dead” if you wish to read articles discussing the topic like, “Knowledge Management In Its Model T Era“. Much of the KM is defunct hype in fact gets fueled by Google being so good at assisting the average user it getting to information quickly. But in the enterprise business environment, managing knowledge and information is a very real problem.

Take a look at the survey results from the April 2007 edition of Scientific Computing:

Biggest Frustration in Searching

Knowledge management (KM) is certainly evolving from its initial definition where a person’s sole responsibility was to research on behalf of others (even though that is still a very important need for organizations when searching complex topics and looking for answers to complex questions). The role of KM is to overcome the exact issues found in the survey. Rich Hoeg, a manager of Information Services at Honeywell, writes quite often on best KM practices at his blog, eContent.

KM solutions must help people find relevant information, help people find where to look, help people find respective experts in the organization, help people discover relevant information that they wouldn’t know to look for and help people so they spend their time doing their jobs, not searching.

SIDE NOTE: Here is a great link to a page with knowledge jargon and knowledge management terminology.

Sphere: Related Content

  • But of course...the answers are in the questions!

  • Over on my own blog I indulge myself by taking samples of text and unpacking them to figure out whether they make any sense and whether the sense they make is the one the author actually intended. Back in January I decided to do this for




    CRM
    , my point being that, as far as the technology products were concerned, all three of the "component nouns";—"customer," "relationship,"; and "management"—had been (in bowdlerized form) fouled up beyond all recognition. By the time I came to the final noun, I had built up enough evidence to argue "that technology providers have no idea what they are managing or why they are managing it." This is as true for knowledge management as it is for CRM. The difference is that, now that knowledge management is on the down-side of the


    Gartner hype curve, its failure to address the two questions Lou used to lead his post is now generally recognized!


    To some extent is was a product of technology providers getting hung up on the word knowledge when they should have been worrying about talking about it in productive ways. Part (but hardly all) of the blame can be laid on Nonaka and Takeuchi, whose introductory chapter about "knowledge" is so shot through with holes that even a "gentleman's C" college freshman can find some of them! However, a more important problem probably resided with all the different researchers who saw knowledge management as an opportunity to promote a personal agenda, whether it involved better data bases, communities of practice, Socratic dialogue, Marxist emancipation, or Heideggerian phenomenology. At least, in the old joke, the elephant only had three blind men groping at it!


    So, if we carve off all of this fat, is there any meat left on the bone?

    One important fact that may still need recognition is that, for all of their


    promotion, Google and Wikipedia are not "solutions to the knowledge problem" and are as much part of the fat as the more elevated disciplines I cited in the preceding paragraph. I tried to explore this observation back in February in my response to the announcement that the Middlebury College history department would not accept Wikipedia as an acceptable citation. The title of that post


    was "Research


    is not about the answers!
    ;" and neither is knowledge management.


    Let me try to reinforce this claim by going back to Lou's first question: What are people trying to solve? As I see it, every organization, whatever

    its size, is a collection of people who know things. If we then take, as a premise, that the "business" of the organization is to satisfy one or more


    goals, then the most important problem in managing the organization is to


    conduct day-to-day operations in such a way that the people who know things are contributing to satisfying the goals. (I know that sounds simplistic, but that's what happens when you start carving off the fat!) The very phrase "knowledge management" disclosed the problem that this was not happening: The things that people were doing were not always leveraging what they knew; and the organization was paying for it with unsatisfied or poorly satisfied goals. Now I am too much of an anti-positivist to accept this as the whole story; but at least it provides a framework in which the broader story can be told.


    One part of that broader story that what is missing is that whole question of "knowledge sharing," which became a focal point of knowledge management

    technology and ultimately led many to ask whether or not Google (and/or


    Wikipedia) was doing a better job. This is where positivism loses its


    punch, because sharing is something that takes place among human agents and therefore belong in the social world, rather than the objective world. Personally, I subscribe to a motto coined by one of my former colleagues who now teaches philosophy at San Jose State: Knowledge cannot be shared, but it can be made sharable. It is not a question of whether or not knowledge is being "poured" into repositories such as databases or even Web pages crawled by search engines. It is a question of the social engagements that take place within the organization and the ways in which those engagement facilitate or impede the "flow" of knowledge. In other words it is all about "talk" (which can take place through digital, as well as physical, channels); and, if we read our Plato better than Nonaka and Takeuchi did, we discover very quickly that much of that talk is ultimately descriptive in nature. It is through such descriptive talk that the scope of who knows what "diffuses" (a favorite word in knowledge management circles) through the


    organization; and often that descriptive talk is best reinforced in


    contexts of demonstrably effective actions. In other words it's all


    about both what you say and what you do!


    At this point we can loop back to Lou's wrap up "KM solutions must" sentence, because I would argue that, once you couple people doing things that lead to satisfying goals with a social climate that encourages descriptive talk reinforced by demonstrably effective actions, you have a KM solution! I apologize if this was a long trip; but, to paraphrase the old saw, there

    is no "royal road" to knowledge management. Now it is someone else's turn to talk (hopefully descriptively)!

blog comments powered by Disqus