Blog

Sharing is caring for SharePoint

Share

Microsoft SharePoint is everywhere these days, and while intrinsically it is a great SharePoint: designed for sharing?platform for sharing, many organizations are struggling to reap this most basic benefit. Did you ever ask yourself why a product whose name starts with 'share' is actually rarely used for that specific purpose?

Yes, SharePoint holds many promises but many of you are not yet getting your full bang for the buck. Why is that the case, and what can you do to solve it?

SharePoint: designed for easy sharing

SharePoint has a come a long way since the early days, back in 2001, when SharePoint Portal Server and SharePoint Team Services were launched. In the years after that, other building blocks were added along the way, as illustrated in this SharePoint history chart, but it wasn't until the release of MOSS 2007 that these building blocks were brought together into a single integrated platform. The 2007 release of SharePoint has seen tremendous business success: it combined collaboration, portal, search, content management, business forms and business intelligence into one consistent piece of software. The exponential rise of SharePoint in the enterprise has been further stimulated by the much-anticipated and significantly improved 2010 release. The rest is history...

Ever since the origins of the SharePoint family, today a multi-billion dollar product suite, sharing has been at the core. Essentially everything is a list - you can put things in lists and share them with your colleagues. This fundamentally simple concept has certainly contributed to the overwhelming success of SharePoint around the world.

But somehow organisations are not yet getting their full bang for the buck. Often it already goes wrong at the start, when SharePoint is introduced with a focus on IT aspects, cost and project management, rather than from a genuine understanding of sharing as a new business model. Others claim that the product is too complex for most end users, and as Steve Krug taught us many years ago:

If something is hard to use, I just don't use it as much. (Steve Krug, 'Don't Make Me Think')

Snapshot of today’s trends in SharePoint usage

At J. Boye we regularly discuss this topic with the many SharePoint users in our various intranet groups. From this, I have derived the 4 following trends - confirmed by industry reports - about how SharePoint is actually deployed and used:

1)  SharePoint's most popular feature is the usage of Team Sites and workspaces for collaboration, closely followed by intranet sites and news portals. A complete list is shown in the figure below: (from the AIIM Market Intelligence report on the usage of SharePoint)

SharePoint usage

2)  SharePoint is often deployed in parallel, and not as a replacement of, other enterprise systems and the traditional intranet. While this approach allows for flexibility and time to run proper pilots, it's inherently a duplication of effort and of infrastructure.

3)  The most common challenge mentioned by our members is user adoption. SharePoint is often perceived as complex, non-user friendly, and not mainstream within the organization (for instance, used by IT only or at headquarters only, and not in the rest of the organization).

4)  Deploy first, do strategy later: Organizations rush into deployment and piloting without clear objectives. I've discussed this in more detail in an article about how to leverage the social features of SharePoint, which was a big topic at the J. Boye conference in Philadelphia, May 8-10, 2012.

Not present at time of photo: sharing!

True sharing needs to go beyond just deploying the latest technology and hoping for the best. I've discussed the idea of sharing on your intranet in a previous article. I'm convinced that SharePoint can support sharing in many different ways, but today only limited progress has been made:

  • Social features: Employees need to be able to connect with each other and share opinions, experiences and common interests. The My Sites functionality of SharePoint is a great place to start doing this, but many organizations are struggling with adoption and quality of information.
  • Mobile access: True sharing means access to information anywhere, anytime, not just from behind an office desk. While mobile support is much improved in SharePoint 2010, most organization do not yet see mobile access as a priority or are struggling with the consequences of 'Bring Your Own Device'
  • Collaboration: This is the area where SharePoint has made the biggest impact, but still many organizations are not leveraging the full potential. Sharing of knowledge is often limited to departmental Team Sites, reducing SharePoint de facto to a glorified system of shared network drives.
  • User experience: Poor usability is often quoted as a major roadblock to SharePoint adoption. Often the technology is deployed ‘out of the box’, with little or no customization or integration with an existing intranet. Sharing and caring are difficult if the technology is working against you!

The solution? Focus and show you care!

No, there is no single right way to introduce SharePoint in your organisation. The platform is very versatile, which is a blessing and a curse at the same time. From my experience, the trick is to focus: pick one particular business benefit that you want to achieve, such as sharing of employee knowledge, and then focus your attention and resources on that area.

And if you really care about getting the most out of SharePoint, then show it by ensuring that the platform is introduced with the right focus. Make sure that the focus is not exclusively on IT, technology or vendors, but care enough to adapt and customize the software to your end users' needs.

