How do you use your Intranet?

I’ve been thinking a lot about Intranets this year. The question is coming up more frequently with clients as to how to use Intranets to lower costs, and improve employee engagement; and the one word which keeps coming up in one form or another is Collaboration. How do you get turn your Intranet into a tool which employees both want and need to use on a daily basis, and one which they use for working with other employees?

Collation of Intranet tool images
Collaboration seems to have been the buzz word of 2011. Much in the same way that Social Media has really taken off and become a key tool for businesses to talk to their customers, it seems that Social Media type tools are being increasingly used to engage and communicate with staff. Bulletin board and twitter style update tools that spring to mind which are focussing on this niche are yammer and present.ly but it still seems to me that these one-line Facebook style updates provide just one channel and you can’t rely on all employees wanting to to engage in this way. Often they will be trying to find or communicate information regarding policies or procedures which are better housed in a document library or sent only to certain individuals.

Back in 2001 I worked with Phones4u when John Caudwell hit the news for banning email. I have no idea if he was the first big business man to hit upon this concept, and he certainly hasn’t been the last – in fact Atos recently declared a ban on all internal emails. In principle there is a sound argument that emails are distracting, prevent people from doing their day to day job, and that people overly rely on it for all communications, when often picking up the phone and talking is a far better way to get a resolution. However in truth, like with bulletin or discussion boards this is only one channel and it is about using it in the correct way. Email is a very efficient tool for confirming actions & minutes, sending contracts & agreements or providing notifications of events. Where email fails it is frequently because it is being used instead of conversation. The Inbox fills up and the important notifications get missed. However, in today’s world of overcrowded diaries,  flexible hours and working in different locations and different time zones, an alternative mechanism for conversation than face to face meetings is still required.

For the past decade or so I think it’s fair to say that Intranets have most commonly been used as a broadcasting tool and document repository; with sales messages, staff policies, organisation charts, structure changes and staff bulletins being the key purpose of the site. Unfortunately over time many Intranets have become clogged with information, with fewer people keeping them up to date and relevant information becoming increasingly more difficult to find. More recently Intranets have been plugged into more interactive tools such as HR systems, time management systems or Management Information Systems. However there was still largely a disparity between the types of interaction: interaction between users and Intranet tools, and interaction between multiple users.

Increasingly though organisations are spotting this gap. The fact that employees are having to move between email, Intranets and various interactive tools is being seen as a barrier to efficiency; and so there is a desire to bring the systems together and the line between which mechanism to use when is becoming increasingly blurred. When you look at systems such as IBMs Connections software which links email to a social media type interactive bulletin/discussion board, and can also host content managed web copy and documents or when you look at the various ways you can use Sharepoint tas a web publishing tool for both pages and documents, and where you can not only publish documents but feedback on them and introduce version control – then you start to realise how joined up Intranets could really become.

It is great to see more organisations looking to technology to improve efficiencies in this way. Too often I think Intranet projects are given lower priority as they are not seen to bring in the value to organisations that more commercial e-commerce based web projects could bring. However I do think that before any business embarks on this road it’s important that they go back to basics and identify the key requirements:

  • Who do staff need to communicate/interact with to do their day to day job?
  • What tools do staff need to do their day to day job?
  • What information does staff need to do their day to day job?
  • How are you going to train staff as to which elements to use for which types of communication and then ensure a culture of correct use is followed?

If you start to get too carried away with the technology, or don’t invest the time and therefore forget to ask these key areas, then I fear that no matter what solution is put in place it will ultimately grow into another example of an Intranet which ultimately is undervalued.

Technology and web access has never before been so much on the move….

Anyone who uses trains or planes to get from A to B wouldn’t be surprised to learn of the increasing use of mobile platforms to access content online. Never before have you seen so many people sitting in close proximity staring at so many different types of screen: mobile phones, web phones, laptops, tablets, e-books… the list seems endless.

It doesn’t seem to be that long ago that when you talked about your organisation being ‘mobile ready’ you were referring to the fact that you had a website optimised for mobile phones (a .mobi intead of a .co.uk) but in today’s increasingly fast changing world that is no longer really enough – and I would suggest its not necessarily a wise investment either.

If you refer to mobile usage now you need to think of mobile in its truest sense of the word: people on the move. People on the move have a different set of needs to people sat at a desktop and we shouldn’t think of the term mobile as being a device, more that mobile is a circumstance. For example someone could be on a large screen laptop with free wi-fi in a coffee shop and intend to spend the morning there (I’ve done it myself often enough) – would they be considered to be a mobile user? And increasingly it seems we are also using our phones or laptops in the home to tweet, read or work, whilst sat in front of the other big media device of the century: the TV. In fact I’m doing so now.

For me, if you are supporting the needs of mobile users you should be thinking about the reason they are accessing the web in the first place, and the various constraints that they may be encountering. For example, if someone is ‘on the move’ then they may have bandwidth issues, limited time, restricted screen size, or be in a crowded place. All of these factors will influence the users behavior when interacting with your site. If your organisation is a shop then your ‘mobile’ users could be looking for a map, directions or contact details to help them find you. If you are offering advice then is it accessible in a way that can be easily navigated to and read in bite size chunks. If your users are customers who need to access account details then what are the details they will really need when they are mobile, and how can they access them?

None of these concepts require specialist technology to support the users needs, it is all about clever information architecture – where you put information on your site and how your users navigate to it – and ensuring that the user journey works for all types of users.

It can also be argued that with a new mobile gadget being released every few months, is it realistic to redesign your site for each and every device? With this in mind accessible and user focussed web design and best practice has never been so important.

I’m not saying that sites built for a specific device with a specialist technology don’t have a place – in fact if your audience is only using one method to access your information then it makes total sense to optimise it for that browser or device… and if you are creating a short shelf life pieces of functionality then there may be some really great cost or experiential reasons for developing it in a specific way.

Never the less if you are looking for ways to reach your mobile audience I would argue that if you consider your core user needs, and lay out your website in the most appropriate way for these needs, and if you use technology that works across all devices, then you will reap the returns of having a site that people can use from anywhere.