« The rolling content inventory | Main | Great Ocean Road »

Why KM is hard to do

Patrick Lambe has written an article exploring why KM is hard to do. To quote:

We recently did a small information management/knowledge management internal initiative at Straits Knowledge. The relative ease with which we did it, compared to the problems faced by several of our clients (much larger organisations) has got me pondering on the way that existing infrastructure impacts an organisation's current effectiveness, both positively and negatively. In this article I use the case study of our internal initiative to analyse the way that infrastructure in large organisations imposes friction on the rate of change, and propose some project management and change management strategies to deal with that. If you're the kind of person who prefers to cut to the chase, I'm using this blog post to summarise the takeaways for KM project planning that I ended up with.

Posted by jamesr on June 19, 2006 11:11 AM
Categories: Knowledge management