“Knowledge Management” and “Manage Knowledgement”
Ross Mayfield has an excellent post on using wikis for teambuilding that also has some interesting discussion of what he sees as a dichotomy between “Knowledge Management” and Manage Knowledgement”:
Manage Knowledgement is a way of describing KM that’s backwards but works. With KM, users were supposed to fill out forms as a side activity to extract their tacit knowledge. Then some form of artificial intelligence would extract value. Turns out, users resisted and the algorithms didn’t match reality. With MK, through blogs and wikis, the principle activity is sharing, driven by social incentives. Contribution is simple and unstructured, isn’t a side activity and there is permission to participate. Intelligence is provided by participants, both through the act of sharing and simply leaving behind breadcrumbs of attention.
This is a more organic approach to managing and sharing knowledge that I think is centered in how people really work, as opposed to artificial constructs. That’s not to say that there still isn’t something artificial about blogs and wikis in some sense, but I think they lend themselves to our more social natures, capitalizing on our uses of social currency. I’m not aware of any “knowledge management” systems (with a capital KM) that sprang up on their own, nor am I aware of droves of people wanting to participate in KM systems just for the fun of it. The growth of social media outside of any corporate mandates, the fact that people are using these tools “under the radar,” suggests to me that they are already better-suited in many ways to human interaction than previous KM systems might have been.
Of course, within this new paradigm of sharing knowledge people need to not only learn the specific technology skills associated with these tools, but they also have to learn new processes. For example, as Ross points out, when we begin using social media tools, we have to have conversations about how to make the best uses of them:
Simple conversations occur that lead to simple agreements like “let’s use these four tags, for these four kinds of information — and lets agree to pay attention to pages and posts with this tag on a daily basis.” While it seems mundane at first, the team not only develops a shared language, but a way of working with it.
We can see, then, that we have two very different sets of literacies that need to be developed–the technological skills to be able to edit a wiki or comment on a blog post, but also the people/process skills necessary to negotiate the kinds of tags you’ll share or to write a blog post that effectively summarizes what you learned at a conference. This is what makes developing new work literacies difficult for many people, I think–it’s asking us to combine technology and people skills in ways that can be challenging to those of us who may have tended to specialize in one or the other. There’s an even greater integration of people and technology skills than we may have experienced before.
You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.
June 10th, 2008 at 7:48 am
Making the technology as easy as possible, or selecting the easiest technology should always be part of our KM/MK plans. This is where enterprise software has fallen apart, but many ERP implementation specialists have made much money.
My rule of thumb is to try to find a technology that’s as easy as e-mail. I’ve also learned that it’s best to start with one technology/application at a time. For newcomers, blogs and wikis are the same beast. Don’t ask them to master both at the same time or there will be confusion.
June 10th, 2008 at 8:01 am
Harold–totally agree on the need for technology to be as easy to use as email. I also agree that we need to not overwhelm people with suggestions that they learn several technologies at once. That’s a recipe for disaster!
Within organizations, I suspect that wikis might actually be an easier sell than blogs as a starting point. I think that people can more easily see where an easily editable group website can have a ton of applications. I think that blogs may be a harder sell, though, except potentially as marketing/communication platforms for external use.
June 10th, 2008 at 8:21 am
I was introduced to e-mail in 1991. At that time, it was so complex that I didn’t even want to figure out e-mail until I was forced to 8 years later. By that time, e-mail was simple. Now it is even more powerful and user friendly. The same thing could be said for word processing (I remember when I used to have to put code in similar to HTML to format). One thing we have to remember is that new technologies still are not at a level that non-techies will be able to figure out how to use them. I think we risk introducing new technologies to workers before they (the technology, workers, and even the organization) are ready.
June 10th, 2008 at 2:11 pm
Harold - I also use email as an example / analogy. Of course, even with email the use of it is still evolving. And it takes a while to get good at it. Of course, it was probably more obvious the value proposition once you had to sent a message to someone and the other option was paper / mail.
June 10th, 2008 at 7:42 pm
There is a fundamental difference as well between tagging/writing so that others can understand (and find) your work, and tagging/writing something so you can remember/find it yourself.
I think Harold has a point, technology has a part to play, but it needs to get out of the way and allow people to grapple with the underlying issues rather than the technology.
One problem with wikis is that they tend to get out of date quickly, sometimes that’s appropriate (e.g. when they relate to a project), but often it means that useful content is exiled in an unused wiki, when it should have a lifespan beyond it. Finding a way to make knowledge ‘elements’ usable in wikis/blogs etc., but still portable between different sites, might be a useful way to go.
June 11th, 2008 at 11:45 am
Having been involved in several KM projects (with varying degrees of success) one of my observations is that the system (whatever technology it is based on) needs to address a very specific issue/topic/problem for it to take hold. Unless people can see the value and obtian value from it they will not use it. If it is successful at this level then extending the system to cover broader knowledge sharing within the organisation may be practical.
I also agree with the above comments about email. It needs to be easy but one of the reasons for the success of email is that not using within an organisational context excluded people from important conversations - if people feel they are missing out on something important by not paying attention to the KM system then it is more likely to be successful.