It would be great to hear what you consider to be in your top 10, please add a comment.
1.The all or nothing approach
Companies often endeavour to implement a full intranet site including Publishing sites, Team Sites, MySites, InfoPath forms, Business Intelligence and Document Management. An all or nothing approach. While these are great features, they can be overwhelming for end users when implemented all at once, not to mention the SharePoint team. And if they are not rolled out in a managed way, their impact falls short and you end up with lots of nothingness in your intranet.
For example, if someone has many deadlines and tasks to deliver, will they really go and update their MySite? Or even tag those documents correctly? Or even load those documents to the Team Site rather than just email them?
In order to create a successful SharePoint platform in your company, you need to take it step-by-step.
One approach we use in WebVine, is in addition to designing the intranet site, to create a number of small wins for departments also, for example setting up document management for the finance dept. Finance departments are very organised and methodical, and it’s easier to get metadata requirements from them, than from marketing for example. Then when you launch the intranet, showcase the library and have the finance team speak about the benefits of document management. You can do the same for with HR by building an Infopath form for them. And so on.
When people see the results, they become enthusiastic to follow suit, then start working with the remaining departments. You will have a much better chance of user engagement and success.
2.Implementing document management incorrectly
I have seen many SharePoint document libraries and I have rarely seen one that is done well. Often, using a share drive would offer similar benefits, aside from version control and the ability to send links instead of attachments.
If you are using SharePoint, then document libraries can offer tremendous benefits. However staff are not shown or trained on how to derive to most benefit from document libraries, and end up discarding them.
When you setup a library, the first thing to do is to run a workshop on how to design it. You need to capture the metadata that is applicable to the people using that library. For example, if you are setting up a library for the IT department, it will look different to the Legal department library. You also need to consider using content types and managed metadata in your libraries as these offer tremendous benefits.
With content types you can create a list of templates within a library, so if a user clicks ‘New’ they are presented with a list of predefines templates. If the templates are setup correctly eg a word document called ‘budget report’ then information entered in the word document can be captured as filterable metadata in the library. See below for a good and not so good example of a document library.
A better example of what a library should look like, no folders, filtered by metadata3.Just using SharePoint as a CMS
Implement SharePoint as an intranet site takes a lot of work. Especially if engaging a design agency, managing multiple stakeholders and creating a decent site design. Not to mention creating content. Unfortunately, the resources used to create the intranet site end up being the same resources used to maintain and update the intranet. If resources are limited (intranet resources are usually thin), developing the SharePoint environment further tends not to happen. So you have an intranet that cost a million dollars in licensing, that could have been delivered much more cheaply on another CMS. If you are not offering any value other than SharePoint being a CMS, what’s the point in using SharePoint?
Team sites, project sites, document management, process improvements, collaboration, reporting and more all need to be on the strategy plan (just not all delivered at once of course). Otherwise it’s one expensively run website you have sitting there.
To get these projects off the ground, you’ll need a good understanding of what SharePoint can offer your company, and executive level support (see point 8). Ensure you get this support up front and create a SharePoint strategy that delivers decent ROI.
Then you will maximise your SharePoint investment.
4.Lack of SharePoint expertise in the organisation
Making a SharePoint project a success has many facets. Organisations rely completely on their staff to get projects over the line. But what happens when you don’t have enough knowledge in the project team? Quite possibly the team doesn’t even realise it.
For example, SharePoint is pretty easy to install. But if the administrator doesn’t understand the effect of version control, archiving, records management, and a whole lot more, then the site can come to a grinding halt within 12 months.
Understanding how the SharePoint environment will be used and planning for that up front is crucial.
Also, organisations tend to deploy collaboration features and expect people to use them. But soon after find empty MySites and discussion groups 1 thread deep. Having SharePoint technical understanding is not enough; you need a plan to ensure adoption in the organisation. Once people see empty pages, they tend not to come back.
Try to find lessons learnt from other companies, attend conferences, do your research, and get external assistance if you need to.
5.Missing out on key features completely
You don’t know what you don’t know. As a result, there are fabulous gems within SharePoint that are easy to implement, but are often missed. These features make a real difference to organisations, releasing people from repetitive tasks, so they can actually do productive and enjoyable work.
Custom lists, workflows, content types and forms are awesome and can transform the work culture of a company.
If you are still sending around lots of excel spreadsheets, then it’s likely you are missing out on at least one key feature. Custom Lists are a fantastic way of sharing information and getting rid of those excel documents. You can import an excel document and save it as a list to start with, then you can modify the list. For example setting a date field to default with today’s date. You can set alerts on the list, so if someone updates it, everyone on the alert is notified.
You can create different views of the list, so the manager (on the manager dashboard page if desired), sees the high level information only.
You can easily filter information on the list, for example I only want to see information related to NSW and status of urgent.
You can share information with other lists, for example if I have a column of projects and that appears in 2 different lists, I can create a look-up list to populate both lists.
The possibilities for more collaborative working between people and teams are endless – just using custom lists.
And there is plenty more that SharePoint can offer. So get under the hood, find out how to use these features, and ensure you utilise these in your organisation.
6. The gap between IT and the business
Business users rely on IT to inform them of what they can do with SharePoint. However, I have spoken to many SharePoint administrators who admit they do not to tell their business users about key features as they don’t have the time to help them use this functionality. IT also rely on the business to give them requirements, however, if the business don't have the information to know what is possible, they won't know what to ask for. As a result the business may ask for things that are difficult, costly and time consuming to develop.
So there is this information gap. This gap as many people know can lead to frustration, disagreements and a lack of understanding on both sides.
Perhaps a middle ground may have been found if both sides spoke the same language. Configurations to SharePoint can be made without requiring IT's involvement, with the correct knowledge and permissions. Business goals can be created and met if people actually understand what SharePoint can do.
Have knowledgeable SharePoint people in your team that know about SharePoint's features such as InfoPath forms, lists, libraries, search customisation, the many webparts available, personalisation and more. So they can persuade IT to make some of these features available and IT can be relieved of the burden of doing everything.
7. Assuming staff will automatically use SharePoint
Companies that do not engage their staff in how SharePoint is going to benefit them, soon discover a few issues. It's nice to have a nice looking intranet site with news posts and maybe a yammer feed, but is that it? SharePoint is not just a technology solution; it brings about a completely new way of working. People need to be educated in this new way of working together, step by step. Champions need to be found on a grassroots level, and real business benefit needs to be demonstrated. And people won’t get it without guidance and understanding ‘what’s in it for them.
So, in order for people to really appreciate SharePoint, they need to see how it can remove those ‘daily grind’ tasks. This is where SharePoint really comes into play.
* That report that Jo has to email every week to 20 people and then collate answers into a single document can be easily done in 1/10th of the time without Jo having to move.
* Shelley no longer has to email people when she updates certain documents; they are automatically alerted.
* That list of vendors that is somewhere in the file share is now actually accessible, sortable and easy to get to.
* The Finance manager sees updated live finance data at anytime on his customised home page, without having to request the information. When you give people back their lives through freeing up their time, they love SharePoint, in addition they are much more productive and happy.
8. Executive level support and understanding is not there
In order to transform how an entire organisation manages information, you need executive level support. Otherwise you won’t get the funding needed to go the whole way. Key stakeholders and people in roles like sales will not see the benefit to harnessing and accessing knowledge in the organisations. They are more focussed on external results, not streamlining internal processes.
However, you don’t want to let that derail the SharePoint project, as transforming how people work has tremendous benefits to the company.
If the CEO is aware of these benefits and wants the see them realised, then it’s a lot easier to get SharePoint over the line, and delivering tangible results.
After all, who wants to be left in the dark ages using shared drives and email and continuously losing information. So when the right people can convey a clear message to the executive team of the importance of SharePoint to the organisation, the project has a much better chance of success. Make sure you have those people in your organisation, and if you don’t have them, get some help. For some reason people really value external consultant’s opinions, even if internal staff convey the same message, so consider hiring them even for this pitch alone.
9. Leaving out Search until the last minute
Many SharePoint implementers do not consider SharePoint Search until the launch, like an afterthought.
However, Search is a very important piece in the SharePoint pie, and if it’s not configured well, will not deliver accurate results. The more help you can give SharePoint up front, the more satisfied people will be with the results. And they really do expect Google at their fingertips, after all, that is what they are used to.
Setting up managed metadata or tags so that you can filter results needs to be decided early on, otherwise at the end when you have already configured all of your lists and document libraries, it’s too late.
For example, if someone can filter the results by department, topic, region, job role, or whatever filters are most suited to your content, that will be incredibly helpful in searching SharePoint. So understand Search from the outset, take it into consideration, create a Search strategy and implement it. You will benefit from the importance of getting Search right in SharePoint.
10. SharePoint sprawl and incorrectly setting up the environment
If SharePoint is not governed well, it can lead to a plethora of Team Sites and even publishing sites in an organisation. This sprawl leads to a very unstructured intranet, which soon becomes unreliable. People get lost in numerous sites and lose faith in the integrity of the intranet, and this kind of sprawl can lead to deterioration in server performance.
Very often, SharePoint environments are not configured optimally. Someone installs SharePoint, which can be done fairly easily, and away they go. I have seen a number of companies with large SharePoint environments, relied on by thousands of employees, have their environments crippled due to a poor foundation. A lack of understanding at the infrastructure level, and in configuration, can leave SharePoint farms running slowly, giving a poor user experience, a bad name for SharePoint, and even worse, can grind to a halt.
So ensure you have people who know what they are doing when initially setting up SharePoint, who can take into account the volume of data likely to be reached in a number of years, the number of users accessing the system, and many other key factors.