If your company has invested in SharePoint, they have likely put a lot of time, money and resources into its acquisition and deployment. Yet many companies are not realizing the return that they could be on their sizable investment.
Most companies do not understand the plethora of features that are available to them, nor how to best leverage the platform to maximize their investment. Most are guilty of one or more of the following:
- Underutilization of features
- Lack of clear requirements or vision
- Not using metrics to gauge feature usage and adoption
- Understaffing to properly support the platform
Underutilization of Features
One of the main pitfalls with SharePoint is that many organizations use very few of the features. SharePoint is such a vast platform, offering a huge array of rich features and functionality; however, few companies are taking advantage of all that SharePoint has to offer.
Many companies use SharePoint as a glorified file share and don’t take advantage of metadata or content types to classify and better organize their information. Other advanced features, such as personalization, workflow, reporting services, InfoPath (although in retrospect, that may not be a bad thing since there will be no more future releases of InfoPath), and mobile and social features aren’t being used as much as they could be.
Joe Herres, executive vice president, products and services of H3 Solutions, says there are a few reasons why some organizations are reluctant to deploy mobile features.
The biggest hesitation is security and figuring out how to lock it down. The second is budget -- everyone wants mobile, but nobody's putting budget to mobile. Or they have directives to investigate then mobile falls in priority.”
Social features are another area of concern for many companies. Vlad Catrinescu, SharePoint consultant and co-founder of SP24: The 24-hour virtual SharePoint conference, regularly deals with these worries with his clients.
From my experience, I think that companies are still afraid of the whole enterprise social idea and not all of them encourage it. I had companies that welcomed the idea and found it awesome, while others requested custom permissions on the SharePoint social features so users could do nothing.”
As far as some of the other underutilized features, companies simply just don’t know about them.
Lack of Clear Requirements or Vision
As with any software implementation, not having a clear vision or specific requirements defined can lead to a launch failure. And if people aren’t using what little you have deployed in SharePoint because there was no real plan in the first place, then it will be hard to justify adding more features or functionality.
There also needs to be a good reason to implement a particular feature. When planning to implement SharePoint mobile features, for example, the main drivers seems to be behind culture, not behind the need. According to Herres:
A lot of the need for mobility comes from mandate. The CIO says we want to be mobile. But you need to ask questions. Why do you need mobile? What does mobile need to do?”
People won't adopt SharePoint unless it solves their problems, so figuring out exactly what those problems are and taking time to define use cases is key.
Not Using Metrics to Gauge Feature Use and Adoption
If you don’t know which features your users are (or aren’t) using, then how can you suggest improvements or changes? And how can you measure the successful adoption of SharePoint if you aren’t defining goals and measuring them?
Admittedly measuring ROI can be a challenging endeavor. But a lot of companies just aren’t making any real effort to do so.
Understaffing to Properly Support the Platform
A huge issue in my opinion is that companies are not staffing well enough to properly support the platform. SharePoint is not a product like Word or Excel that only performs limited function; it is an Intranet, a content management system, a collaboration hub, a search center, a knowledge base, a blogging platform, a reports and KPI center, a workflow engine, and much more.