7 Key Knowledge Management Principles

What are the key principles for knowledge management? Dave Snowden has been thinking about this topic (a.o.) and kicking against the KM world for some time.Now, he updated his old 3 rules to to 7 principles based on his thinking about KM in the legal profession. They are:
1. Knowledge can only be volunteered, it cannot be conscripted.
2. We only know what we know when we need to know it.
3. In the context of real need few people will withhold their knowledge.
4. Everything is fragmented (also refer to this one).
5. Tolerated failure imprints learning better than success.
6. The way we know things is not the way we report we know things.
7. We always know more than we can say, and we always say more than we can write down.
Great principles to chew on (as Mary Abraham says). Not only for the legal profession, but for all companies!
With respect to 'number 4' I'd also like to point to another great post by Snowden on bottom-up, low-cost knowledge management, starting with setting up blogs.Wiki's could/should be the next step in Snowden's bottom-up, low-cost community-building approach! John Tropea of Library Clips tells us how, by answering the question how blogs relate to wiki's.

Comments

  1. AnonymousOctober 23, 2008 at 10:57 AM

    Although hardly recognized in most organizations, the last principle is actually a real important one! The fact that we know more than we can say or write down has an important consequence for knowledge management in organizations. Currently, we are setting up a discussion about the impact of this form of knowledge on for example a Business Intelligence implementation. More on this subject can be found on www.intelligent-business.nl.

    ReplyDelete
  2. UnknownOctober 23, 2008 at 7:40 PM

    Thanks for your comment Mariska! True that principle is hardly recognized. Most organization think very mechanistically about KM. Thanks again for the pointer to your blog.

    ReplyDelete

Post a Comment

Please leave a comment! Just log in using one of the formats and if you want me to get back to you. Otherwise comment anonymously.

Popular posts

Keep the Intranet Small

Image
This tweet by Jonathan Phillips ( @digitaljonathan ) triggered to finalize this post, that's been burning in my draft box. I've always been intrigued by how unsuccessful many intranets are. And there are all kinds of good reasons for intranet failure. One of the things that is hardly ever mentioned is: Shouldn't the intranet be smaller? Usually intranets are huge. Lots and lots of pages with lots and lots of content. With complex navigation. The intranet  evaluation surveys almost always show employees only use the news page and people finder. But still we build and maintain nice big intranets. Not only stats point to smaller intranets. There are others reasons as well. I came up with a few. If you have more, just leave a comment. Here's my list: -            user requirements: users don't require large intranet -            search/navigation: searching and navigating a small intranet is easier than in a large intranet -            mobile: the content of the
Read more

Enterprise 2.0 Research

Image
There's not too much fundamental research on Enterprise 2.0. Deloitte recently published interesting research done on enterprise 2.0 implementations and their return-on-investment. In the EU research has also done as well. Study is being done for the European Commission and it was carried out by Tech4i2, IDC and Headshift. What was the goal of the study? Goals of the study To provide a clear definition of Enterprise 2.0 is, describe the market and the positioning of EU industry, also in comparison with US and Asia; To analyze the take-up of Enterprise 2.0, the organizational requirements, and the role on the transition to a knowledge based low-carbon economy; To collect evidence on its macro-economic impact, as a market opportunity for the European Software industry and as a productivity tool for European business; To identify and analyse both the direct and contextual challenges, including the need for Next Generation Access and the legal barriers; To analyse an
Read more

Innovation in Turbulent Times

Image
I love reading articles about innovation. And every now and then you read one that is very interesting. "Innovation in Turbulent Times" by Rigby, Gruver, Allen (in HBR, June 2009) is one of them. This article takes fashion companies as an example for continuous, year-by-year innovation. And how successful fashion companies are usually led by two people: a left-brainer and a right-brainer. "If you don't have highly creative people in positions of real authority, you won't get innovation. Most companies in other industries ignore this lesson." They extend this to show that successful non-fashion companies have the same kind of leadership. And this kind of leadership is usually also characterized by a long-term relationship. I think this concept can also be extended to teams and projects as well. More often than not, people are good at one or the other: thinking up great concepts or ideas, or, making them. In teams and projects we can learn from this as
Read more