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?
- People using SP 2010 have a great experience (especially the first time they use it).
- People are confident they can use it for what they need it for without experience problems.
- People don’t waste time calling the helpdesk because many problems have been prevented.
- Effective governance encourages early adoption and increased knowledge sharing.
- Costs spent preventing problems are justified by increased productivity and reduced risk of errors.
- People find registering difficult and lengthy because of extra steps taken to prevent problems and don’t bother.
- People find it too restrictive for their needs and it stifles innovation.
- People turn to other tools (maybe not approved) to meet their needs and ask other people for help to use them.
- Too restrictive governance prevents most beneficial use by raising the barrier too high for people to use SP2010.
- 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.