UI / UX

I say this with utmost humility - I’ve designed quite a few solutions and reporting applications. Some were very simple while others had varying degrees of complexities. But, in both cases I’ve had similar feedbacks from the users - it helped them do their work more efficiently and they were pleased with the end results.

Computers have been in our offices for more than three decades now and more recently mobile phones and tablets have also found their place in office computing. Even after so many years of usage - technology at work for many people is all about compromises. Internal systems are often cluttered, overly complex and offer tons of features built by geeks for geeks. The problem is that most people don’t speak geek - and probably they never will.

The point that I am trying to make here is the importance of good User Interface (UI) which will most likely translate into better User Experience (UX). UI is one of the vital part of any software, it ascertains how easily you can make the software do what the user wants to achieve. UX on the other hand is about how the user feels before, during and after the task is accomplished.

If you are into software development - make sure you give your users/clients a solution that delights them. Remember! A powerful software with a poorly designed UI has very little value. If you are a user - learn and understand the system well, give it some time - it will reveal itself. If it is making your job harder, then it’s time to seek something new.

Below I’ve listed some points, they may help developers think from the user’s perspective. The same list may be helpful to users who will be involved in specifying requirements or testing the solution.

• Make sure the application is consistently quick to load. A well designed splash screen with graphics and logo would arguably be a good idea if it takes a bit longer to start. Splash screen typically notifies the user that the application is in the process of loading. The idea is to keep the user informed about what’s happening. Always give feedbacks. (A rectangular box that appears when you load MS-Outlook is one example of a splash screen)
• Make sure the data entry forms are uncluttered and consistent throughout the application. They shouldn’t look like Christmas trees. Make each step purposeful and relevant. Don’t make the user click through extra steps.
• Make clear exits. That means never get the user into a corner from where they don’t know how to get out again.Always make sure if they are stuck, there is an easy way to get out from that screen. Give them a chance to undo.
• Prevent users from making mistakes. Use proper validations, input masks, etc. Even with best of systems - errors happen. Sometimes it is the application that has malfunctioned, sometimes it may be the user's fault. Whatever may be the reason, these errors - and how they are communicated - can have a huge impact on the way someone experiences the solution. The error message should be like a conversation with the user. Make sure it is courteous, understandable, friendly, jargon-free and helpful.

• Reward the user for using your product. The example here can be - well designed, easily accessible  reports. The report should be a useful piece of information with pertinent visuals. Sadly many reports are loaded with texts, boring facts, and dull numbers that feel like punishment to read. Where applicable - let the user view the information from different angles.

There is a lot that can be added here and I would highly appreciate if you can share your experiences via comments. Thank you & happy computing :)