Knowledge Sharing Activities in People’s Daily Work
In my previous entries and at many other locations we discussed that it would be significantly beneficial if knowledge sharing activities of people are not an additional task but an integral part of their daily work. Many platforms - digital or not - require that people access another tool or step out of their daily routine. To achieve this, a good am of motivation and personal benefits is needed and we all agree this is not an easy task. Integrating knowledge sharing into people’s daily work would be without doubt a strong driver for user adoption.
How to integrate knowledge sharing in the daily routine? We have asked our users for ideas and I am happy to summarise here what they have came up with.
- When we establishing a project definition or a failure analysis, link to the global knowledge platform to search for similar solution and benchmarks
- At the end of each project, conduct an after action review and contribute the results to the global knowledge platform
- Integrate the platform into the e-mail system; one access point and one password
- Install a notice in all meeting rooms that reminds to access the global knowledge platform for related topics and identify results that can be shared
- In training sessions refer to the knowledge platform to access related information
In addition to this recent survey, we have integrated a regional remedy system with our global knowledge platform: when entering a new incident the user can directly search the global platform for solutions; the discussions from the remedy system are made available in the global knowledge search. This was a simple solution to integrate existing regional knowledge sharing activities in the global platform.
What are your experiences to plant knowledge sharing activities in people’s daily work?
1 Comment so far
Page 1 of 1 pages
Comment Guidelines: Basic XHTML is allowed (<strong>, <em>, <a>) Line breaks and paragraphs are automatically generated. URLs are automatically converted into links.
Here’s what I think, you need to steal the email market share...you need a new dashboard to rival the inbox, just like Facebook has done.
Rather than wait for the AAR, ask questions in the status updates of your project homepage, or even post experiences in a blog (not sure if people do this in email already, or it’s something new that the blog format encourages...like the Star Trek captains log). This is in-the-flow real time solutions and learning. We need to do this anyway as memory fades and looking in hindsight we suffer from makes things look much more linear...instead we want lots of blog post fragments, which we can interpret ourselves later on (ie see patterns).
Collect anecdotes as issues occur to find patterns
http://johntropea.tumblr.com/post/5231761245
Capture as it happens - Memory fades, protecting our world view, and forcing cause and effect
http://johntropea.tumblr.com/post/9851009344
Use wikis for meeting agendas, or even use forums to deal with issues as they happen. This way meetings are more about action.
Observable work, not status meetings
http://johntropea.tumblr.com/post/9560846194
Discuss a document via the comments field on the document itself. These new comments will appear in your activity stream, or your @mention stream if you have been @mentioned within the comment.
The way I see it is email is our in-the-flow tool, so we need to re-purpose it as much as we can. And at the same time we need to have conversations on the object itself, this way a conversations simply is metadata
Posted on November 10, 2011 at 10:48 AM | Comment permalink