Next steps for your SharePoint intranet

  • Share with the best: SharePoint implementation projects are often discussed – and compared! – in our many J. Boye intranet groups across Europe and North America.
  • How does your intranet measure up? We’ll tell you as part of our intranet benchmarking!
Guy Van Leemput shares & cares about intranets!

Guy Van Leemput
Online communication and intranet expert

Guy is heading up J.Boye’s activities in the Benelux region (Belgium, the Netherlands and Luxemburg). His primary focus is launching and moderating Groups on web and intranet.

Prior to joining J. Boye, he was a senior manager at SWIFT, the global provider of secure financial messaging services, where he worked in various roles, including being responsible for all e-channels for internal and external communication.

gvl@jboye.com

6 Responses to “Sharing is caring for SharePoint”

  1. Good article Guy. User adoption of SharePoint is one of the hardest areas to get right. One way that I have found is getting interested people to be champions and for them to help support others in using SharePoint. We also try and focus on a small number of features for team sites such as sharing documents. If they can do that well then we move on to other areas.

    Small steps, small steps….

  2. David says:

    Guy, my company uses SharePoint for intranet, 700 users. The company website is not run on SP but they are looking to do so. I am in the marketing area and don’t want IT getting too involved in content side of website if they host it on SharePoint. Do you know of any articles that 1. argue for different team to look after SharePoint as intranet platform, and web platform and/or 2. articles that recommend hosting websites off-site with dedicated hosting, due to downtime and security concerns if IT hosts in-house (my concerns!). Re second article topic: is there a simple case for hosting SharePoint intranet and website both internally, due to ease of sharing docs between platforms, for example? tx

  3. Kevin Cody says:

    @David – I’ve been involved in many similar discussions about whether the intranet and website can be supported by a single platform. I tried to find the discussions on LinkedIn without luck. Personally I believe the requirements of an intranet and a website are quite different, the audience is different, there may be some content cross-over but much of the content will be different (intranet should support UGC and not be concerned about SEO for example) and even the skillset to specify & manage is quite different. I did find this article by Step Two Designs from 2003 (!) which also argues against a common platform http://www.steptwo.com.au/papers/kmc_intranetvsweb/index.html It may pre-date Sharepoint 2007 & 2010 but the argument is no less valid today. It is interesting that IT may be pushing for a common platform which of course is more technically elegant but has little to do with real business needs.

    Kevin

  4. Wim Putzeys says:

    @David – as a long-time website and intranet development service provider, I agree with Kevin’s comments. Most of my customers want more editorial control over their website than over a collaborative intranet, which requires a different skillset, typically from a specialized team. However, maintaining the intranet and the website in the same technology is not necessarily an issue if you are happy with Sharepoint’s web publishing support (still limited compared to dedicated WCM tools) and the service level IT provides. On a website you typically need to be able make quick updates – content and functionalities – and I have seen marketeers’ flexibility reduced because IT runs the website and the intranet on the same platform with the same same service window.

  5. David says:

    Kevin and Wim, many thanks for your insightful comments.

    For the website we use Dot Net Nuke, the worst CMS I have ever used, but it wasn’t my decision. Anyway, being in bed with Microsoft they have come up with a SharePoint connector to apparently make file uploads from intranet to web quite easy, for authorised users.

    Is there synergy in using a CMS for the web that at least has some connection to the SharePoint intranet, for ease of file transfer, for example?

  6. John says:

    I think often times a certain product is designed for one purpose but over the years evolves into something much different than its initial design. Sometimes software products follow this type of evolution path but are stuck with a name that might not apply 100%.

Most popular posts from our blog
August 12, 2009 by Janus Boye
Selecting the right CMS is not an easy task with; there is in excess of 1,000 vendors in the very dynamic CMS…
February 16, 2010 by Janus Boye
All modern CMS vendors claim to be capable of delivering content to mobile devices. Some even offer additional modules to make the…
March 21, 2011 by Janus Boye
You may be impressed by some of the features during a CMS product presentation, but in reality many of the features that…
Recent comments
May 17, 2013 by Rachel
FWIW, I'm in the camp that considers WordPress to be a blogging solution, and no more than that. It's certainly…
April 19, 2013 by Fredrik
Dear Mr. Olsson! Even though your post is now almost a year old, I could not have agreed more today.…
April 17, 2013 by Jason Rhoads
It's amazing how the social media features are changing traditional intranets. Any word on how they are going to handle…