Your company has

SharePoint

but your team, your

department or your

entire company do

not seem to get

much value out of it

How can I make a difference

in such a big problem?

Change your process

Ensure long-term success

1. Be the role model 2. Be inspired!

Change your process

Ensure long-term success

1. Be the role model

- Mahatma Gandhi- Patrick O’Toole

“Be the change you wish to see in the world”

SharePoint^

1. Learn

2. Test functionality

3. Evangelize

4. Do the right things, always

1. Break up monotony

2. Find something fun every day

3. Think differently about your role

1. Technical support

2. Cost center

3. Disruptive

1. Problem solvers

2. Add business value

3. Innovative

“[Steve] Peltzman told me his job is…

being responsible for how we use technology

‘helping define and drive our business strategy, as well as

to ‘win, serve, and retain’ customers.’”

Change yourself

Ensure long-term success

1. Identify

problems

2.Solution

& build

3. Wrap

up

Change yourself

Ensure long-term success

1. Identify

problems

2.Solution

& build

3. Wrap

up

1. Identify

problems

2.Solution

& build

3. Wrap

up

1. Identify problems

Listen to your coworkers, Identify pain points,

Document and Prioritize your conversations

Why identify?

“Do not assume that anything you create will

provide value …for anyone”

Listen and identify

1. Ask the right questions

2. Listen for problems and dive deeper

Do not think about a solution yet

Listen and identify: bad questions

1. “What can SharePoint do for you?”

2. “How can we help you?”

3. “Would an approval workflow help you?”

Listen and identify: good questions

1. “Tell me about a typical day.”

2. “What tasks take you the longest?”

3. “What is most frustrating to you?”

4. “Tell me about the last significant issue you

faced.”

Listen and identify: good questions

1. “What are some of your short term (or long-

term) goals as a team, department, etc.”

2. “What parts of your strategy seem most

difficult for you to obtain?”

Document and prioritize

1. Document the problems you discovered

2. Take a guess at impact

Do not think about a solution yet

What to document

1. Stakeholders

2. Problem details

3. Success criteria

4. Impact (1-5)

1. Identify

problems

2.Solution

& build

3. Wrap

up

2. Solution & build

Spend time solutioning the problems your

heard, choose a single solution and build

Solutioning

Simple

Low

supportExtensible

Solutioning

Simple

Low

supportExtensible

1. OOtB

2. Create less

3. Limit changes

Solutioning

Simple

Low

supportExtensible

1. Will business

change?

2. Users/IT extend

3. Anticipate

Solutioning

Simple

Low

supportExtensible

1. You should not support

2. Over-document

3. Change behavior

Solutioning

Simple

Low

supportExtensible

Choose and build

1. Choose

2. In case of ties – select higher impact

3. Consider stakeholders

4. Build, test and demo

1. Identify

problems

2.Solution

& build

3. Wrap

up

3. Wrap up

Communicate value & review your solution

One pager

1. Business problem

2. Solution

3. Value

Elevator pitch

Be prepared to tell a 2-3

minute story about your

solution

...and USE IT

Setting

Characters

Conflict

Resolution

Results

Formally communicate value

1. Email (copy their managers)

2. Display on team site

3. Use elevator pitch

Review solution

Introducing Ad hoc governance

Creating and reviewing rules on a

solution-by-solution basis

Review governance policies: How?

Review

1. Features used

2. People involved

3. Processes created

Ask

Should any standard

rules be applied?

1. Document technical solution

2. Present solution details to a team member

3. Note any lessons learned

Change yourself

Change your process

Your work is just beginning!

1. Training plan

2. Support plan

3. Manage incoming request

Stick to your guns!

Explore future functionality

Anticipate big solutions

1. New features (Yammer, Delve)

2. Custom development

Slalom Consulting

University of Illinois

Capricorn

@OToolePatrick

Patrick O’Toole

The Problem: “Frustration” – Reuben Stanton

What Can I Do?: “Lazy dog” – Héctor García

Be the Role Model: “Leadership” – Pedro Ribeiro Simões

Identify: “Ehtsham & Alexander in Conversation” – Erik Ogan

Wrap-up: “DSC_2680 copy” – Philip Watts

Long-term success: “2010 Stanley Cup Champions Chicago Blackhawks Parade” – critiqual

Appendix

Simple (details)

1. Use out of the box features

2. Limit the amount of collateral

3. Limit the changes to the existing

environment (permissions, features,

etc.)

Simple

Extensible (details)

1. Think about how business

problem might evolve

2. Provide users with ability to extend

3. Anticipate additional requirements

Extensible

Low support (details)

1. Create an application that

requires little support from you

2. Do not change behavior

3. Provide documentation as needed

Low support