Stuff and nonsense in Unified Communications

Matt Lambert | Unified Communications, Unified Messaging | Tuesday, February 19th, 2008

There’s far too much of it about and I’ve just read some more here. Sorry Art, I have to call it like I see it

The clue is in the first paragraph, where it says;

“What was most interesting about this piece was that it quoted several different definitions of UC promoted by leading industry technology developers and analysts”

We can’t let people off with describing the technology just how they would like to see it at some far off distant point can we? Those leading developers and the pet analysts, with their own interests at heart, are currently spinning off each other into a dustcloud that nobody can see into.

I really don’t have a problem with people who disagree about a definition -if they would only come up with a definition that people can understand. Yes it can be complex, which is why a clear explanation is required….apply more rigor. If people can’t understand what you’re saying, stop talking.

Personally, I don’t think the following should be mixed up.

  • Unified Messaging
  • Real Time Communications (The real Unified Communications can stand up)
  • Fixed Mobile Convergence
  • Communications enabled business processes.

That’s because Unified Communications is about the person, the user - people communicate, companies don’t.

So, what exactly is being unified for the user? - Answer: GUI client software.

The whole point is that instead of installing ten types of client software and teaching the user to work each one, for the telephone, instant messaging, conferencing, video conferencing, web conferencing, for example - a user just has one interface and a single address book for the lot. Multimodal. By combining client software, we make it easier for the user to use - and therefore to understand.

You wouldn’t/couldn’t have a single interface for messaging and real time communications because they would have different buttons. I also can’t see people using GUI software on a mobile device, pie in the sky…but perhaps that’s just personal opinion.

UC will generate sales - but only when they show it fully working to the end users.

/end rant.

If anyone else wants to agree or disagree, feel free to join in.

The product experience is everything

Matt Lambert | Unified Messaging | Monday, November 5th, 2007

As per my last post, I am continuing to look at the software user interface, and the impact on communications software product success.

I found a link to a great presentation from Peter Merholz of adaptivepath. “The Experience is the Product” sounds a lot like “the software IS the interface”, which is a Steve Jobs quote I return to, again and again.

Eastman Kodak, iPod and the Wii are good examples in the presentation of innovation.

In some ways, it is good to find one’s themes echoed somewhere else, particularly when someone much more eloquent is putting forth their thoughts.

I also noted more than a passing resemblance to trivergence , where the device is but a part of the overall system.

To flesh out the experiential side of product success, I again recommend listening to this linked file, from Lou Carbone. This is a must for any product manager.

I’ve seen loads of white papers that explain the technology (admin) approach and the communications enabling business processes (business case).

But where are the white papers on the Unified Communications user experience?

Thanks be to Futurelab and Karl Long for the pointers.

Related posts

How many user interfaces do you want for unified communications

Unified Communications software makes you feel like a genius

User/s matter/s

Matt Lambert | General | Friday, November 2nd, 2007

I recently posted about how Unified Communications are everything to do with user interfaces, and a great post over at ZDNet from Dennis Howlett, links to a number of other opinions and discussions around the User Interface subject.

A theme looks to be developing that the people who place the order for software solutions, have a different agenda, or ticklist, from the people who then use the software. And this is a disconnect of some proportion.

Users want complete and utter flexibility in how they use the software - feature richness combined with ease of use.

Administrators wants software that doesn’t go wrong, failover in case it does, and simplified user management.

So, the products that ‘win’ and get the sale don’t necessarily do things right for the user. .

The trouble is, studies seem to show that most contributory causes of software project failure is ignoring the needs of the user.

I’m not sure how recent the following is, and is skewed towards software development, but things likely won’t have changed much.

If you get the user bit wrong, then the third consituent, the Business, won’t get their promised returns.

So, how do you know what is the right choice for the user? Just looking at software won’t help much.

These people seem to know a lot about user interfaces. The first part of Seven Critical Considerations for designing Effective applications, includes ‘designing for the users previous experiences’.

What a user already knows, applied to the new, is intuitive software.

As an aside, this makes me wonder if the new user interface Ribbons for Windows Office are going down well.

I don’t know the answer, but these comments on a post by Chris Pirillo are fun

Later, I noticed an ad in the bus I took home from work. It emphasized that Office 2007 was very, very different from previous versions. That, in my opinion, is an understatement. Microsoft seems to think that’s a selling point. I beg to differ. It might be a selling point to someone who’s never used Office before, but realistically, how many people is that? Office has long been the default software in professional offices, and computer professionals don’t want to have to learn a new program from scratch every time Microsoft decides to upgrade. It inhibits productivity to have to do so.

