Instant Messaging (IM) is great – and there’s still a lot of scope for corporate adoption. It’s particularly useful when you want to ask a quick question to someone who you don’t really know that well. It’s not as scary as calling someone you’ve never met, and it’s a lot quicker than an email which usually has to have a lot of “I’m sorry for bothering you this way but I got your name from abc and I was wondering if you could possibly help me find how I can do …”.

An instant message can look like “Hi – it’s Jon here from accounts. Do you know where I can find the official expense form?” and the reply can be instant, whereas an email may not be replied to for days, if at all (especially if the person you’re trying to contact is on holiday).

However, whereas you can get the answer quickly, I find it can be difficult to actually end an instant messaging conversation, especially if it is with someone you don’t know. Here’s an example:

A : “Hi – I heard you might be able to help me find x”
B : “Sure – it’s here : http://jonmell.co.uk/. Once you’ve filled it in send it to person@company.com.
A : “That’s great.”
B : “No worries”
A : “Many thanks for your help”
B : “Sure don’t worry about it.”
A : “See you later”
B : “Bye”
A : “Bye”

It definitely happens more with people you don’t know so well – if you know someone I guess it’s more comfortable just to end the conversation without doing so formally. Anyone else observed this behaviour in themselves/others?

IBM have recently published an ROI study about their own internal use of instant messaging. I was initially quite excited about this, I am a huge instant messaging fan, and sometimes I think the fact that it seems like such a no-brainer to me in terms of corporate use I struggle to articluate why people should use it (almost like having to justify why phones are useful for businesses).

I was somewhat disappointed with their report. They reckon they have saved $16.5m per year “in phone usage alone“. This is based on 380,000 users, 200,000 concurrent users and 4 million messages sent per day. They then estimate the number of times instant messaging is used instead of the phone, the average number of minutes per call and the phone rate.

So far, so good. But then we get the following which have also “factored into the calculation”:

• Quick access to expertise
• Allow more employees to go mobile

And further cost savings are available from “the cost benefits of high productivity”.

How did IBM measure the benefit of quick access to expertise and allowing employees to go mobile in a way that they managed to combine it into the $16.5m number? How would they go about measuring high producitivity? These are the really interesting metrics, measuring usage of instant messaging at the expense of phones is relatively easy and straightforward, but positions the corporate use of instant messaging firmly as a cost saver.

Now, from a sales point of view this may be the best way to get instant messaging into an organisation and past the CFO, but I am convinced that instant messaging can help generate revenue. For example:

• Did quick access to expertise allow IBM to get the right subject matter expert to contribute to a proposal which led them to win a multi-million dollar contract they would have otherwise lost?
• Did allowing employees to go mobile increase sales face time with customers by x% resulting in $y extra revenue?

This revenue generating activity is how instant messaging can help an organisation which embraces it fully (which I know that IBM does!) but is also where examples of ROI are sorely lacking. It would have been great if IBM could have provided some insight here, even if they were isolated examples rather than figures that could be applied across different industries.

Really interesting post from Stuart over at the Quickr blog – initially about migrating his blog to a new platform. The interesting sideline is about living inside his email client (which happens to be IBM Lotus Notes). Part of the problem for enterprises adopting Web 2.0 communication/collaboration platforms is that there are new applications to learn, which can create barriers. Social networking, blogging, wiki contribution, instant messaging, not to mention email, are all to often separate self-contained applications. When organisations try to roll them out there is often a negative reactin towads “yet another application”, and users have to manage switching between them, sometimes with different usernames and passwords!

Whilst I often encourage clients to move away from email as a form of communication, this doesn’t necessarily mean moving away from their email applications. Instant messaging can now be plugged into both IBM and Microsoft platforms – so you can reply to an email with an instant message, or a pc-to-pc phone call right from within your email client. This significantly increases the chances of your users to actually try the new communcation features rather than simply reverting to habit and relying on email. Stuart’s post shows that blog and twitter posts can now be managed alongside email and instant messaging from a single application. If Web 2.0 collaboration features can be provided within existing applications, the chances of people actually using them is likely to increase.

Social software/Web 2.0 tools such as blogs/wikis/instant messaging can be a great way to manage the exceptions to your business processes. Here’s why…

In a previous life, I was an SOA Evangelist for IBM’s WebSphere integration suite. A large amount of IT spend in the early 2000s went on systems like this one to integrate processes, both internally and with suppliers and customers. The idea was one of cost reduction, reduce the cost of doing business by reducing the time it took to add a customer to a vendor list from 3 days to minutes. The ROI cases were strong and compelling, and many customers managed to get ahead of the market through early adoption.

Now, however, such integration capabilities are more commonplace. Most business processes have been automated to the point where there is not a lot of cost left to be squeezed. Further, (and this is something that bugged me at the time) the vast majority of ‘real’ working practices don’t actually follow the process. The process becomes more of a guideline than a set of rules – exceptions to the process are the norm. Once you have an exception (payment terms are 30 days, but they’re a really important client so we won’t send them a nasty letter until 60 days) – the ROI breaks down as humans have to get involved again. Also, because the ROI cost case relies on people following the process barriers are often put in the way of breaking it, making it even more costly to “do the right thing”, be innovative, and follow an exception.

I was trying to find some stats on how much impact exceptions have on business processes. I am convinced somewhere I found something about 80% of processes resulting in an exception at some point. Vitria are so concerned about exceptions in business processes they’ve created a product for it and claim 50% of process related costs are down to exceptions.

Vitria (and others – I’m not picking on Vitria, they just happened to come high up on Google for “Business Process Exceptions!” offer exception management, but it sounds like another process. To quote from their site:

“Vitria’s Exception Manager is a purpose-built application that provides a systematic approach to resolve exceptions across your enterprise. Exception Manager classifies incoming exceptions, automatically resolves problems, guides resolutions with context-sensitive workflow when human involvement is still required, restarts the normal process flow, and provides full visibility and audit trails across the entire exception resolution lifecycle. “

So what happens when there’s an exception during the classification process. Or an exception during automatic problem resolution? The point is that Business Process Management vendors try to solve the exception problem with what they’re good at, a process. Where Web 2.0 can help here is by providing a tool that fits the problem at hand. What you really need when an exception arises is to communicate with the person who can fix the problem or authorise the exception. The problem is, traditionally, it’s hard to get hold of this person or even know who the right person is! That’s where enterprise social networking, blogs, wikis and especially instant messaging can become vital tools in resolving exceptions whereas email is not that helpful at all. This is why instant messaging is fantastic for large organisations during quarter end – the conversations are all around exceptions to the process – the key is to get the order in the books in a legal manner. We work with one of the world’s largest IT vendors who told us that the accepted downtime for instant messaging during quarter end is measured in seconds, whereas email is hours. Tools such as social networking can also help you find the right person in a time constrained situation, especially if your ‘usual suspect’ in finance or HR isn’t around and you need to find someone similar with the same skills quickly.

The aim of a lot of social software tools is they are based around tacit knowledge. Business processes, however, are all about explicit knowledge. Social software is the yin to business process yang. Exception management definitely falls into the ‘tacit’ space, however, which is why the explicit, systematic approaches to exception resolution fail. The exception is an exception precisely because a systematic approach does not work in this instance, and it is down to employee initiative and innovation to find a solution.

Looks like we’ve found another ROI for Web 2.0 – reducing the cost of business process exceptions which can be up to 50% of the cost of a process.