Sexy Software, The Enterprise and You
I original skipped over Robert Scoble's post, Why Enterprise Software Isn't Sexy, it just seemed too obvious to be worth reading in much detail. I've been working on software that sells to enterprise customers for the past 6 years or so and no one cares about it, but release a poor version of that software for the consumer space and everyone goes ga-ga over it. EditLive! and eWebEdit Pro have been bringing WYSIWYG editing to the browser for years and no one cared because they were sold to the enterprise, but when Google put out Google Docs everyone went crazy about it, even though it has half the functionality and twice the bugs.
There's a ton of people going into the obvious reasons why people don't care about enterprise software, mostly because the vast majority of people don't ever have to make decisions about which enterprise software to use. Bob Warfield has a pretty good response to most of that commentary.
I tend to think that the difference between consumer and enterprise software isn't in the actual technology - it's in the sales processes. Consumer software is sold on the basis of high volume, low prices whereas enterprise software has very little volume and very high prices. It's amazing how much comes out of that very simple difference.
With huge numbers of direct customers, consumer software providers are outright scared of support costs. They have to make the install seamless because they don't have the resources to help people install it. They have to make the product high quality because they don't have the hands on contact to find out about half the problems and they don't have the support resources to handle the feedback they'd get anyway. There's almost certainly a free download that you can get started with straight away so everyone can get their hands on the product to try it out and talk about it - right then when they hear about it.
Enterprise software however, often close fewer than 100 deals a year (I know many enterprise companies who close less than 10 a year and are still doing ok). The price points are huge and the sales cycle is much, much longer - at least months, if not years. Ephox has had potential clients that took over 2 years to close and we tend to have relatively short sales cycles. That means that a client of enterprise software is going to hear from at least one sales person directly, usually multiple sales people, pre-sales engineers, professional services etc etc etc. Enterprise sales require building relationships with clients, not just an online store. That relationship and the cost of the sale means that you are selling your support services as much or more than the product itself. Quality doesn't matter anywhere near as much as long as you can show you have guaranteed response times and the support team to get things working again. Installation is a nightmare because you're going to be working with a professional services team or a technical partner anyway. The cost of all those people doesn't seem that much because the software itself is so expensive - if spending another $50 000 makes your $300 000 CMS roll out successful you'd be a fool not to pay it. Try asking a consumer to pay an extra 15% of the purchase price to get help to install the product and it's not going to end well but that's expected in the enterprise sales model.
Don't forget as well, that consumer software generally sells directly to the end users, whereas enterprise software sells to CIOs, CEOs and CTOs who force it on their employees. A bad UI generally kills a consumer application but it's par for the course with enterprise software because enterprise software isn't sold to the people who actually use it. Listen in on a sales call for enterprise software and you'll hear all about scalability, integration, security, interoperability, support, customisation, more support and corporate compliance. The UI only gets a passing mention and then it's usually about how everything will be in one place so employees will be more productive or how they'll have all this information at their fingertips rather than on how much user training is required or how many clicks it will take to do anything. We can deal with usability problems through our support team - we mentioned how reliable our support is right?
The bottom line is that most enterprise software sucks big time. It may provide huge business benefits over manual efforts or it may make new business models and processes possible, but the vast majority of people are the ones that have to use it and the UI sucks. Just look at the problems enterprise roll-outs have with user adoption and you'll see that but it just isn't affecting the sales cycle enough to cause change. The good news is that it's starting to change - all this buzz about consumer software is starting to get the more adventurous knowledge workers into technology and make them aware of how things should work and that's starting to put pressure back up the business chain and affecting the enterprise software process. Expect to see consumer technologies and styles making the jump over to the enterprise more and more as businesses realize that it all those extra clicks add up to serious costs. Just don't expect it to change fast - nothing in the enterprise ever does.

December 11th, 2007 at 4:50 pm
This might seem like a pedantic post, but found it made the post difficult to read so thought you may be interested.
You haven’t used non-breaking spaces for your thousand’s seperators in $50 000 and $300 000. In firefox fullscreened 1280 * 1024 line breaks after the 50, so was reading this as
… - if spending another $50
000 makes your $300 000 CMS …
Kind of read it as ‘if spending another $50, emergency number makes your $300 000 CMS …’
December 11th, 2007 at 5:06 pm
That is particularly pedantic. :) Should be fixed now if Safari’s playing nice with things. Sadly I think I forgot to mark it as an unimportant update, sorry about that…
December 13th, 2007 at 8:54 am
Word ‘em up!
AJ for PM
Nice post.
I’m thinking of making this one of my career goals - making enterprise software not suck.
It’s not just that it isn’t “sexy”, its just that usability is not a high enough priority. In fact, I find that in lots of software.
One of the traps in engineering large-scale software, is specifying the UI. You can’t specify a look-and-feel - you can’t specify usability. Not easily, anyway. This is something you need to experiment with - this is where prototyping and agile process excel.
The other trap is using a tight design and spec for the other functionality of the system. As such, the UI is left to the wayside. In this scenario, the UI is only required to provide access to the functionality. This is one path to the situation where the UI is implemented in a way that makes sense to a developer, or to the system, rather than the user.
In fact, this problem isn’t just in enterprise software - too much software is like this.
Related to this, is the issue of tightly coupling the UI with the lower tiers. This can tie the functionality to the usability. A UI needs to be flexible so you can refine it. A user action is not always 1:1 with a system function.
If software has users, it requires usability. Think about the use cases from a user’s perspective. Think of what the user intends to do, what information they expect to have to provide, what actions they expect to perform to achieve this, and what format will the end result take. Also think of how they will discover features - what need will drive them to seek a specific feature, what button (or other UI element) will they look for and where they will start looking for it.
The other trap is not refining a UI. The first cut is never good.
Yet another trap - developers know how to use their own software - they know how it works because they built it. Test drive it with someone else. See how they attempt to use it, and how they actually use it.
Still more traps - for god’s sake keep your UI’s simple.
- be flexible in your input
- don’t clutter the screen
- make features obvious
- don’t whinge at the user unless you really have to
- actually write human error messages
- use common UI metaphors that the target user will be familiar with
- make it fast
December 13th, 2007 at 10:34 am
[...] Adrian Sutton on why sexy and enterprise don’t go hand in hand: Don’t forget as well, that consumer software generally sells directly to the end users, [...]
December 13th, 2007 at 11:20 am
[...] « Sexy Software, The Enterprise and You [...]
December 14th, 2007 at 11:48 am
[...] This of course leads us to the question, is the enterprise software arena ripe for an upstart with a far more sexy, usable product to come in and take a lot of market share? To a degree yes, but only if they can also solve the existing problems that are well served by enterprise software - support, scalability etc. All the things that the enterprise sales process currently focuses on. [...]
December 14th, 2007 at 11:23 pm
[...] Symphonious ยป Sexy Software, The Enterprise and You “Listen in on a sales call for enterprise software and you’ll hear all about scalability, integration, security, interoperability, support, customisation, more support and corporate compliance. The UI only gets a passing mention…” (tags: enterprisesoftware enterprise2.0 software) [...]