People don’t really want new. They want better old stuff. Isn’t redesigning a user interface completely just letting competitors in?

The next installment of Seven Critical considerations will include designing for flexibility.

The reason that’s important is that it’s hugely unlikely, nay even impossible, for anyone buying a solution to anticipate all of their users different wants and needs. And, they will be entirely different from each other thats for sure.

If software designers find it excrutiatingly difficult to know what to design for the best, then what hope the rest of us mortals who don’t do it for a living.

These are my suggestions to look at

1. The solution with the longest feature list, not a kludge (there is even a word for it).

2. The longest history. That enough people bought it to keep it going long enough to add all those unanticipated features in the first 4 versions is encouraging.

3. Look at companies that concentrate on one technology - in the hope that no wars for research and development budget will be fought. The innovators dilemma is a cautionary tale. “who’d have thunk that ’smaller’ disk drives would sell?” Great book.

However, if someone makes great technology, it often gets bought - so maybe that one doesn’t work. In fact, maybe none of them will.

Perhaps a better idea is to not take shortcuts, but they’re so tempting. Here’s another one. Buy from people who love what they do.

Ah well, I’ll keep reading till I find out some more.

Unified Communications software makes you feel like a genius

Matt Lambert | Unified Communications, Unified Messaging | Monday, October 15th, 2007

The trouble with using bad software is, it can make you feel like an idiot.

For me, BAD software is something that

  • a. ‘could’ ‘logically’ transform a task, but somehow manages to elude our using it to the fullest extent.
  • b. takes longer to achieve the task than the way we’re doing it already

Whatever the software, the improvement has to be outstandingly obvious for people to adopt it.

Not knowing what is good for us then, is just a symptom of being human.

At this point, it would be easy to score some cheap points about ‘user unfriendly’ and frustrating software ruining a perfectly good product idea - sadly we’ve all used bad software, so that’s not the focus.

And, for the record, I don’t buy into the refrain that bad software workers are just blaming their tools. More often, they blame themselves.

On the flip side then, what makes good software good?

I contend that Good software makes you feel like a genius.

Without any training courses you just know how it works….and how good is THAT, being able to use software without any training.

It doesn’t take long for the feelings about how good the software is, to blend very neatly into feelings about how clever you are.

Of course, it’s only fair to share the good fortune and show other people how much of a genius they could be too. When this happens, the results can be impressive (ipod sales). Good design has a momentum all of its own.

Intuitive software is like that.

The WAY it gets to be intuitive is to think ahead, to know what the user wants to do, before they themselves know they want to do it, as well as just being tons better than the old way.

Intuition itself is based on past experiences, it’s why traffic light colours have spread into many other facets of life.

Intution then, is what you already know, applied to the new.

So, to Unified Communications.

Software has proven itself useful - a given I hope - and thus (communication) applications are being presented and are multiplying at an incredible rate.

Even websites are now interactive, and thus a brand new interface for every site and every service.

Unified Communications is completely, utterly, about the reduction of user interfaces. Nothing to do with a single box or supplier for every application.

This is in a world where the amount of software that users are being presented with is leading to their shoulders sagging under the load.

A good example of this user interface ‘reversal’ is with voicemail.

A user’s past experience of a machine that answers a phone, was an answering machine. And THAT is exactly how people used it, ignoring the 90% of functionality that was available past the first keypress, because their intuition didn’t tell them anything different.

People trust their intuition more than they do other people, and so training courses were of little value in improving the situation, a comparitively weak alternative to an intuitive interface (but better than nothing).

Enter Unified Messaging - NOW, voicemail looks like email. You get one, you click it and its just another email.

It’s simple but exceptionally powerful.

Ok, a difference is that you play voicemail - but the player looks just like a VCR…so we’re home!

Suddenly, without training, every user knows how to play, reply, forward..with or without an introduction, save, and even forward to a group of people and link it to whatever other systems they’re using. Address books are also leveraged, and users can be managed within the same environment.

This advance in software helps user’s ‘get it’ without trying, and when that happens, 90% of people suddenly gained a great deal of productivity without any instruction.

Moreover, when we get that, it’s easier for them to treat email like voicemail when calling in to their office voicemail system. When listening to an email is just like listening to a voicemail, the concept has been transmitted, wordlessly, unlike this post :-), by building on their previous experience of (unified) messaging.

And so it continues, when ‘messaging’ becomes that easy to use, the next step is to eliminate mobile voice messaging, because it’s so much less useful than it ever was.

