The changing face of SharePoint Adoption

Andrew Woodward

A brief historyWe all come from somewhere, with our own experiences.

SharePoint 2003 / WSS V2• Web Parts• Lists and Libraries• Portals• Search

SharePoint 2003 / WSS V2We liked

• Simple team sites• Building Corporate Portals• Search and People• People did use it!

We did wrong

• Too much development• Under the desk deployments• Little or no training and governance

MOSS 2007 / WSS V3• Office Integration• Web Content Management• Workflow• Wikis / Blogs• Business Intelligence• BPOS

MOSS 2007 / WSS V3We liked

• Document and Records Management• Business Intelligence• Workflow• BPOS (for a few…)

We did wrong

• SharePoint Designer• Upgrades• Too much development• Still limited or no training and governance

SharePoint 2010• The Ribbon• Major architecture changes• Social…• Managed Metadata• FAST Search

SharePoint 2010We liked

• Improved Development story• Improved services architecture• Managed Metadata• Social features (some)• FAST (for some)• Office365 (for some)

We did wrong

• SharePoint Designer• Too much development• Push from IT• Complex architecture• Information Architecture• Internet sites!

SharePoint 2013 / Office365• Social – then they bought Yammer!• Search – FAST baked in• Skydrive

One Drive for Business• Usability• Mobility• Office365

SharePoint 2013 / Office365We liked

• Web Content Management• User Interface• Search• Social<< Yammer!• App Model• Office365 (for some)

We’re doing wrong – but there’s hope

• Social• App Development• Adoption• Information Architecture

Consider…

200 million users in 2008

Launched 2010

It was 3 years before a new version of SharePoint was released… during which time we had the iPad 2, iPad 3, iPad 4 and Mini

1.2 billion by 20131 billion people adopted a new technology in 5 years….

Interesting

Google search trends

AdoptionWith all this change?

Traditional..• Cycle of change… 3 years… more?

• IT Driven?

• No clear ‘What’s in it for me’?

• What hope did do users have!

We tried..• Lots of talk of Governance• End User training• Lots of good books• A SharePoint Centre of Excellence

• But the results never really Wowed!

A way to think about people..Always going to adopt, they are the ninja’s, the champions – support, encourage but don’t spend too much time here

Not quite there, they may not know what it is. But they won’t resist the change, sceptical but open. These are the sweet spot for your efforts

Resistant to change. They may not get it, may be disagree or just not be ready to change. Don’t waste time here, let their network of yellow dots encourage change.

We tried… (2)• But we took a product feature approach

• Question: Records Management

Typically Red, Yellow or Green dots?

Change happensIts the only constant.... But its getting much faster

Yammer Changes

FeaturingDaily releasesA/B testing

https://about.yammer.com/success/engage/grow-your-network/release-schedule/

Office365• Regular releaseshttp://community.office365.com/en-us/w/office_365_service_updates/default.aspx

• Sustained engineeringhttp://blogs.technet.com/b/office_sustained_engineering/

Challenges• How do you support?• Training and guidance?• Testing?• User Experience?

Approach• Build Community• Be the tummeler, start a movement• Remember the dot’s• Small changes

What’s in it for me?

THANK YOU