1. Why SharePoint 2010 May Not Be
The Answer To The Social Intranet
Thomas Vander Wal - InfoCloud Solutions, Inc.
2 March 2011
Intrateam :: Copenhagen

2. Understanding social
components 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 Collaboration
Social Software
Groups
Conversation
Relationship
Reputation Build
Order
Sharing
Actions
Presence
Identity Object

10. Collaboration
Groups
Traditional
Groupware 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 with
Permeable 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

20. Where SharePoint 2010
has strength for social

21. SharePoint is a toolkit with
“some” assembly required

22. Already used, which
removes another
disconnected service

23. Platform, tool, and
interface where other
work is being done.

24. Solid identity and formal
relationship platform

25. Information Across Horizontals
Div 1 Div 2 Div 3 Div 4
Packaging
Logistics
Marketing

26. Solid data
underpinnings

27. Do your SharePoint developers
know all they need to deploy an
optimal social intranet solution?

28. Do they have depth
understanding social
interaction, or are they
social tool “clickspert”

29. SharePoint Social
Developer Needs
• Deep SharePoint knowledge
• Interaction design strength
• Depth in complicated and complex
social interactions
• Social interaction design

30. Scaling and Functionality
D A - Personal Use
B - Serendipity
C
People Participating
C - Mature Social
Tool
B D - Complex Social
System
A
Actions
InfoCloud Solutions, Inc. - 2011

31. 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

32. Closer to Real Growth Curve

33. Build or buy a social intranet
solution as a best fit for
SharePoint 2010

34. Key Questions...

35. SharePoint experienced
developer with time?

36. Do you have developers
& designers with social
software development
experience?

37. Abilities to modify
SharePoint to customize
deeply if needed?

38. Are the social tools the
developers priority?

39. If one or more “no”
answers, it could be
well worth it to
consider options

40. Options...

41. General Advantages
• Advantages:
• Quick up and running social tools
• Optimizing more difficult elements is done
• Continual iterations and improvements

42. Built On Top of SP 2010
• Advantages:
•Data (metadata) integrated tightly with
SharePoint (bonus for search)
•Tight integration with SharePoint strengths
•One common platform

43. 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

44. Built On Top of SP 2010
• Newsgator
• Telligent

45. 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

46. 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

47. SP 2010 Plug-in
• Jive
• Socialtext
• Traction
• Socialcast (activity stream and
communication platform)
• Many more...

48. Mange Tak!

49. URL: http://infocloudsolutions.com
E-mail: thomas@infocloudsolutions.com
AIM: vanderwal
Skype: tjvanderwal
Twitter: @vanderwal or @infocloud
InfoCloud Solutions, Inc. - 2011