October 15, 2011
Particularly impacts long-lived technical and scientific projects, where staff turnover has to be expected, or you need to revisit an issue months later and ask "how did we solve that"? Particularly in software, the 'design may be the code', but the thinking behind the code is needed too.
A system that people have reasonable buy-in to, that has parts that can encode and store specific knowledge with templates etc, but that also involves elements that are more flexible for 'emergent' or tentative ideas (eg Wikis, Trac projects). Plus I'm interested in systemic support to help navigate and 'garden' knowledge systems as they scale up.
Professional software developer and computational scientist - interested in knowledge management, particularly things such as Wiki websites for knowledge sharing and collaborative work.