Many people have asked me if I think SharePoint is ‘good’ or ‘bad’? It’s a great question to ask but it is harder to give the right answer based on my experiences with SharePoint creating strategies, leading project teams, implementing governance frameworks or just using the many features.
I have seen with each SharePoint version – 2003 to 2013 – how some new features help but other features can hinder how an organisation needs to use it….but one thing is clear, Microsoft don’t package up ‘good’ or ‘bad’ versions of SharePoint.
I believe it is how an organisation implements SharePoint that helps you feel if it is good or bad.
Here are five factors that can help you decide if SharePoint is ‘good’ or ‘bad’:
It is important you have a strategy for your intranet or digital workplace that SharePoint can be shown will help to achieve. A strategy helps set the direction you are moving in. It helps identify key priorities you need to achieve to help your organisation. Timescales also help to manage expectations and show what is practical from what is aspirational.
You should not just have a SharePoint strategy. That can lead to you delivering technology solutions that don’t meet the aims of your organisation or cover wider aspects of cultural change. Your strategy must not be based on SharePoint: it should be wider and align with your organisation’s overall strategy and related areas e.g. IT, Comms, HR, etc. and measure the benefits.
You need to have a governance framework that underpins your strategy in the long and short term. This means having clear roles and responsibilities, linking these together into a hierarchy with publishing standards, training and processes for new content editors.
Without a governance framework people could be unclear on the purpose of each SharePoint tool e.g. MySite, TeamSite, and how is the best and most appropriate way to use them. Without a governance framework there can be chaos and a digital mess that can be very difficult to untangle and gain any benefit from for a long time.
Have a clear plan for why you need to use SharePoint, what you need to achieve, how you plan to achieve it, and when you need to complete each phase by. This helps you to see what is the best approach and prioritise the way you introduce SharePoint to people in your organisation.
If you are planning to replace many existing online tools e.g content and document management systems and/or collaborative tools it is critical that you consider the impact that actions taken in an earlier phase could have knock-on effects during a later phase (which maybe 1-2 years ahead) e.g. permissions, SharePoint Designer.
Without any plan the consequences for your organisation and people’s online experience could be disastrous. SharePoint is a very powerful tool and needs to be managed carefully!
People publishing and using SharePoint information need to appreciate that it is not all the same in its value (something I will be writing about in the future) e.g. a policy is unlikely to change frequently and be inaccurate but an opinion expressed in a discussion group may be inaccurate, incomplete, change next day.
People need to understand the differences in the information they use and behave accordingly in their judgement and actions based on how much value they place on it.
SharePoint is more than a change of technology, it can change business policies, processes and how people behave when they have a problem or want to share some helpful information.
I have heard how IT have approached the business saying “we have this free tool option on top of X product that we’ve bought which we’re going to use for Y purpose”. It’s a natural reaction to test out something for free but many organisations have found it doesn’t work out the way it is planned.
Firstly, you need to make sure you have a business problem that SharePoint is a good (note I didn’t say the best) technology solution to solve. Sometimes I have seen the introduction of SharePoint create problems that didn’t exist before.
Make sure you involve people who will be affected by any changes you plan to make as early as possible who can also test these to see if they do help as you expect SharePoint to and feedback any issues to be acted upon before it is launched.
Your organisation needs to be clear on what the problems and their root causes are before considering whether technology, and if so, which solution e.g. SharePoint can best help resolve the problem.
I hope this can help you to appreciate there are factors that influence why people feel SharePoint is ‘good’ or ‘bad’ apart from the technology itself. It is more likely to be how you have approached and implemented SharePoint rather than the tools and features people can use that affects your view when you think about it more deeply.
Please leave a comment with your views and contact me if I can help in any way.