A SharePoint 2010 strategy to prevent problems

In my last two posts I have covered the benefits and drawbacks of SharePoint 2010′ restricting use and encouraging best practice and how this fits with a great governance strategy.

I will now cover the benefits and drawbacks of preventing problems with SP2010 features.

You need to get your strategy right and what it is you want to achieve.  Is it encouraging innovation and keeping governance light touch?  Or is it to prevent the ‘wrong’ behaviour and minimise risk of your brand and reputation being damaged?  How much do you want to spend preventing problems?  What does your cost/benefit analysis show?

Benefits

  1. People using  SP 2010 have a great experience (especially the first time they use it).
  2. People are confident they can use it for what they need it for without experience problems.
  3. People don’t waste time calling the helpdesk because many problems have been prevented.
  4. Effective governance encourages early adoption and increased knowledge sharing.
  5. Costs spent preventing problems are justified by increased productivity and reduced risk of errors.

Drawbacks

  1. People find registering difficult and lengthy because of extra steps taken to prevent problems and don’t bother.
  2. People find it too restrictive for their needs and it stifles innovation.
  3. People turn to other tools (maybe not approved) to meet their needs and ask other people for help to use them.
  4. Too restrictive governance prevents most beneficial use by raising the barrier too high for people to use SP2010.
  5. Costs of preventing problems are higher than benefits to be gained and not justified.

Again, I’d really like to hear about first-hand experiences dealing with these points/decisions and what trade-offs you had to make.  My next post will cover aligning your SP2010 strategy with your business strategy.

7 responses to “A SharePoint 2010 strategy to prevent problems

  1. Pingback: Aligning your SharePoint 2010 strategy with your business strategy « Mark Morrell

  2. Pingback: Moving to SharePoint 2010? Define your stakeholder strategy « Mark Morrell

  3. Pingback: SharePoint 2010 special interest group « Mark Morrell

  4. Pingback: BT Intranet SharePoint 2010 examples « Mark Morrell

  5. Pingback: Measuring the value SharePoint 2010 can bring to your organisation « Mark Morrell

  6. Pingback: It’s how you use SharePoint 2010 that decides the value it brings « Mark Morrell

  7. Pingback: SharePoint 2010: the human dimension « Mark Morrell

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s