Informal, joined up Informal, joined up knowledge sharing knowledge sharing using using connected weblogs in connected weblogs in pursuit of pursuit of Mental Health Mental Health service improvement service improvement Lee Bryant, BlogTalk 2, July 2004 http://www. headshift .com [email protected]
28
Embed
Informal, joined up knowledge sharing using connected weblogs in pursuit of Mental Health service improvement Lee Bryant, BlogTalk 2, July 2004 .
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
Informal, joined up knowledge Informal, joined up knowledge sharingsharing using connected using connected
weblogs in pursuit of weblogs in pursuit of Mental Mental Health service improvementHealth service improvement
Lee Bryant, BlogTalk 2, July 2004http://www.headshift.com
1. Weblogs as personal and social knowledge sharing tools
2. How to stimulate and support a social knowledge sharing network
3. Getting Started: identifying and encouraging potential blogging ‘voices’ in knowledge networks
4. How we support individual and collective modes within a social software-based knowledge community
5. Some observations on our methodology, conclusions & linksNotes available on SubEthaEdit now, on the Wiki later or mail me….
1 :: Weblogs as personal and social knowledge sharing tools
Some barriers to online knowledge sharing• Knowledge is a social construct - not just ‘content’
to be managed• Too focused on content creation vs. linking people• Formality of systems, tools and process• Metadata/“Metacrap” - top-down view not user
view• Divergent conceptual models of communication,
KM,e-learning and other software
• KM Software vendors lock us in to command and control systems, yet KM consultants speak of “knowledge ecology” and systems thinking
Lessons from Social Software
• Informality of weblogs / wikis encourages participation
representation and user involvement in categorisation
• Weblogs and Wikis promote ‘loosely joined’ markup and linking culture rather than content recreation
• Simple conceptual models for personal publishing
Social Software is not just online social networks and weblogs, but loosely coupled software that is…
Social in the way it is conceivedSocial in its purposeSocial in the way it behaves
2 :: How to stimulate and support a social knowledge sharing network in the real world
Case Study: National Institute for Mental Health in England
Aims:• cut across multiple, conflicting perspectives and interests• help people in different organisations & disciplines work
together to improve mental health services & experiences.
Key challenges:
Multiple perspectives - political issues of representationHighly devolved organisation with roots locally, in the fieldLow level of IT awareness and exposure beyond email & listsCultural ‘legacy’: long meetings, email-centric comms, etc. Integration: their work involves multiple organisations
A social engagement approach
1. Scope project --> map network --> define objectives together
2. Use a project weblog to learn their issues and language and to help teach them ours (knowledge transfer)
3. Participative design: let users shape their system4. Patient seeding of Weblog-driven local ‘feeder’ sites to
get early adopters blogging ‘close to home’ where comfortable
5. Develop the platform with pilot user groups6. Phased launch from core users -> partners -> public7. Training and support through events, demos, support
QuickTime™ and aTIFF (LZW) decompressor
are needed to see this picture.
Who are we trying to reach & why?
Offline networking & communications
Based on the target groups identified by the mapping, we undertook extensive offline networking among Mental Health professionals and service users to understand their content and interaction needs, and introduce people to blogging…
3 :: Getting started: identifying and encouraging potential blogging ‘voices’ in networked organisations
Keep it local, keep it simple, keep it real
• Setup ‘feeder’ blogs within local corporate Web sites• Train and mentor staff to allow direct posting to
public sites• Prove benefits of open dialogue through user
feedback• Aggregate upwards when they are ready - don’t
scare them!
Early wins: ‘feeder’ blogswww.nimhenorthwest.org.uk
• Participative design: don’t just consult - let users design
• ‘Feeder’ blogs can get early adopters blogging ‘close to home’ and grow outwards from there
• Modular development of the platform using web services - throw away what doesn’t work and build on what does
• Phased rollout: core users -> partners -> public• Training and support through events, demos, support• Solve real problems and make friends - don’t sell
software
Some Links
• http://kc.nimhe.org.uk (invite only for now)• www.headshift.com/nimhekc (original Project Weblog
with background docs)• www.nimhenorthwest.org.uk (active local feeder site)• www.nimhewm.org.uk (active local feeder site)• http://bme.nimhe.org.uk (public consultation weblog) • http://www.nimhe.org.uk (background on NIMHE)• http://modern.nhs.uk/improvementknowledge
(collaboration site about improvement knowledge)• www.headshift.com/moments (headshift weblog)