Sharing knowledge with yourself

Stephen Downes responds to my recent post on weblogs and passion with the following observation:

Weblog tools are just another input device. Great. With a lousy search and user interface. Weblogs get data into the system, but that’s never been the problem with knowledge management: no, the problem is in using the data in any meaningful way. Will weblogs help with this? Not until something thinks seriously about the other end of the equation, thinks of the harried user rather than the inspired blog writer. [OLDaily]

While I agree that the current generation of weblog tools have some serious limits in terms of search and user interface, I disagree with his contention about where the problems lie in knowledge management systems. In the organizations where I’ve struggled to make knowledge management work, one of the fatal flaws has been the notion that knowledge management is somebody else’s problem. The silver bullet is out there in someone else’s head and “if only that lazy SOB had recorded the knowledge in the first place, then I’d be sitting fat and happy.”

I’ve concluded that one of the root problems with knowledge management is that I’m that lazy SOB. Until I start to do a better job of managing my own knowledge, why should I expect anyone else in the organization to do so? Weblogs are the first tool I’ve found that start me on the process of making my own knowledge more useful to me.

Here’s where the explicit vs. tacit distinction made so often in knowledge management discussions is misleading. Sure, the knowledge that has become so central to my work that I don’t have to think about it is a source of great power, is difficult to capture, and more difficult yet to share. But a huge amount of the knowledge important to me remains explicit and never ends up making the cut to tacit. That doesn’t mean I can’t make it a more useful resource to me.

Here’s a little test you can run on your own PC. Search for all the document files, spreadsheets, or powerpoint presentations stored on your machine. How many have a filename something along the lines of “final draft xx.doc” where xx is some number between 1 and 10? Can you tell what’s inside that file without opening it? If there was a diagram you used in a presentation last year that you wanted to use tomorrow, how many presentations would you have to open and scan before you found it?

The problem with getting more leverage out of knowledge work isn’t somewhere out there in the organization. It’s looking back at me in the mirror every morning. Worse than that, it’s that lazy slob I was looking at in the mirror six months ago who was too busy then to put a halfway decent name on a file or save that really great diagram as its own file.

What does this have to do with weblogs? Weblogs put the emphasis where I believe it belongs; on the individual knowledge worker. It encourages them to begin thinking about their own knowledge work more explicitly and systematically. It helps them realize that they are the problem and the solution. You have to learn how to share knowledge with yourself over time before you can begin to share it effectively with others.