New Wave Collaboration And Enterprise 2.0


Published on

Let's see how some consumer and enterprise technologies are coming together to help organizations with expert location, knowledge management, portable identity, communities of practice, and re-imagining email as a collaboration tool.

Published in: Technology, Business
1 Comment
  • Apologies for the excessive blurring in the later slides - I unwittingly violated a community policy by leaking information. I'll try and find public domain examples to drop in as replacements soon.
    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

New Wave Collaboration And Enterprise 2.0

  1. 1. New Wave Collaboration and Enterprise 2.0 Daniel J. Pritchett, Sharing at Work
  2. 2. Topics <ul><ul><li>Knowledge Transfer vs. Knowledge Management vs. Expert Location </li></ul></ul><ul><ul><li>“ Above the flow” vs. “in the flow” collaboration </li></ul></ul><ul><ul><li>Expert Location and the Social Graph </li></ul></ul><ul><ul><li>Portable Identity </li></ul></ul><ul><ul><li>Multi-faceted collaboration tools </li></ul></ul><ul><ul><li>Activity Streams and communities of practice </li></ul></ul><ul><ul><li>Highs and lows of email-based collaboration </li></ul></ul><ul><ul><li>Consumer analogues </li></ul></ul><ul><ul><li>Innovation Management </li></ul></ul><ul><ul><li>Profiles of other corporate collaboration initiatives </li></ul></ul>
  3. 3. About Me <ul><ul><li>“ Workplace collaboration” blogger </li></ul></ul><ul><ul><ul><li>Writing at for a year now </li></ul></ul></ul><ul><ul><ul><li>[email_address] </li></ul></ul></ul><ul><ul><ul><li>Active on Friendfeed ( /dpritchett ) and Twitter ( @dpritchett ) </li></ul></ul></ul><ul><ul><li>Business Intelligence Solution Developer </li></ul></ul><ul><ul><ul><li>Joined a Fortune 100 manufacturer in 2005 after graduate school </li></ul></ul></ul><ul><ul><ul><li>Four years in the IT services group: </li></ul></ul></ul><ul><ul><ul><li>Two years of report development for the supply chain project </li></ul></ul></ul><ul><ul><ul><li>One year of ETL automation for the supply chain project </li></ul></ul></ul><ul><ul><ul><li>One year of business intelligence development </li></ul></ul></ul>
  4. 4. Knowledge Transfer vs. Knowledge Management vs. Expert Location <ul><li>Knowledge transfer (KT) is a series of one-time obligations </li></ul><ul><ul><li>Training for new hires, consultants, & transfers </li></ul></ul><ul><ul><li>Document responsibilities for one’s position </li></ul></ul><ul><ul><li>Top-down dissemination of corporate strategies </li></ul></ul><ul><li>Knowledge management (KM) is a continuous improvement strategy </li></ul><ul><ul><li>Automatically capture workflows and explicit knowledge </li></ul></ul><ul><li>Expert location bridges the gaps: </li></ul><ul><ul><li>Which of the thousands of other company employees in Memphis knows what I need to know to solve this new problem? </li></ul></ul><ul><ul><li>Provides access to “tacit knowledge” </li></ul></ul>
  5. 5. KM: In the flow vs. above the flow <ul><li>Key concept for collaboration change management </li></ul><ul><li>Above the flow collaboration tools are standalone destinations </li></ul><ul><ul><li>Wikipedia model provides a monolithic data repository. Think document stores in team rooms or shared file folders </li></ul></ul><ul><ul><li>Can be viewed by employees as unnecessary to daily work </li></ul></ul><ul><li>In the flow collaboration tools are tightly integrated with daily work tasks </li></ul><ul><ul><li>Think help ticket systems. Outlook/Domino/Web services generate email alerts and allow flexible reporting for metrics and exception handling </li></ul></ul><ul><ul><li>Unavoidable due to workflow integration and visible metrics </li></ul></ul>
  6. 6. How do we facilitate expert location today? <ul><li>Tenure with company affords contacts and experience across many business units </li></ul><ul><ul><li>Ask a company veteran to point you in the right direction </li></ul></ul><ul><li>Highly connected employees are extremely valuable but they are also bottlenecks as they can only work so many hours in a day </li></ul><ul><li>HR maintains a skills inventory; employees don’t use it for non-HR activities </li></ul>
  7. 7. How can we improve expert location? <ul><li>Public skills inventory (LinkedIn style) </li></ul><ul><li>Portable identities </li></ul><ul><li>Activity streams </li></ul>
  8. 8. My Portable Identity <ul><li>LDAP (using our Active Directory accounts) allows portable identities within enterprises </li></ul><ul><li>Active Directory profiles lack the descriptive depth of LinkedIn and Facebook </li></ul>
  9. 9. Reusing portable identities
  10. 10. Social Graph <ul><li>“ The global mapping of everybody and how they’re related” – Brad Fitzpatrick, Google </li></ul><ul><li>Facebook aims to map this graph and provide services utilizing the connections </li></ul><ul><li>Org charts are only part of the picture </li></ul><ul><ul><li>Aside from your current chain of command you might know plenty of people from previous teams </li></ul></ul><ul><ul><li>Ad-hoc workgroups cross team boundaries - think mergers and IT asset cutovers required, full-time month-long design doc “caves” </li></ul></ul>
  11. 11. Why do we use email as our primary connection? <ul><li>Decision makers and mobile employees don’t have the luxury of a web-based workflow </li></ul><ul><li>E-mail archiving and security best practices are well known </li></ul><ul><li>Lowest common denominator </li></ul>
  12. 12. The problem with how we sometimes use email <ul><li>Imagine a design doc in progress… </li></ul>
  13. 13. Why choose between email or wikis?
  14. 14. Example: Microblogging <ul><li>Immediate </li></ul><ul><li>Conversational </li></ul><ul><li>Eminently searchable </li></ul><ul><li>“ In the flow” </li></ul><ul><li>Team borders are optional </li></ul><ul><li>Mashups come naturally </li></ul>
  15. 15. Multiple access points
  16. 16. RSS and portable streams <ul><li>Publishing an XML version of the stream allows reuse with other tools </li></ul><ul><li>Meet employees where they are already comfortable </li></ul>
  17. 17. Consume info with RSS widgets
  18. 18. Interact via Instant Message
  19. 19. Email as an alert system
  20. 20. Topical tracking with keywords
  21. 21. Interact via Email <ul><li>  </li></ul>
  22. 22. What are email’s strong points? <ul><li>Universal </li></ul><ul><li>Asynchronous </li></ul><ul><li>Instant </li></ul><ul><li>Searchable archives </li></ul><ul><li>Alerts </li></ul><ul><li>Automation </li></ul><ul><li>Personal knowledge base </li></ul><ul><li>Few technical surprises </li></ul>
  23. 23. Email as a personal knowledge base
  24. 24. Where does email let us down? <ul><li>Unnecessary duplication of information </li></ul><ul><li>Threaded conversations can be hard to unravel </li></ul><ul><li>Getting latecomers up to speed on a discussion is difficult </li></ul><ul><li>Private by default – implicit loss of work history </li></ul><ul><li>Opaque personal knowledge bases limit potential for others to benefit from your workflow </li></ul>
  25. 25. Innovation Management
  26. 26. Innovation tool vendor: Spigit
  27. 27. Collaboration initiatives at other corporations
  28. 28. Deloitte’s D Street <ul><li>“ Wanted to make a large company feel smaller” </li></ul><ul><li>Average age of employees is 28 </li></ul><ul><li>“ more easily offer flexible work arrangements, establish virtual teams, bring new employees up to speed, improve collaboration and increase retention” </li></ul><ul><li>Pre-populated Facebook-style profiles </li></ul>
  29. 29. Lockheed’s “Unity” community <ul><li>54,000 US employees online </li></ul><ul><li>SharePoint 3.0 + Active Directory + Google search appliance </li></ul><ul><li>Post personal information such as hobbies, interests and bios with photos </li></ul><ul><li>&quot;The women's group asked for it to be open internationally” </li></ul><ul><li>Lockheed is working on a social-networking policy but today blocks access to most of the popular public social-networking sites. </li></ul>
  30. 30. United Business Media uses Jive SBS <ul><li>Works out of the box – community was online literally within one day of signing contract </li></ul><ul><li>Jive provides a standalone community with bookmarks, blogs, RSS widgets, </li></ul><ul><li>Not a SharePoint replacement, rather a community building complement </li></ul><ul><li>Tips: Log and brag about community “wins”, hold adoption contests, add polls and discussions to any announcements when possible </li></ul>
  31. 31. Wachovia uses SharePoint <ul><li>Staged rollout plan: 1,000 in December, 10,000 in Feb, all 120,000 by the end of 2008. </li></ul><ul><li>Acronym definition wiki quickly grew to 900 entries </li></ul><ul><li>Piloting per-project wiki program </li></ul><ul><li>“ Ultimately, Wachovia plans to extend its Enterprise 2.0 network to customers and business partners, but carefully and gradually.” </li></ul>
  32. 32. What’s coming up? <ul><li>SharePoint 2010 </li></ul><ul><li>Google Wave </li></ul><ul><li>Continued rise of Software as a Service </li></ul><ul><li>New applications leveraging social graphs </li></ul><ul><li>Greater focus on activity streams and alerts </li></ul><ul><li>Extend communities to embrace customers and suppliers </li></ul>
  33. 33. Questions and discussion <ul><li>Contact me @dpritchett on Twitter or as [email_address] </li></ul>