Why the User Interface Matters

Not very long ago, maybe even yesterday, it was reasonable to expect that your line of business applications looked something like this:

Credit to StuffThatHappens.com by Eric Burke

Though Eric Burke’s comic pushes for the need for simplicity, within the context of business requirements, simplicity is rarely an option. While a deep investigation into why data is needed or why a work flow exists may occasionally identify an outdated requirement, user input is needed by one system, team or another. In the past, all of these requirements often led to interfaces like the ones above, but that expectation is rapidly changing.

While it would be easy to blame attractive new interfaces from Apple, Google and even Microsoft for the change in expectations, there are far more bottom line reasons for improving the user interface. An application that provides an intuitive interface can decrease training costs. An application that provides useful feedback for incorrect input can reduce escalations and errors. An application that shows and hides data in accordance with the user’s current task allows the user to become more efficient.

For application development teams, just meeting the feature requirements is no longer sufficient. Applications should be judged by how easily users can be trained and user efficiency once they’ve learned the application. Business metrics, such as input error rates, should also be a factor in the evaluation. These metrics are just as important as the number of features implemented.

Jim Rush is a Product Development Manager for Enghouse Interactive’s Voiyager product line. When he’s not busy creating new features for Enghouse Interactive, Jim enjoys woodworking.