Three reasons why Enterprise software, as a rule, offers such a poor User Experience
Posted on 5th July 2010 in Business & User Experience
There is a general rule of thumb that applies to the World of software: if an application is a consumer application then to be successful is must be well designed, easy to use and well thought through. If, however, an application is an enterprise application the user experience is not nearly as important as the feature list.
Having spent many years designing and developing enterprise applications I can tell you that there are many people who build enterprise applications that truly care about creating great user experiences, and there are many clients who list it as a requirement when purchasing their systems. So why is it that using so many enterprise applications is such a bad experience?
I would suggest that there are three primary reasons;
1. The people who buy the software are not the end users
The first problem lies with the buyers, and it may well be the biggest problem of all. I have never been in any sales meeting where a potential customer has brought along one of the people that will actually use the application to help evaluate it. Never. I’ve given plenty of demonstrations to and had plenty of feedback from managers, team leaders and senior executives, but never from someone whose day job will involve using the application. Managers need to learn that they are not the audience for the application. They need to understand that their opinion of the interface is not an evaluation of the user experience and they need to understand that the interface (however pretty it is) is not the user experience.
2. Software designed to do everything for everyone will not be very good at any one thing
The second problem lies with the software vendors. Many vendors will do two things to compete: add more features to their products and make their products infinitely configurable. Both are aimed at making the products appeal to the widest audience possible, but both strategies result in products that are either too confusing to use or don’t quite do what you need them too. Imagine a car that was designed to win a formula 1 race, fit a family of 5 in the back, go off road, be driven on water, be driven in cities and replace tractors on farms. It wouldn’t work right? Well software designed to do everything rarely does either. (A note to buyers: just because a feature is listed as present in an application does not mean that it will work how you expect it to, or how your organisation needs it to.)
3. It is really hard to define a great user experience, or prove that a system offers one
The final problem is that it’s almost impossible to define what makes a great user experience. What works for one person will not for the next. In most sales situations that I’ve seen there is a technical buyer, a business buyer and someone with the authority to spend money. For the technical buyer benchmarking the system is easy; they ask about infrastructure, redundancy, back up routines, disaster recovery and service up-time history. For the business buyer the questions revolve around feature lists; “does it do this, that or the other?” “Can we use it to do these 4 key things?” “What reports will the system generate?” For the money folk the questions are about pricing, return on investment, service levels and contract length. All of these questions can be easily answered with fact based, well evidenced answers.
Ask if the system offers a good user experience and how would someone prove that it does? How would a buyer benchmark it against competitors? It’s easier just to ignore the question and focus on evaluating the more tangible aspects of the product. No vendor is ever going to claim that their product offers a bad user experience are they?
How can we combat these problems?
So how can we deal with these problems and start forcing enterprise application designers to build better user experiences?
Buyers: Test, test, test and then test again
Organisations looking to buy enterprise software need to start testing applications as they will be used in their organisation and they need to be conducting this testing with the actual people that will be using it day after day. In a World where money talks, and customers are king, the only way that vendors will focus more on creating fantastic user experiences is if their customers ask for it. That’s why consumer software, as a rule, offers a better experience; we as consumers demand it.
Vendors: Focus on what works for your target audience
Enterprise vendors then need to stop trying to out do each other with more and more features in their products, and start focusing on delivering simple, easy to use tools that do less but get the job done. Make one version per market segment if need be, but make sure that your products stay true to your intended audience and don’t become so generic that they don’t work for anyone.
The rest of us: Work on defining great experiences
The challenge to the rest of us is to help define what makes a great user experience and help both buyers and vendors understand how to test products in meaningful ways to ensure that they are as great as they can be. No small challenge, but then small challenges aren’t as much fun are they?
Comments (6 so far)
[...] This post was Twitted by steveworkman [...]
Twitted by steveworkman on the 5th July 2010 at 5:01 pm
I’d like to rally your first point a little, if I may:
Two years I was involved in the procurement of an ERP system for a large news corp to handle backend finances and some logistics – sales, collections, procurement, content inventory etc. They employed our small band of consultants for about 10 weeks to help them decide on the right system to use.
The functional needs were complex, but nothing that the two biggest suppliers couldn’t handle. The budget was flexible enough and the emphasis was on getting the job done the best. Sounds like an ideal time to get the users involved and incorporate their hands-on demo use into the decision right?
So, we did. We had a smart, motivated, and above all highly influential team of clients (CFO, Financial Controller, heads of department, down to some on the ‘shop floor’) and over 2 long days we trialled and had demoed to us various functions and features of the software, the performance of which we measured and recorded for later comparison.
And the results were about the same for each vendor. “Looks a bit tricky, but I’m sure we’ll get used to it”.
In the end, it came down to the functional: ease of deployment, integration, training and maintenance. Money mattered a little too. So, somewhat subjectively I thought, did the performance of the vendors’ sales teams over the period of evaluation.
UI didn’t feature highly at all.
A few things struck me:
– Enterprise software is not changed often (due to the various costs of acquisition, deployment, training, disruption, security, maintenance) and so the old software was OLD. The UI was beyond abysmal (green screen) and pretty much anything more recent than Windows95 would have an acceptable interface.
– In fact the status quo (functionality and UI-wise) was SO awful that pretty much any of the replacement software under consideration would reduce their workload by about 80%
– Partly due to this workload, only a limited number of trusted staff (whose opinions are deemed to matter) were able to provide input to the decision making process on a regular basis
Some thoughts:
– Large scale demos and trial periods are hard to do in an enterprise situation where the emphasis is on making money (even just surviving) through today. Some real users need to be given free time and resources to get up into the crow’s nest and look to the horizon. Demo suites, week-long use cases, mirroring workload on two systems all would help in the decision
– Enterprises are complicated, often needlessly, but that’s another discussion. If you have 15 sprockets for your widget and the pretty software can only handle 12, then the ugly one that can handle 99 sprockets will win.
– There’s no time (this is a biggie): “The budget for the new system was set this year, we need to buy it this year. We WILL buy a system, it WILL be one of these.” There’s no null case, all the vendors have to do is be better than each other.
Jon on the 5th July 2010 at 7:00 pm
Hi Jon,
Thanks for sharing.
I can empathise with your story. I’m sure it’s a scenario that’s played out day in day across the enterprise community.
So many companies list the UI and UX as important when they are initially looking for a new system, but then spend no time evaluating either when it comes to picking the winning solution from their gathered vendors.
The sooner they do, the sooner the UI and UX of enterprise applications will be better designed. I look forward to that day.
James on the 20th July 2010 at 3:17 pm
One more thing to add for combating the problem. Ensuring that the buyers of enterprise software have allowed time and budget for UX design. Often it is left to the developers to plop fields on the screens rather than to actively design the process. There needs to be a real, iterative, engagement with representative user groups which allows active engagement across the user base.
David Reinhardt on the 20th July 2010 at 7:59 pm
Hi David,
I could write another whole article on the need to build in time and budget for designing the UI and UX of bespoke solutions. You’re right, so few project plans leave room for quality experience design and focus far too much on the technical side of the solution design.
Again, I think this is largely because the experience design is so intangible, and if we’re honest about it, because so many of the consultants and programmers who design bespoke enterprise solutions are technical folk who got into the game because they enjoy code. They get excited about which technology they will be using on a project, which development framework they’ll be using and how agile they can be. They don’t really get too excited about the soft side of the project, and having to think about the user experience design isn’t something that comes naturally.
Thanks for your comment
James on the 21st July 2010 at 12:01 pm
[...] Three reasons why Enterprise software, as a rule, offers such a … [...]
The Benefits of Being a Home Business Owner-business on the 21st August 2010 at 12:36 pm