tag:blogger.com,1999:blog-7585040184982733654.post6578105493110963708..comments2024-03-20T11:13:46.071+00:00Comments on Knoco stories: What Enterprise Social Networks can tell us about KM adoptionNick Miltonhttp://www.blogger.com/profile/02413967879826601863noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-7585040184982733654.post-71368440700817598322018-01-10T13:59:10.504+00:002018-01-10T13:59:10.504+00:00Thanks JackThanks JackNick Miltonhttps://www.blogger.com/profile/02413967879826601863noreply@blogger.comtag:blogger.com,1999:blog-7585040184982733654.post-6515353012693778602018-01-10T13:52:24.016+00:002018-01-10T13:52:24.016+00:00It's a familiar problem when we look at "...It's a familiar problem when we look at "update" or "contributions" in almost any capability like this. I was actually surprised to see numbers above 20% in your quotes. Remember the ratio of heavy contributors to contributors to lurkers 1:9:90 -- or variations on that theme.<br /><br />I agree with the direction of your thinking though. _Why_ does this thing exist? What (business) problem does it solve? Do we already have commonly-used workarounds to that problem (email and hallway conversations)? Has anything been done to shut down / discourage the workarounds? <br /><br />I still go back to something from the early days of KM - the BP story described in Learning to Change - When people start new initiatives, the leaders ask what they've learned from previous initiatives like this. And no funding / permission if the investigation hasn't happened yet.jackvinsonhttps://www.blogger.com/profile/04640729671070784516noreply@blogger.com