This is the third post of a six part series that provides important considerations for your SharePoint implementation project plan. I’m not claiming there are ONLY 6 considerations, or that these are definitively the 6 most important, but I am claiming they’re important enough to be pretty darn close to the top.
Consideration 3: A word on governance
Not long ago, the trend I saw on SharePoint implementations was that governance was completely overlooked. Apparently word has sufficiently circulated through the community that governance is critical. “Your SharePoint implementation won’t be successful without good governance” you read in sternly worded prose on best practice documents. Now, governance appears to be something that most implementers are at least thinking about.
The new big question when it comes to governance is how to do it properly. The default trend of governance policy appears to be a very heavy focus on the governor. “Thou shalt do this” and “Thou shalt do that”, entombed in voluminous sheafs of documents sure to never be reviewed by anyone. Their dense prose, strict edicts, and sheer volume ensure that.
Proper governance is a subject well beyond a short blog post. But here are three points to get you thinking in the right direction:
- Satisfy legal /regulatory (SOX, etc.)
- Think about the Governor(s)
- Think about the Governed
Points 1 and 2 seem to get great attention by default. My recommendation: don’t forget about point 3. Think about the governed. Build a governance policy that, if not in whole at least in parts (organize well – these are perhaps the only parts anyone will ever read again), thinks from the standpoint of the governed.