When you look at a business level, there is a growing recognition that providing good UX in your product or website has some serious commercial benefits. Making it easy and pleasurable to use is likely to lead to increased customer satisfaction, which in turn can achieve greater brand loyalty or stickiness. In terms of sales, good UX can give the competitive edge over other products with similar functionality and if your users love it, they will recommend it to others.
What about back office software?
The back office users we are talking about here have two important characteristics that make them quite different to the customer-users that most UX literature is focussed on.
- The back office user is not following their own agenda. Back office users are paid to be there and use the software, so the stickiness of the experience, whether the user would recommend the software and even user satisfaction to an extent are not major commercial risks. It is the user’s job to use the software, so they have to continue to do so regardless of the experience.
- The back office user does not require highly learnable and discoverable software. In most cases, back office users are provided with training and time to learn how to use the interface, or at least plenty of practice and repetition. This is not always the case of course, but it is reasonable to design for a longer onboarding period.
Reducing the requirement for an interface to be highly learnable and discoverable, and shifting the emphasis away from trying to hold on to users can result in a very different approach to designing an interface. But if our back office users are so low risk, why should we bother about user experience at all?
Perhaps the biggest motivation for investing in good UX in back office systems is the potential for improved efficiency and productivity of staff. Employees cost money and having less of them is an attractive prospect for most businesses. Making your user interface more usable can save a lot of effort – fewer clicks, less duplication of work, greater accuracy/fewer user ‘errors’ and better designed workflows can all contribute to faster smarter working.
And so we start designing our interface not for the novice user, but for the user who is going to use the system day in, day out. Maybe the interface for our customer-user was visually attractive, with simple choices broken down in to multiple steps. The interface for our back office user perhaps allows them to enter a lot of information very quickly. Maybe it is keyboard-centric. That all depends on what the system is for and we’ll let the user tests decide the specifics!