Why SharePoint 2010 may not be the Answer to the Social Intranet
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

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

on

  • 7,342 views

 

Statistics

Views

Total Views
7,342
Views on SlideShare
7,318
Embed Views
24

Actions

Likes
9
Downloads
92
Comments
2

3 Embeds 24

http://paper.li 11
http://connections.ey.net 11
http://twitter.com 2

Accessibility

Categories

Upload Details

Uploaded via as Adobe PDF

Usage Rights

CC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs LicenseCC Attribution-NonCommercial-NoDerivs License

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

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

  • 1. Why SharePoint 2010 May Not BeThe Answer To The Social Intranet Thomas Vander Wal - InfoCloud Solutions, Inc. 2 March 2011 Intrateam :: Copenhagen
  • 2. Understanding socialcomponents and what is needed to build an optimal solution
  • 3. Social Tools and Fit
  • 4. Social Activity Types
  • 5. Personal
  • 6. Collective
  • 7. Community
  • 8. Collaborative
  • 9. Elements of CollaborationSocial Software Groups Conversation Relationship Reputation Build Order Sharing Actions Presence Identity Object
  • 10. Collaboration GroupsTraditionalGroupware Conversation Relationship Reputation Build Order Sharing Actions Presence Identity Object
  • 11. Social Progressions• Sparks: Ideas shared• Campfire: Gathering of others with interests• Bonfire: Broader interest gathering• Torch: Honing for broad use & replication
  • 12. Comfortable Spaces withPermeable Walls
  • 13. The 4 rings of enterprise social tools
  • 14. Enterprise Social Tool:Components for Success Tools
  • 15. Enterprise Social Tool:Components for Success Capabilities Tools Interface / Ease of Use
  • 16. Enterprise Social Tool: Components for Success Capabilities Tools Interface / Ease of Use Intelligence &Business Needs Sociality
  • 17. Spheres of Sociality Everyone Collective Selective Personal
  • 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. Where SharePoint 2010has strength for social
  • 20. SharePoint is a toolkit with“some” assembly required
  • 21. Already used, which removes anotherdisconnected service
  • 22. Platform, tool, andinterface where other work is being done.
  • 23. Solid identity and formal relationship platform
  • 24. Information Across Horizontals Div 1 Div 2 Div 3 Div 4 Packaging Logistics Marketing
  • 25. Solid dataunderpinnings
  • 26. Do your SharePoint developersknow all they need to deploy anoptimal social intranet solution?
  • 27. Do they have depth understanding socialinteraction, or are theysocial tool “clickspert”
  • 28. SharePoint Social Developer Needs• Deep SharePoint knowledge• Interaction design strength• Depth in complicated and complex social interactions• Social interaction design
  • 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. 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. Closer to Real Growth Curve
  • 32. Build or buy a social intranet solution as a best fit for SharePoint 2010
  • 33. Key Questions...
  • 34. SharePoint experienced developer with time?
  • 35. Do you have developers& designers with social software development experience?
  • 36. Abilities to modifySharePoint to customize deeply if needed?
  • 37. Are the social tools the developers priority?
  • 38. If one or more “no”answers, it could be well worth it to consider options
  • 39. Options...
  • 40. General Advantages• Advantages: • Quick up and running social tools • Optimizing more difficult elements is done • Continual iterations and improvements
  • 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. 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. Built On Top of SP 2010• Newsgator• Telligent
  • 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. 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. SP 2010 Plug-in• Jive• Socialtext• Traction• Socialcast (activity stream and communication platform)• Many more...
  • 47. Mange Tak!
  • 48. URL: http://infocloudsolutions.comE-mail: thomas@infocloudsolutions.comAIM: vanderwalSkype: tjvanderwalTwitter: @vanderwal or @infocloud InfoCloud Solutions, Inc. - 2011