<p>As a consultant I get to work with clients to help them roll out new installations of SharePoint or create new projects on top of existing implementations. I also get called in to help with existing SharePoint implementations that aren't being used. Either people didn't adopt it, the company did not get all their content and business processes created, or they just never rolled out the platform to the end users.</p><p>One of the first things I do is ask why employees aren't using their current SharePoint implementation. You need to understand all the reasons why to take steps to mitigate that from happening again.</p><p>I usually get a range of responses. This definitely isn't an exhaustive list, but rather some of the most common explanations that I hear. Some clients are even guilty of two or more of these infractions:1. Lack of Vision or Clear Plan</p><p>Failing to plan is a recipe for disaster. Many companies think of SharePoint as simply a product that you install on the server and then everyone will just start using it. That couldn't be further from the truth. SharePoint is not a single product, it's a platform that can do a number of different things. And while every company probably has a few similar processes and use cases, they also all have their own unique needs. If an organization thinks they can just install SharePoint without a plan, or they don't attempt to tailor it at all for their needs, it's not going to bring very much business value. And any system that doesn't provide business value probably isn't going to get used.2. Lack of Time and Resources</p><p><a href="http://www.cmswire.com/cms/social-business/4-common-reasons-sharepoint-projects-fail-024730.php">Keep reading...</a></p>