SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Governance is something that companies tend to think about on their second implementation of SharePoint.

Sometimes you have to go through the pain of difficult navigation (without a defined information architecture), tons of out of date content (without a content retirement policy), or searchability nightmares (after dumping gigabytes of unstructured data from a fileshare into SharePoint) to understand the value of a planned approach as opposed to a wild-west greenfield deployment.

There are certainly some templates from the likes of Joel Oleson and Paul Culmsee at the Governance Resource Center on TechNet, but dropping a 50 page governance document on a team that hasn't worked with SharePoint before will just cause eyes to roll back in heads.

Are there any useful strategies for communicating the importance of building even basic governance into a SharePoint implementation?

share|improve this question
Even 50 pages seems light for all the governance you could talk about for SharePoint... – Kit Menke Apr 12 '11 at 19:41
I'd agree, considering some of the documentation out there if it's 50 comprehensible pages I'd find that a bonus. – MichaelF Apr 13 '11 at 12:30

Here's my 2 cents on governance: If you don't create a governance document, then your governance is "Ok everyone Free for all!" and you know how well that works.

I would start small and at least get them to help define the way new sites are created, this will get them to see that there is so much more to think about than just implementing SharePoint and installing it on servers.

For instance, if you create a site, you have to think about(not all inclusive): 1. What URL to use (where it falls in taxonomy) 2. What site template to use 3. What features to activate 4. Who can see/use the site 5. How security (the stuff you talked about in #4) will be managed 6. Whether or not the site can be searched 7. What colors/branding will be on the site 8. Whether or not SharePoint Designer can be used on that site and who can use it. 9. Whether the site will inherit navigation (if site collection, if it will have a portal site connection) 10. What the content of the site will be

And this is just the tip of the iceberg, you can get even further down, but just getting them to realize the basics of what goes into creating a simple site will make them stop and think that without some proper planning, you'll end up with a big mess.

I hope this helps.

share|improve this answer

Check out :

Business-Centric Portal Strategy for running successful Sharepoint Projects

share|improve this answer
Sure, this is a wiki so the requirements on the answers are lower than usual, but to just leave a link to a blog post by yourself without leaving any of the details in the post is not really how we like it! – Robert Lindgren Jan 23 '14 at 10:30

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.