I headed out to "Content to Context" yesterday, expecting to learn more about things like taxonomies and structured software packages. However, those are apparently "1.0" tools, and the world of knowledge management has moved on to 2.0. Knowledge is only useful if people are able to share it easily in ways that are meaningful. And knowledge can't be so tightly defined as to only include printed and electronic files. It is an organic concept that is, at its core, dependent on the people that generate it. Coming from an organization that has been trying, somewhat in vain, to get its employees on the document management / sharing train and calling that effort "knowledge management," I found this a) disturbing, and b) liberating. I would be excited to be able to implement a tool that fostered sharing from both the top down and the bottom up (and sideways, and in a mobius strip, if so inclined), and that was both easier to use and less expensive than our current software. However, what I can't figure out is how to convince my company that they should abandon a project that has already had so much time / effort / money poured into it. Is it better to make the best of what we've got?
Is there anyone out there with a similar problem? Has anyone come up with a good solution that they would like to share?
--Julie
Recent Comments