Why SharePoint 2010 may not be the Answer to the Social Intranet

7,357 views
7,073 views

Published on

Published in: Technology
2 Comments
10 Likes
Statistics
Notes
No Downloads
Views
Total views
7,357
On SlideShare
0
From Embeds
0
Number of Embeds
25
Actions
Shares
0
Downloads
95
Comments
2
Likes
10
Embeds 0
No embeds

No notes for slide

Why SharePoint 2010 may not be the Answer to the Social Intranet

  1. 1. Why SharePoint 2010 May Not BeThe Answer To The Social Intranet Thomas Vander Wal - InfoCloud Solutions, Inc. 2 March 2011 Intrateam :: Copenhagen
  2. 2. Understanding socialcomponents and what is needed to build an optimal solution
  3. 3. Social Tools and Fit
  4. 4. Social Activity Types
  5. 5. Personal
  6. 6. Collective
  7. 7. Community
  8. 8. Collaborative
  9. 9. Elements of CollaborationSocial Software Groups Conversation Relationship Reputation Build Order Sharing Actions Presence Identity Object
  10. 10. Collaboration GroupsTraditionalGroupware Conversation Relationship Reputation Build Order Sharing Actions Presence Identity Object
  11. 11. Social Progressions• Sparks: Ideas shared• Campfire: Gathering of others with interests• Bonfire: Broader interest gathering• Torch: Honing for broad use & replication
  12. 12. Comfortable Spaces withPermeable Walls
  13. 13. The 4 rings of enterprise social tools
  14. 14. Enterprise Social Tool:Components for Success Tools
  15. 15. Enterprise Social Tool:Components for Success Capabilities Tools Interface / Ease of Use
  16. 16. Enterprise Social Tool: Components for Success Capabilities Tools Interface / Ease of Use Intelligence &Business Needs Sociality
  17. 17. Spheres of Sociality Everyone Collective Selective Personal
  18. 18. Enterprise Social Tool: Components for Success Capabilities Tools Interface / Ease of Use Intelligence & Expand Use &Business Needs Increase ROI Encouraging Sociality Use Social Comfort
  19. 19. Where SharePoint 2010has strength for social
  20. 20. SharePoint is a toolkit with“some” assembly required
  21. 21. Already used, which removes anotherdisconnected service
  22. 22. Platform, tool, andinterface where other work is being done.
  23. 23. Solid identity and formal relationship platform
  24. 24. Information Across Horizontals Div 1 Div 2 Div 3 Div 4 Packaging Logistics Marketing
  25. 25. Solid dataunderpinnings
  26. 26. Do your SharePoint developersknow all they need to deploy anoptimal social intranet solution?
  27. 27. Do they have depth understanding socialinteraction, or are theysocial tool “clickspert”
  28. 28. SharePoint Social Developer Needs• Deep SharePoint knowledge• Interaction design strength• Depth in complicated and complex social interactions• Social interaction design
  29. 29. Scaling and Functionality D A - Personal Use B - Serendipity CPeople Participating C - Mature Social Tool B D - Complex Social System A Actions InfoCloud Solutions, Inc. - 2011
  30. 30. Social Interaction Design• Simple communication patterns and progressions• Different design patterns to optimize use for social activity types• Optimizing for use (how to get unstuck with long term benefits)• Understanding when it is the tool, interface, and/or sociality (or culture) and how to think through it to solve
  31. 31. Closer to Real Growth Curve
  32. 32. Build or buy a social intranet solution as a best fit for SharePoint 2010
  33. 33. Key Questions...
  34. 34. SharePoint experienced developer with time?
  35. 35. Do you have developers& designers with social software development experience?
  36. 36. Abilities to modifySharePoint to customize deeply if needed?
  37. 37. Are the social tools the developers priority?
  38. 38. If one or more “no”answers, it could be well worth it to consider options
  39. 39. Options...
  40. 40. General Advantages• Advantages: • Quick up and running social tools • Optimizing more difficult elements is done • Continual iterations and improvements
  41. 41. Built On Top of SP 2010• Advantages: •Data (metadata) integrated tightly with SharePoint (bonus for search) •Tight integration with SharePoint strengths •One common platform
  42. 42. Built On Top of SP 2010• Disadvantages: • Can be limited to data and interface options (5 star ratings) • Waiting for improvements on top of SharePoint • 3rd party software focussed administrator / developer needed
  43. 43. Built On Top of SP 2010• Newsgator• Telligent
  44. 44. SharePoint Plug-ins• Advantages: •Iterations and innovations at its own pace •Quick cycle to get up and running •Getting best tools to fit your problems and culture •Heavy focus on social interactions •Often many years developing and iterating •Often embracing complicated and complex needs
  45. 45. SharePoint Plug-ins• Disadvantages: • Lack of perfect integration with SharePoint • Need additional admin or developer skills • Data / metadata stored outside SharePoint (search and aggregation implications) • Can be lag time to update when MS iterates SharePoint
  46. 46. SP 2010 Plug-in• Jive• Socialtext• Traction• Socialcast (activity stream and communication platform)• Many more...
  47. 47. Mange Tak!
  48. 48. URL: http://infocloudsolutions.comE-mail: thomas@infocloudsolutions.comAIM: vanderwalSkype: tjvanderwalTwitter: @vanderwal or @infocloud InfoCloud Solutions, Inc. - 2011

×