The term “failure” is a harsh word. Regardless of how you may view the term in your personal or professional life, in SharePoint terms, I equate the word failure to “any SharePoint implementation that does not meet its full potential within an organization.” For those of you who know me, you know that I have very high standards for both myself, and my work. When I think about SharePoint Implementations over the past 7 years, the word failure jumps to the forefront of my mind. This action occurs because it is only on the rare occasion, that I see an implementation of SharePoint meet its true potential within an organization.
I believe that most SharePoint implementations failto meet their true potential) due to a series of pitfalls. From my real-world experience, some of the most common causes for a failed SharePoint implementation orbit around the following:
- Inadequate resources to support the implementation
- A lack of planning
- Improper expectations as to SharePoint’s role within the business
I am not one to simply point out a problem without also providing supporting details around a solution. This blog doesn’t simply complain about a problem. It offers a solution as well. Through a series of blog posts on the topic of why SharePoint implementations fail to meet their true potential, I’ll be explaining common pitfalls, discussing real-world history, and explain the impacts these pitfalls can have within an organization’s SharePoint implementation.
From here on out, I’ll try to explain things from the perspectives of both the SharePoint administrator, as well as a business owner. Finally, I’ll provide possible avenues for improving upon these pitfalls and provide guidance as to how these problems can be avoided in the future.
Click here to read the next post in this series.
Stay tuned!
mpassannante