Don't Toss the Grenade Over the Wall! It Will Blow Up!

I attended a presentation at the Mindsharp Best Practices Conference titled "Understanding Change, Power, and Conflict in Your SharePoint 2007 Deployment." The presenter was Mark Schneider who has over 30 years experience specializing in strategic technology planning and governance.  He really knocked the ball out of the park on this one.  Having been a SharePoint administrator for many years previously, he really brought to light why many SharePoint deployments fail and the preventative steps you can take to avoid this from happening.

First of all, SharePoint is a disruptive tool.  It changes your business and threatens your end users.  Fact of matter, workers DO NOT LIKE CHANGE.  SharePoint implementations will directly affect both your business processes and your people that perform them.  And what do your people really care about at the end of the day; paying their mortgage and feeding their families.  This new way of doing business and process changes really need to be balanced to keep social order within the workplace.

How Do You Make This Change Successful?

  • Get a Powerful champion (CEO or high-level business sponsor)
  • Get Grassroots support (make sure they know you aren't out to make their jobs harder)
  • Make sure your budget is Approved and Funded
  • Document clear and objective goals
  • Maintain control over the project

What Do You Do When Your People Perceive SharePoint as a Threat?

  • Identify how your organization will react
    • Identify your opponents (they are least likely to adopt)
    • Determine your opponents needs and make sure you meet them
    • Invite your opponents to initial planning activities (this will give them a sense of ownership)
    • Always be humble and invite criticism
  • Fail on the whiteboard, not in production

What Are Some Tactics to Remove SharePoint as a Threat?

  • Training, Training, Training - end-users, power-users, champions, IT
  • Blogs - get your champions and power sponsors involved
  • Examples - start with a small department and show your end users how SharePoint works and why it's beneficial to them
  • FAQs - invite and accept all
  • Testimonials - take every chance you can to promote positive experiences
  • Dialogues - maintain open lines of communication around your project and be very candid

OK, so we've mitigated the threat of SharePoint as something that IT is just going to throw over the wall, users won't like it or adopt it, and its just something that the company has wasted more money on...at least we've attempted to mitigate this.  Now let's understand some other tactics that need to be put in place to make your deployment a success, such as governance and an effective communication plan.

How Do You Establish Collaborative Governance?

  • Establish a team across the organization - get high-level business user, information workers, etc. involved
  • Review planned changes from a variety of perspectives - everyone does business in different ways, understand this
  • Get input and ownership from all groups impacted by the change - no surprises
  • Ensure you have awareness and advocacy within impacted groups
  • Gain trust from all groups impacted - remove the "us vs. them" mentality

How Do You Establish an Effective Communication Plan?

  • Over communicate - you can never provide enough information
  • Always provide candid responses to questions - don't hide anything
  • Communicate any problems before others find them - OK, so there's a problem, but you've still that trust level established
  • Always have answers for why changes are being made - don't just use the IT knows best excuse
  • Have applicable and understandable answers to the "What's In It For Me?" question - this will go a long way

So, in review, the following steps will aid in a successful deployment and increase end-user adoption for your new SharePoint deployment:

  1. Over communicate
  2. Keep your plans sensible
  3. Establish an effective governance team
  4. Training, Training, Training

Here's an excellent Microsoft-provided resource to get you started:

GEAR Up
"GEAR Up is an online content tool that will assist IT professionals and business managers to find timely resources and guidance through phases of a typical SharePoint Server 2007 deployment cycle: Get Ready, Engineer, Adopt, and Release.  Each phase relates to end user adoption of SharePoint Server 2007."


Posted Sep 17 2008, 01:57 PM by Jeremy Minich

Comments

C. Hansen wrote re: Don't Toss the Grenade Over the Wall! It Will Blow Up!
on Wed, Sep 17 2008 3:12 PM

Great article - sums up the deployment challenges in an easy to read manner that can be readily consumed across multiple target audiences.

The GearUp link is actually well done in terms of Launch prep.

Having gone through this a number of times, I have rarely seen SPS/MOSS launches go well. The #1 reason why they fail? IMHO, poor sponsorship and lack of planning.

70% of successful MOSS deployments are discovery, planning and communications. 30% is design and implementation.

To do this effectively, you must:

1. have adequate sponsorship to secure the personnel required -  whether that be outsourced, insourced or hybrid.

2. have adequate resources in the operational space to build a multi-tiered SDLC around the platform technolgoies, with a strategy for Dev, Test, Auth and Pilot

3. have scope control boundaries - MOSS can quickly become a lot of things, but decide up front if it's your solution for all of your web channels, or one particular channel  ( Intranet / Extranet / Internet  and/or LOB apps).

4. you must have adequate boundaries around roles and responsibilities - you don't want your PM being your Architect, or your Tester being your Dev Lead.

5. you must have a program manager - there are as many (if not more) non-technical decision that need to be made as technical ones.

6. you must have the capability to handle work inflow from across the enterprise - this requires a plan + a tool

7. you must have cooperation with whoever is in charge of your Brand and image

8. you must be able to perform work once you launch - in other words, technology insertion does not address dev factory (SDLC)

9. you must have operational alignment with your Ops teams - technology insertion does not assume an operational support system is ready and performing.

10. you must have tools - add ons that provide rich features that you could spend eons coding (if you had the talent) but for pennies on the hour you could buy one and include it ni your baseline product offering - these are varied, but the ones I liked are in backup/recovery/DR and reporting dashboards.

11. you must have a means for communicating the health of the platform and doing trend analysis to provide informaiton to sr. managers and executives - or risk getting your funding squashed (which you'll need ongoing).

Having stood up a number of MOSS implementations at the enterprise level over the years, these are my "truisms".

By and large, Execs and Directors just do not understand the levels of committments needed in terms of funding and personnel to implement successfully in an enterprise environment. 6 times out of 10, SharePoint enterprise implementations result because some guy in IT decided to install WSS and then got some guts and stood up a VM with SPS or MOSS on it - and it grew...and grew...and grew....until (holy-smokes) it was ta-da...a production system-whether intedend or not.

The amount of IT and non-IT personnel to make the launch of an Enterprise platform a success is significant; 10x if you're going to use it as an enterprise dev platform across multiple channels.

Sadly, I am standing up a new MOSS implementation for my current employer for 40k personnel. I have a team of 2, including myself, and the other person is our home-grown SharePoint admin. Think we'll be successful?

The Bamboo Team Blog wrote September e-news in a Nutshell
on Fri, Oct 3 2008 5:53 PM

If Einstein were alive now, he would definitely think our company wasn’t aging because we are moving

Blogs

See you in San Francisco!

Register for SPTechCon

Subscribe by Email

Syndication

Bamboo Nation Now on Twitter

Bamboo Now in Alltop!

        Featured in Alltop

Blue Rooster Cycling

Bamboo is a proud sponsor of the Blue Rooster Cycling Team.
Blue Rooster Cycling Logo

Bamboo Solutions Corporation, 2002-2010