20080409 Bkmf Km2.0


Published on

Presentation by Ray Sims at Boston KM Forum's "KM 2.0 – Real or Hype?" quarterly event at Bentley College.

Published in: Technology, News & Politics
  • Ray, Excellent preso! I especially like the timeline-themed '2.0 resume' - this is the second time I've seen something like it and I wonder if this could be the future of resumes?
    Are you sure you want to  Yes  No
    Your message goes here
  • Good seeing you again today Ray, great presentation, and I think the flow worked well from you to me. Still much more to be spoken and written, but another drop in the bucket!
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • 20080409 Bkmf Km2.0

    1. 1. <ul><ul><li>KM and Web 2.0 – </li></ul></ul><ul><ul><li>A User’s Perspective </li></ul></ul><ul><ul><li>Boston KM Forum: </li></ul></ul><ul><ul><li>KM 2.0 – Real or Hype? </li></ul></ul>
    2. 2. Ray's 2.0 Resume (early adopter, or not?)‏ (≈ 250 Contacts)‏ (≈3700 Bookmarks)‏ (≈400 Tweets)‏ <ul><li>Novell internal wiki </li></ul><ul><li>Novell internal blog </li></ul><ul><li>Podcast fanatic </li></ul><ul><li>RSS fanatic </li></ul><ul><li>blog.simslearningconnections </li></ul>(≈3 0 at any time)‏ <ul><li>Linux desktop </li></ul>
    3. 3. Topics <ul><li>Web 2.0 </li></ul><ul><li>Knowledge Management </li></ul><ul><li>Three scenarios for bringing the two together </li></ul><ul><li>Closing thoughts </li></ul>
    4. 4. <ul><ul><li>What “2.0” means to me... </li></ul></ul>
    5. 7. <ul><ul><li>What KM means to me... </li></ul></ul>
    6. 9. Three Definitional Questions (of the many we could ask)‏ <ul><li>1) What scale? </li></ul><ul><li>2) What domain? </li></ul><ul><li>3) What metaphor? </li></ul>
    7. 10. <ul><ul><li>Scale </li></ul></ul>
    8. 11. Individual <ul><li>Personal Knowledge Management (PKM), and Personal Learning Environments (PLE)‏ </li></ul>
    9. 12. Team <ul><li>Team / Project / Community knowledge management and learning </li></ul>
    10. 13. Organization <ul><li>Organizational Knowledge Management and Learning </li></ul>
    11. 14. <ul><ul><li>Domain </li></ul></ul>
    12. 15. Where Does KM Start or Stop?
    13. 16. <ul><li>KM Activities </li></ul><ul><li>Knowledge Distribution (26)‏ </li></ul><ul><li>Knowledge Creation (21)‏ </li></ul><ul><li>Learning (14)‏ </li></ul><ul><li>Knowledge Classification (9)‏ </li></ul><ul><li>Collaboration (7)‏ </li></ul><ul><li>Knowledge Harvesting (6) </li></ul><ul><li>Knowledge Discovery (2) </li></ul><ul><li>KM Outcomes </li></ul><ul><li>Improved Execution (28)‏ </li></ul><ul><li>Value from Knowledge Assets (12)‏ </li></ul><ul><li>Knowledge Codification (11)‏ </li></ul><ul><li>Knowledge Retention (3)‏ </li></ul><ul><li>Continuous Improvement (2)‏ </li></ul><ul><li>Cultural Change (2)‏ </li></ul><ul><li>Improved Knowledge Processing (1)‏ </li></ul><ul><li>Improved Resource Assignment (1)‏ </li></ul>Source: Stephen Bounds' analysis of Sims' 53 KM Definitions compilation. 25 March 2008 post to ActKM discussion list. The numbers with ( ) indicate the number of definitions which include this concept.
    14. 17. Firestone and McElroy <ul><li>One domain possibility is within an outlier in the compiled definitions... </li></ul><ul><li>...where KM is made distinct from Knowledge Processing </li></ul>
    15. 18. Source: Joseph M. Firestone in “On Doing Knowledge Management,” Knowledge Management Research & Practice (2008) 6, p.17. Adapted from Firestone and McElroy, 2007.
    16. 19. <ul><ul><li>Metaphors </li></ul></ul>
    17. 20. Stocks <ul><li>Codifying, capturing, harvesting, storing </li></ul>Static
    18. 21. Flows <ul><li>Conversations, fragments, connections </li></ul>Fluid and Dynamic
    19. 22. Why Flows? <ul><li>Speed of change versus speed of codifying </li></ul><ul><li>Continuous versus something that happens at the end of the project </li></ul><ul><li>Small pieces loosely joined, context preserving </li></ul><ul><li>Broader participation, with more connections </li></ul><ul><li>Weak signals perception </li></ul><ul><li>Results: innovation and better decision-making </li></ul>
    20. 23. Why Flows? <ul><li>“ If you ask someone, or a body for specific knowledge in the context of a real need it will never be refused. If you ask them to give you your knowledge on the basis that you may need it in the future, then you will never receive it.” (David Snowden)‏ </li></ul>
    21. 24. Taking This a Step Further... <ul><li>“ Knowledge as water was favoured most as metaphor to diagnose the situation, while knowledge as love was favoured for developing solutions.” (Daniel Andriessen, 2007)‏ </li></ul>
    22. 25. Knowledge as Love Statements (sample from Andriessen's paper) <ul><li>Problems </li></ul><ul><li>Knowledge exchange should be reward in itself </li></ul><ul><li>We lack quality time </li></ul><ul><li>There are a lot of attractive but lonely singles </li></ul><ul><li>We talk about wedding certificate but not about our relationship </li></ul><ul><li>We lack an atmosphere of trust </li></ul><ul><li>Our marriage sometime falls into a rut </li></ul><ul><li>Solutions </li></ul><ul><li>Allowed to choose our own partner </li></ul><ul><li>Allow variety in people’s passions and aspirations </li></ul><ul><li>Give people time and space to share knowledge </li></ul><ul><li>Don't try to manage and systemize knowledge </li></ul><ul><li>Allow polygamy: exchange knowledge with more people </li></ul>
    23. 26. Leaping to Some Early Conclusions... (via three scenarios)‏
    24. 27. The (non)Obvious Fit <ul><li>Web 2.0 is ideally situated to support Personal Knowledge Management / Personal Learning Environment (PKM / PLE) </li></ul>
    25. 29. PKM / PLE: Individual Benefits <ul><li>Increase knowledge within chosen field </li></ul><ul><ul><li>Maintain long-term employability </li></ul></ul><ul><li>Build external network </li></ul><ul><li>Bridge generational barriers </li></ul><ul><li>Increase competency for thriving in information abundance </li></ul><ul><li>Opportunity to become an enterprise 2.0 evangelist </li></ul>
    26. 30. Personal Example (another Network Effect and Twitter moment)‏
    27. 31. PKM / PLE: Company Benefits <ul><li>Smarter employees </li></ul><ul><li>Reduced Training & Development expense </li></ul><ul><li>Access to external networks </li></ul><ul><li>Bridge generational barriers </li></ul><ul><li>Create an enterprise 2.0 on-ramp </li></ul>
    28. 32. PKM / PLE: Company Prescription <ul><li>Provide PKM / PLE education </li></ul><ul><ul><li>Including provisioning a starter toolkit? </li></ul></ul><ul><li>Minimize firewall barriers to social networks / media </li></ul><ul><li>Encourage employee blogs </li></ul><ul><ul><li>Sun Microsystems example </li></ul></ul><ul><li>Build culture of trust </li></ul>
    29. 33. BT Case Study <ul><li>“ While some companies begin the impossible task of shutting out social media tools, at BT we have just completed a...project to make sure all our employees can access social media sites. Why? Because we see social media tools as a huge opportunity to transform the way our employees interact with each other, with ‘the company’, and with our customers, partners and suppliers.” (Richard Dennison)‏ </li></ul>
    30. 34. Required 2.0 Competencies <ul><li>Increased intellectual property sensitivity </li></ul><ul><li>Multi-tasking? </li></ul><ul><ul><li>Not really. Rather, increased attention discipline </li></ul></ul><ul><li>Skimming / scanning </li></ul><ul><li>Being OK with sharing “half-baked” + editing the boss </li></ul><ul><li>Efficient network creation and vetting </li></ul><ul><ul><li>Knowing what and whom to pay attention to </li></ul></ul><ul><li>Software application mechanics </li></ul>
    31. 35. Back to the Future? Source: Dave Pollard, How to Save the World, KM 0.0 - Simply Enabling Trusted Context-Rich Conversations Among Communities That Care, 6 December 2007
    32. 36. The Easy Entry (scenario #2)‏ <ul><li>Enterprise (KM) 2.0 is easily adopted & instantly valuable for small to medium sized teams and projects </li></ul>
    33. 37. Team/Project-level Killer Practice <ul><li>Wiki as default text and management tool </li></ul><ul><ul><li>Not documents, not SharePoint </li></ul></ul><ul><li>Project blogging </li></ul><ul><ul><li>Convey project news and decisions </li></ul></ul><ul><ul><li>Replaces status reports </li></ul></ul><ul><ul><li>etc. </li></ul></ul><ul><li>Ban project related email </li></ul><ul><ul><li>Period. </li></ul></ul>
    34. 38. Team/Project-level Wiki Use Cases (a few examples)‏ <ul><li>Design and product documentation </li></ul><ul><li>Decision log </li></ul><ul><li>Event planning </li></ul><ul><li>Project related good practice </li></ul><ul><li>Project related FAQ </li></ul><ul><li>Links to outside resources and references </li></ul>
    35. 40. The Longer Journey (scenario #3)‏ <ul><ul><li>Enterprise adoption, although more challenging; is already happening and shows promise </li></ul></ul>
    36. 41. The Four Greatest Opportunities (looking through a KM lens) <ul><li>Increased social capital </li></ul><ul><li>Increased innovation </li></ul><ul><li>Improved decision making </li></ul><ul><li>Improved efficiency </li></ul><ul><ul><li>Which also leads to increased adoption and contribution </li></ul></ul><ul><ul><li>A virtuous circle, after initial disruption </li></ul></ul>
    37. 42. Why More Efficient? <ul><li>Increased transparency (openness) </li></ul><ul><li>Network effect </li></ul><ul><li>Raw speed, e.g. wiki edits versus documents </li></ul><ul><li>Less overhead </li></ul><ul><li>Opportunity to reduce email </li></ul>
    38. 43. Source: Chris Rasmussen at US National Geospatial Intelligence Agency (via http://www.wikinomics.com/blog/index.php/2008/03/26/wiki-collaboration-leads-to-happiness/ )‏
    39. 44. Lightweight and Open Source: Matt Moore, Engineers without Fear blog (30 March 2008)‏ See http://www.slideshare.net/engineerswithoutfears/peak-email for fuller details
    40. 45. Reducing email <ul><li>Move to “pull” versus “push” </li></ul><ul><ul><li>I subscribe to, or view, what I need versus getting pushed what others think I might need </li></ul></ul><ul><li>Move to true collaboration on a work product versus “talking about” </li></ul><ul><ul><li>Increased focus </li></ul></ul><ul><li>More open </li></ul><ul><li>More easily tagged and searched </li></ul>
    41. 46. Concerns and Challenges <ul><li>Doesn't fit with the company culture </li></ul><ul><li>Technology immaturity and proliferation </li></ul><ul><li>Additional information silos and digital landfills </li></ul><ul><ul><li>Leaking intellectual property </li></ul></ul><ul><ul><li>Counter to compliance </li></ul></ul><ul><ul><li>Loss of control </li></ul></ul><ul><ul><li>Employee time waster </li></ul></ul>
    42. 47. Beginning The Enterprise Journey <ul><li>On Technology, decide if the utility metaphor is viable </li></ul><ul><ul><li>If it has support, then go for </li></ul></ul><ul><ul><li>Consider possibilities in an “intranet 2.0” approach </li></ul></ul><ul><ul><li>But also consider leading with core work processes </li></ul></ul><ul><li>Find and nurture the early adopters and innovators </li></ul><ul><ul><li>Don't force them to go underground </li></ul></ul><ul><li>Still start with an individual, team or company function strategy versus the entire enterprise </li></ul><ul><ul><li>Laying the foundation for the enterprise </li></ul></ul>
    43. 48. Integration and Coordination Key (for fullest value)‏ <ul><li>Technology </li></ul><ul><ul><li>Enterprise search </li></ul></ul><ul><ul><li>Single sign-on </li></ul></ul><ul><ul><li>Where practical, common branding & user experience </li></ul></ul><ul><li>Process / Workflow </li></ul><ul><ul><li>E.G., wiki for collaborative authoring that then feeds published static site or document for compliance </li></ul></ul><ul><li>Even if not company-wide platform, still maximally coordinate with others on enterprise 2.0 path </li></ul>
    44. 49. Critical Success Factors (the usual suspects + 1)‏ <ul><li>A champion or champions </li></ul><ul><li>Comprehensive training and assimilation plan </li></ul><ul><li>Comfort with user-driven innovation & emergence </li></ul>
    45. 50. Closing Thoughts <ul><li>More than hype </li></ul><ul><li>Networks and flows make a web 2.0 enabled KM look attractive </li></ul><ul><li>Just do it! </li></ul><ul><ul><li>Start somewhere, at least with yourself </li></ul></ul><ul><li>Engage in the knowledge management debate </li></ul>
    46. 51. Photo Credits <ul><li>2.0 meme mindmap: Janelle Siegrist (makeup), José Luis Molina (network), Ann-Kathrin Rehse (rose bud), Steven (glass house), Samuel Herrman (car), Reed (at computer)‏ </li></ul><ul><li>Scale pins: Sanja Gjenero </li></ul><ul><li>Stocks versus flows: Sanja Gjenero (books), Weatherstock (waterfall) – both via stock.xchng </li></ul><ul><li>Heart: Sundeip Arora </li></ul><ul><li>Route 66: Keith Syvinski </li></ul><ul><li>Leap : Penelope Berger </li></ul><ul><li>Bored child: Christie Merrill </li></ul>