why sharepoint 2010 may not be the answer to the social intranet

Thomas Vander Wal - InfoCloud Solutions, Inc.2 March 2011

Intrateam :: Copenhagen

Why SharePoint 2010 May Not Be The Answer To The Social Intranet

Understanding social components and what is

needed to build an optimal solution

Social Tools and Fit

Social Activity Types

Personal

Collective

Community

Collaborative

BuildOrder

Identity Object

Presence

Actions

Sharing

Reputation

Relationship

Conversation

Groups

CollaborationElements ofSocial Software

BuildOrder

Identity Object

Presence

Actions

Sharing

Reputation

Relationship

Conversation

Groups

Collaboration

TraditionalGroupware

Social Progressions

•Sparks: Ideas shared

•Campfire: Gathering of others with interests

•Bonfire: Broader interest gathering

•Torch: Honing for broad use & replication

Comfortable Spaces with

Permeable Walls

The 4 rings of enterprise social tools

Tools

Enterprise Social Tool: Components for Success

Tools Interface /

Ease of Use

Enterprise Social Tool: Components for Success Capabilities

Tools Interface /

Ease of Use

Sociality

Capabilities

Intelligence &Business Needs

Enterprise Social Tool: Components for Success

Spheres of Sociality

Everyone

Collective

Selective

Personal

Tools Interface /

Ease of Use

Encouraging UseSociality

Capabilities

Expand Use &

Increase ROI

Social Comfort

Intelligence &Business Needs

Enterprise Social Tool: Components for Success

Where SharePoint 2010 has strength for social

SharePoint is a toolkit with “some” assembly required

Already used, which removes another

disconnected service

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

Solid identity and formal relationship platform

Information Across Horizontals

Div 1 Div 2 Div 3 Div 4

Marketing

Logistics

Packaging

Solid data underpinnings

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

Do they have depth understanding social

interaction, or are they social tool “clickspert”

SharePoint Social Developer Needs

• Deep SharePoint knowledge

• Interaction design strength

• Depth in complicated and complex social interactions

• Social interaction design

InfoCloud Solutions, Inc. - 2011

Scaling and FunctionalityPe

ople

Par

ticip

atin

g

Actions

A

A - Personal Use

B

B - SerendipityC C - Mature Social

Tool

D

D - Complex SocialSystem

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

Closer to Real Growth Curve

Build or buy a social intranet solution as a best fit for

SharePoint 2010

Key Questions...

SharePoint experienced developer with time?

Do you have developers & designers with social software development

experience?

Abilities to modify SharePoint to customize

deeply if needed?

Are the social tools the developers priority?

If one or more “no” answers, it could be

well worth it to consider options

Options...

General Advantages

• Advantages:

• Quick up and running social tools

• Optimizing more difficult elements is done

• Continual iterations and improvements

Built On Top of SP 2010

• Advantages:

• Data (metadata) integrated tightly with SharePoint (bonus for search)

• Tight integration with SharePoint strengths

• One common platform

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

Built On Top of SP 2010

• Newsgator

• Telligent

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

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

SP 2010 Plug-in

• Jive

• Socialtext

• Traction

• Socialcast (activity stream and communication platform)

• Many more...

Mange Tak!

InfoCloud Solutions, Inc. - 2011

URL: http://infocloudsolutions.comE-mail: thomas@infocloudsolutions.comAIM: vanderwalSkype: tjvanderwalTwitter: @vanderwal or @infocloud