Extend this same process of interface elimination to fax and text messaging and it goes to reverse the users feeling of being overwhelmed by yet more software to learn - in fact, the roll out could be headed….”we’re giving you less to learn”

In itself, hardly earthshattering - but, in context of a massively overly supplied PC screen, software without training and high adoption rates (that’s what we see) is more than a good thing, it is somewhat exceptional to the norm.

The next frontier

Where are we (users) with ‘real time’ communications software interfaces?

There is one area where this is already working very well, and this is by ‘communications enabling’ a user’s existing interface. Where you ‘telephone enable’ a customer database, for whatever reason, it is possible to extend the users experience, intuitively. Click to dial is a form of this, but quite limited, but another is rules based call routing based on who is calling and why.

However, for most people, personal real time communications includes,

Telephones, Instant Messaging, Audio, Web, and Video conferencing, mobiles and lots more.

And, ‘Nowhere fast’ about sums it up.

To my mind, each best of breed (realtime) company has a piece of the jigsaw, but instead of playing nicely together and just finishing the picture, they’re off constructing the other 80% of the jigsaw pieces themselves. I’m talking about IM, telephony and even public network companies. This isn’t what the users want or need, in my opinion of course.

There are some notable exceptions, but that’s for another time.

It will be interesting how it all pans out, but talk about being ripe for disruptive technology. I expect a lot of free interfaces will come to dominate, before they eventually get you by charging for the upgrades.

Voice and Applications. He who integrates, wins

Matt Lambert | Fax, Unified Communications, pbx | Friday, July 20th, 2007

This time next year Rodney……..(for Only Fools and Horses fans)

This linked article from Red Herring shows Jajah has linked up with eHarmony dating site - I wonder who made the first move?

Whoever, it’s a great idea, and the service will presumably hide your number from people you’re not sure you want to know! I picked this snippet up from Alec of Iotum who also looks to treat voice only as a component part of a wider application.

The article, and Jajah’s website shows their burgeoning integrations list, and I feel this will be absolutely key to winning mindshare in the voice application market…even the hosted one.

jajah_conference_call_visual.jpg

In fact, voice right now is very reminiscent of the early fax market.

The market in the early 90’s seemed to be dominated by Unix based proprietary systems - check out this quote from Network Computing in the 90’s

Fax servers today are more or less tied to the software delivered with them, at least on the server side. Some fax servers support the Communications Applications Specification (CAS) and can therefore work with a desktop application that supports CAS. So to an extent, you can plug in the desktop client of choice, but you may end up losing some of the unique abilities of the server (such as sharing common phone books or accounting).

(more…)

Speech Recognition access to Unified Communications, which one?

Matt Lambert | Call Handling, Mobility, Unified Communications, Unified Messaging | Monday, June 4th, 2007

Unified Communications as a concept has a number of interfaces around which technologies are consolidating

Interfaces are converging around Messaging, Real Time Conversations and incoming call handing - complemented by applications being ‘enabled’ for communications.

Speech Recognition (the user independent variety) is another method to access Unified Communications technologies, usually from a mobile telephone, but being new, it is difficult for companies to position different solutions and make buying decisions.

So, one of the first questions I would put forward is ‘how many speech interfaces does a user want?’

Do they want to call in and access and handle messages and contacts, call another system to set up their voice/emailbox and change their incoming call handling settings, and perhaps yet another number to access their Speech enabled application. Perhaps a different server could run the speech driven company directory transfers?

Perhaps not.

speech.jpg

Each speech platform will have it’s own ‘logic’ in terms of users interfacing, so learning more than one will likely be more than users can stand. This should be a way of filtering out some one trick ponies!

How many user interfaces do you want for Unified Communications?

This post is incomplete, but then so is the industry

I’ve mentioned before that the key to understanding Unified Communications (all of it) is the software interfaces presented to the user. (You may notice I don’t mention voip at all in the following, it’s about users).

Unless the user is going to adopt functionality, there is almost no point deploying it…..and by definition the more interfaces there are, the more difficult adoption will be (how many training course will users go on).

Once the required interfaces are defined, it’s so much easier to put the technologies in the right place, or in the right box, so to speak, and so I have been framing business requirements around the GUI.

The reason I’m bothering here is that I have met with customers who have in front of them very interesting new products - but they overlap so much, and so how does one decide?

It can be as tricky as hell, as current comms software technology on offer includes

Messaging

  • Email
  • Voicemail
  • Fax
  • Text Messaging

