Wednesday, June 21, 2006

Why KM is hard to do

A Green Chameleon posts on why KM is hard to do.

The issue they focus on is that of "infrastructure" - systems & institutions that simultaneously enable & constrain.

The answers they come up with are:
- Consult intensively, but keep decision-making simple
- Establish and maintain clarity of purpose
- Acknowledge the baggage
- Manage the timeline
- Shorten and leverage learning curves
- Use social networks
- Provide for habit-changing strategies
- Demonstrate impact to stakeholders

Now there is some good stuff in the article - esp. observations on the nature of infrastructure. And the recommendations are solid & commonsensical.

KM is simple. Yet KM is hard. Reasons why this might be so have been occupying my thoughts recently.

As practical as the article is, I think it leaves out some key reasons why KM is hard to do:
- We think more is better. More knowledge is better knowledge. This assumption rarely holds.
- We have trained each other to be uncooperative from an early age. There is another word for collaboration at school... cheating.
- Most organisations begin KM programmes because they are responding to a traumatic change in their internal or external environment. However the result often ends up reinforcing the pre-change organisation more than the desired end state. It becomes a conservative part of the infrastructure that Patrick describes, a hindrance rather than a help.

1 comment:

Anonymous said...

Thanks for this Matthew, I should have asked you to do the blog version of the article! It's the best one-line summary of infrastructure I've seen :)

Thanks also for the comments on what we missed.