|
|||||
|
|
|||||
|
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
Via Seb's Open Research: discussion about Klogging roles turns into discussion about The natural progression for knowledge: from K-logs to well structured forms. Blogs is definetely worse than simple disscussion board to give proper credits to all who participated. I would just cite some ideas:
I treat blog as my external brain more than a publishing tool (at least so far). Could you imagine someone trying to digest knowledge stored in several brains to get something meaningful out of it? Could be funny :))) From another side, there is at least one editor who might want to digest posts in blog - it's me. At first, blog helps me to capture ideas by articulating them, but then I want to look for patterns and connections that emerge. This would be something to do for the smart tools. Date, time and categories are definitely not enough for me. I want something like this: However, it is possible, once a K-Logging culture is in place to utilize taxonomy tools (tools like Wikis and Traction Software) to organize K-Log generated information into a larger whole. The key to success is to first lay the groundwork with a K-Log network and then leverage it after it begins to produce results. K-Logging puts the knowledge into a format that makes it easier to manipulate by a taxonomy tool. Longer term, I think most organizations will use combinations of the two types of tools to turn the Intranet into a rich, vibrant, and growing knowledge repository. (John Robb on K-Logs and Taxonomies in Yahoo! Groups: klogs) More on: personal knowledge management
|
This weblog is my learning diary. Sometimes I write about things related to my work, but the views expressed here are personal and do not necessarily reflect the views of my employer.
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||