Keeping things simple to ensure SharePoint success

January 25, 2012 —  (Page 3 of 3)
Another thing to consider is that the complex functionality often takes more time to implement. Spreading that functionality into phases allows stakeholders to see things sooner. It normally makes a project go smoother when functionality can be rolled out for people to start using sooner as opposed to later. This approach also makes it easier to make small course corrections along the way as people start to use the functionality, which tends to lead to a better product in the long run.

It seems like it wasn’t that long ago that I did my first SharePoint project. I’ll never forget when my boss walked past my cube, clapping his hands and shouting, “Who wants to do SharePoint?” That person ended up being me. Things have turned out pretty well, but I learned a lot of hard lessons during that first project—many of which I’ve shared in this short article.

I’d be interested to hear from readers about these tips or others that they give. You can find me on Twitter:

John Ross is a SharePoint MVP and Senior Consultant with SharePoint911. He has over eight years of experience implementing solutions for clients ranging from small businesses to Fortune 500 companies, as well as government organizations. John is coauthor of the books “Professional SharePoint 2010 Branding and User Interface Design” and “Real World SharePoint 2010: Indispensable Experiences from 23 SharePoint MVPs.” Visit his blog at

Pages 1 2 3 

Share this link:

This site's content Copyright © 1999 - 2014 by BZ Media LLC, All rights reserved.
Legal and Privacy
Phone: +1 (631) 421-4158 • E-mail: