Knowledge Management at Boeing links to Behavior

Its about behaviors, not tools.  How often that is so true.  You need to know the behavior (decisions) before you choose your tools.  In the APQC blog by Lauren Trees.    " ... APQC recently spoke to Jyoti Patel, knowledge management strategist at Boeing, about how Boeing merged two organizations and developed common processes, knowledge management capabilities, and data system architectures while also designing a knowledge management strategy that emphasizes behaviors over tools. ... "     Worth a read.

One segment talks about their own internal wiki, something we also attempted.  I would make similar comments about hurdles to address:

" ... Our wiki, e-Book, has over 550 pages of content and 955 users; it has been built over 6 years as an entirely grassroots effort. I’ll speak to the cons first. It’s difficult to maintain a navigational structure that works for a diverse range of users, which happens when new groups join. We want to grow the user base to drive more participation, which leads to a higher standard of content. I think striking the balance between the right number of users while maintaining relevance to your core users is key. We have a lot of content consumers, but only a subset of those are content creators/editors, which means that there is a critical mass of users for a wiki to maintain efficacy. Another con is that our engineering population values content approved by experts, so it has been a hurdle for those folks to accept an open source model. Also, it’s slow to build content momentum within an organization where the demographics are so polarized and the level of comfort using a wiki is very inconsistent among employees. This is a long-term resource with long-term gains and had to be approached accordingly.   .... "