2014 SP Summit Vancouver Bottom Up SharePoint

Building Your Intranet From

The Bottom UpDavid C. Broussard– Principal Consultant, Catapult Systems

www.sharepointsummit.org

What is an

Intranet?

2


The four verbs of the Intranet

Intranet

Engage

Produce

Innovate

Decide

3


How have we always built them?

4

Landing Page

Division Front Doors

Department Collaboration

Ad Hoc Collaboration

OneDrive for Business

Messaging

Collaboration

Governace


But…it takes so long

• Top Intranets take time, people, and money

• Average Development takes almost 2 years!

• Average Team Size is 18 people• Designers

• Authors

• Developers

• Etc.

• Total cost over $1M• Mix of internal and external staff

• Cost of servers, licenses, salaries, etc.

80% use SharePoint

5Nielsen Norman Group – Intranet Design Annual 2013


A highly structured

organization is at risk of becoming

irrelevant in a quickly changing marketplace…

And it’s hard to change


True or False?

• The Landing Page is the Most Important Page in the Intranet?

7


What matters most to the user?

8

"Product successes and failures have shown repeatedly that users don't care that much about features. Users only care about achieving their goals."

-The Inmates Are Running the Asylum, Alan Cooper


Focus on the

Landing PageThe traditional approach…

9


What is the Landing Page?

10


What is the Landing Page?

Is the purpose of a landing page a place where the user can accomplish something, or a place where they find a link to accomplish something?

11


The Pyramid of SharePoint Value

12

Landing Page






The Information Portal as Landing Page

13


Case StudyHEB Grocers – Information Portal


HEB – Regional Grocer

15

Scenario:

• 60,000 users across many locations

• Onboarding process is unique for each job level

• Security of information is essential.

Need:

• Personalized portal for each of my users where they can find life event information, benefit forms, online training and access to other applications quickly and easily.

• Especially for the Store Leaders because they manage all types of employees.


HEB Regional Grocer

16


How does it get

built?Traditional Top Down

17


MSF Waterfall Approach – In Theory

Envisioning• Vision/Scope

Document

• Project Plan and Schedule

Planning• BRD

• TSD

• Governance

• Test Plan

Developing • Code Assets

• Test Scripts

Stabilization • Test Results

• Training

Deploying•Deployment Guide

•Project Close-Out


MSF In Reality

19

Envisioning

• Vision/Scope Document


Planning• BRD

• TSD

• Governance

• Test Plan


• Test Scripts

Stabilization• Test Results

• Training

Deploying

• Deployment Guide

• Project Close-Out


So, what’s the big issue?

We know that building an Intranet is hard, expensive, and takes a long time…so why don’t we just deal with it?

Can’t we just tell management that they need to give us $1M+ and 18+ months and trust us to deliver value at the end?

How do we show value faster?20


A New ApproachBuild from the Bottom Up

21


What are our Goals?

1. Deliver Business Value Rapidly

i. The Business needs to see value from Day 1

ii. Value must map to existing strategic goals

iii. Goals will change and thus our Intranet must be adaptive

2. Lay a foundation for future growth

i. We cannot design our way into a corner

ii. Each portion of the Intranet needs to be “part of the holistic solution”

iii. Each portion needs to stand on its own


Oh, well, that’s simple then…

23


Canadian Pacific Railroad Approach


Top Down and Bottom Up

25

Landing Page






Turning This…

26

Envisioning

• Vision/Scope Document


Planning• BRD

• TSD

• Governance

• Test Plan


• Test Scripts

Stabilization• Test Results

• Training

Deploying

• Deployment Guide

• Project Close-Out


Into This…

27

Envisioning

Planning

Developing

Stabilization

Deploying Planning

Developing

Stabilization

Deploying

Planning

Developing

Stabilization

Deploying


Bending the Value Curve

Day 1 -OneDrive

Month 1 – Ad Hoc Sites

Month 2 –Department Sites

Month N –Continual Improvement

28


Coming all together…

29

Landing page

Functional Areas

Perm Collab


Personal Collaboration


What does the journey look like?

1. Define the Vision

2. Map To Value

3. Work the Solution

4. Evaluate, Adapt, & Iterate

30


Practical

ExampleOil and Gas Services Company

31


Oil and Gas Services Company

32

Scenario:

• 3,000 users across many locations, 700 Information Workers

• No “owner” for intranet

• Currently on SharePoint 2003 with unstable farm

• Own Office 365 E1 Plan for 700 users

Need:

• Promote culture of Safety throughout company

• Provide reports to decision makers throughout the company

• Must get off unstable farm

• Build momentum with quick wins to gain traction across the company


Define the Vision

• Work with the business to identify the strategic drivers for the Intranet

• Meet with end users to find out how they work, what their goals and needs are

• Create a vision for the project that the client agrees on

“We will create an information workplace for our users allowing them to share knowledge and work efficiently”

33


Map to Value

• From the user interviews we will build User Stories that define their normal tasks and activities

• These stories will be ranked for importance to the company and project

• Each User Story will get a work estimate

34


Work the Solution

• Identify the Top ranked User stories that fit into the first iteration

• Team will work the list items daily

• If an obstacle can’t be cleared, put item on hold and move to the next one

• Goal is to deliver early and get feedback from the end users

• How big or small can a unit of work be?

35


Evaluate, Adapt, & Iterate

• As each iteration draws to a close two things must happen

1. Each item worked on must be deployed

2. Next Iteration must be planned

• User Stories can be added or removed

• Priorities can be changed

• Delivered work is monitored for adoption and potential improvements

• Overall solution is re-aligned with goals36


Wrap Up


Pros and Cons

Pros:

• Delivers value faster

• Allows for changing priorities

Cons:

• More difficult to manage process

• Easy to lose sight of the “big picture”

38

Thank you for your attention!This presentation will be available on the

Vancouver SharePoint Summit website a few days after the event.

Please rate this session!Fill out the survey form

2014 SP Summit Vancouver Bottom Up SharePoint

Technology

Transcript of 2014 SP Summit Vancouver Bottom Up SharePoint