The summary of the Blogwalk discussion on the Knowledge Board provides a rather definitive statement of how communities of practice have certain advantages over weblogs as a knowledge management tool:
Communities are better social structures for problem-solving, knowledge stewarding and innovation
Part of the justification for this is as follows:
A weblog is usually very poor in content structure… In order to be reuseable, a body of knowledge geared towards action typically has more structure: description, keywords, type of information, type of content, type of data, type of document, summary, domain of knowledge, subdomain, attributes, etc.
I’m somewhat sceptical about this. Much of my involvement with our projects is in technical areas – in fact sometimes, it seems that all I do is solve technical glitches that prevent our solutions from working. One of the main tools for this is the collective knowledge of people who have been there, done that with the particular problem I’m facing – and increasingly, their knowledge is expressed in the form of a blog entry. “I’ve been wrestling with problem x, and here’s what I did to resolve it’ is a typical style of entry that will be thrown up when you Google a ‘how do I fix this kind of problem’-type question.
And occasionally, that’s something I contribute back to the world at large, relating a tale of how I tamed the recalcitrant beast of PHP – or whatever – through breathtaking feats of daring-do. (Or more prosaically, fixing typos in the code
But if I had to structure that knowledge, by codifying it and entering into some kind of knowledge base, it’s probably something that I wouldn’t bother with. Firstly, publicly-accessible formal knowledge bases of this kind are few and far between in the types of areas I find myself working in; and secondly because the knowledge is dispersed around a community of involved individuals, it’s unlikely that there would be any grand coming-together to agree such a codification structure in the first place. In that respect, dealing with open source developers is somewhat akin to herding cats.
So perhaps the issue here is not about the codification and classification of the knowledge in the first place, and more about the ease of search and retrieval afterwards. One of the frustrations I encounter daily is knowing how to phrase searches so that they will bring back the hits that I’m after – there are broad similarities in the way that problems are referred to and explained, but ultimately every description is personal. Formal codification would solve this problem, but it would be at the cost of much of the knowledge not being expressed in the first place – so perhaps here is a situation where it’s more a question of quantity, than quality?
