The cost of NO UX

2013-8-12
How much does UX* cost?  Why do we need UX?

by Iain Duncan (@Iain_Duncan)

 

"How much does UX* cost?" Is one of the most commonly asked questions and is normally preceded by "Why do we need UX?"

 

To answer the question of cost itʼs probably best to take an "outside in" approach. After all, the person using your product or software sees it from the outside in. They donʼt actually care about how the code was written, or how your lead programmer thought it would be clever to add a talking paperclip to the final product. All the customer wants is something that works, is forgiving of their mistakes and is a joy to use

Cost can be looked at in the same way. By seeing how much a company stands to lose, or is losing already by not incorporating UX into their product and business development, you can see how much UX is worth.

Taking the "Outside In" or "Front to Back" approach to the cost justification of UX is one that lies in the truth that your users experience your product that way around. So letʼs look at the cost of having NO UX , rather than the antithesis.

(Disclaimer: We are a company based in Cape Town, South Africa and Zurich, Switzerland so therefore have used local currencies as well as USD in the following examples.)

TeleHit a fictional mobile phone operator based in South Africa has developed a new website (with no UX design) for their customers that has produced the following results:

 

 

This is an extreme case to make my point and it must be said that doing good UX wouldnʼt mean that all the costs above would magically vanish or that a bad User Experience is to blame for every part of these losses. Looking at this conservatively even a 10% reduction would be a big saving. This example almost says it all, but just in case it doesnʼt, hereʼs a list, mmmmmm we all love lists.

 

The cost of having no UX can be broken down into the following:

Development

  1. Increased development time
  2. More late changes
  3. Incorrect features and functionality
  4. Frequent requests for changes by users
  5. Future versions and a boatload of fixes

Sales

  1. Difficult to use product
  2. Reduced competitive edge
  3. Fewer satisfied customers
  4. Less repeat business
  5. Bad press

Use

  1. Loss in productivity
  2. More training time needed
  3. More user errors
  4. Lessened quality of service
  5. High customer turnover

Support

  1. Cost of producing more training materials
  2. Help line/call center costs increase
  3. Help line/call center workload increase

Even lists can be a bit overwhelming so hereʼs the short and sweet version:

 

 

Put money into meeting user needs 
=
Get more money out, through increased revenue and reduced costs

 

 

* Just what is User Experience (UX)?

"User eXperience (UX) is about how a person feels about using a system. User experience highlights the experiential, affective, meaningful and valuable aspects of human-computer interaction (HCI) and product ownership, but it also covers a person’s perceptions of the practical aspects such as utility, ease of use and efficiency of the system. User experience is subjective in nature, because it is about an individual’s performance, feelings and thoughts about the system. User experience is dynamic, because it changes over time as the circumstances change." 
- Wikipedia

"All aspects of the end-user’s interaction with the company, its services, and its products. The first requirement for an exemplary user experience is to meet the exact needs of the customer, without fuss or bother. Next comes simplicity and elegance that produce products that are a joy to own, a joy to use. True user experience goes far beyond giving customers what they say they want, or providing checklist features. In order to achieve high-quality user experience in a company’s offerings there must be a seamless merging of the services of multiple disciplines, including engineering, marketing, graphical and industrial design, and interface design." 
- Nielsen-Norman Group