Real Time Conversation interface,

  • Instant Messaging - are you at your desktop
  • Telephony - are you on the phone
  • Conferencing, Audio dial in, dial out, desktop sharing, webinars
  • Video conferencing, are you at your desktop

You can see overlaps wherever you look with UC - but there will be ‘at least’ two interfaces for users - as the ‘button’ requirements are different for messaging, to that of real time.

Messaging buttons; - Address, Send, receive, store, mark as urgent, copy, forward, and so forth

Real Time buttons; - Receive contact, Make Contact, whether IM, call, or video, include someone else in the conversation, transfer, desktop share, present, record, and so forth

  • Messaging interfaces are reasonably well defined
  • Real Time Conversation interfaces are in their infancy
  • Personal Contact Handling isn’t well defined

However, for framing Unified Communication discussions and decisions, each user will probably have at least the first two initial interfaces for personal productivity.

A third interface should exist, but doesn’t yet (?)

Personal contact handling

  • This doesn’t yet exist as a recognised ‘desktop based user interface’ category - although network based Grand Central is a good start in showing what will be possible
  • Call routing and handling, where should calls go, onto which device, at what time
  • Planning - willingness to engage, calendar integration, - Iotum is interesting
  • Call processing, what happens to the caller if you can’t take the call
  • More loosely defined is a meta directory, routing and capture application such as that delivered by Corebridge - because contact information pervades around all communications solutions, (and existing applications).

It isn’t clear where functionality to control personal contact handling will be interfaced by the user, - most of the above is handled at premises based system admin level currently - but it makes sense if all features to determine the inbound call routing for today, all end up in one interface, (if not provided by a single backend system) to be controlled by the user instead of Admin.

This interface could yet still be provided by a hosted system provider, overlaying and complementing existing site number and mobile number implementations - instead of replacing them completely.

The final interface, enabling existing applications with (the same) communications

As well as providing the primary interface for specific channel technology (show me all my received faxes, calls, emails) All the technology channels above ‘may be’ suitable to ‘enable’ an existing user interface, by line of business - Email a Contact, Fax a contact, Call a contact, record a contact, Text a contact

By way of a small example, although fax is a single technology channel above and sounds simple enough - fax integration can get interesting when requirements appear on the horizon to integrate into Exchange Outlook, or Lotus Notes, then to the telephone system (TDM or IP), then to unified messaging (forward the fax to a local machine) then SAP or Oracle line of business applications, then back end integration to hard copy Multi Function Devices and onwards archiving to the industry flavour EDM.

Nobody said it was simple.

At this point, Microsoft Sharepoint usually comes up in the conversation as a replacement interface to all the existing applications, so UC takes on another interface….and so it goes on, much to the user’s consternation.

There’s a play on words about ‘users’ being addicted to existing interfaces, but that would be cheap.

How to choose

Enabling lots of interfaces with a technology flavour tends to point towards best of breed technologies instead of an all-in-one UC solution.

Generalising: wide ranging applications just don’t go very deep in my experience, and ultimately they don’t generate enough ROI, and therefore sales, to justify the development resource to integrate into every interface (converge) that may be required in every industry.

All in one solutions, may be fine in small organisations where the user requirements are very focussed and not wide ranging.

In larger organisations with wider ranges of activites, each messaging ,or real time conversation, ‘technology’ should support the most possible interfaces you can think of, (and multiple interfaces concurrently).

This almost defines a best of breed requirement for each technology - particularly when in a sector that is in acquistion mode - and if you are adopting UC, it won’t be long before you’re in a sector likely to be acquisition minded according to some sources -technology adopting sectors see most acqusition.

So when you acquire a major competitor next month and have to incorporate whatever they are doing into what you’re already doing, you want multi-interface communication products.

It’s plain that in these unforseen circumstances, functionality needs to be priced in a modular fashion, according to the interfaces required and the inherent value of doing so (each interface is it’s own individual case for each technology).

So, am I proposing that in order to have fewer user interfaces, there is a need for more technology boxes and management?

It’s debatable I suppose, but probably.

I’ve seen non specialist technology suppliers integrating essentially as ‘lip service’ to get the original deal, and then support evaporates over the period, especially when the next app needs enabling, and you have to start looking to replace again.

I’m lucky enough to see the best of breed technology I supply stick over a very much longer period.

If I’ve missed anything then it’s likely to be mobile - but that’s a longer conversation.

It’s been a long day, but is there anything else I haven’t thought about?

Powered by WordPress | Theme by Roy Tanck

British Blog Directory
More blogs about unified communications.