What's popular?
- Getting new Moleskine
- "Can you endorse me?" considered harmful
- Weekend reading: Software projects planning and estimation
- Intrinsic motivation vs. Extrinsic stimulus
- Language you speak affects the way you think
- SOA Manifesto
- Metrics that mean
- Getting feedback from users
- Creating great presentation visuals
- Weekend reading: software complexity
What UI is really about?
Recently I happened to witness how users interact with two uncommon types of systems: medical device to test and measure how electric impulses go through tissues and air tickets selling terminal in local tourism agency. I was literally amazed how similar these two systems were from UI standpoint.
Was their interface intuitive? No, not nearly! Medical system had so many different items on the screen with labels I could not even parse let alone understand what they mean. It even did not have a keyboard in usual sense – only about 20 or so buttons. Air tickets terminal stared at the clerk with black screen waiting for him to type in some commands. Definitely not the kind of intuitiveness you would expect from XXI century software, more smells like 1980s. But we’ve got much beyond that with toolbars, tooltips and context help, aren’t we?
Was their interface effective? Oh, yes! With both of the systems users were able to complete required operations with just a few key strokes not wasting the time on moving a mouse, going through menus and so on. If you are able to serve 20 people who want to buy tickets per hour instead of 18 that makes difference. If you are able to diagnose 7 patients per hour instead of 6 it is even more important.
Do you know what I want to say here? Think of how many minutes your software will save for its users multiply that by frequency of use and feel satisfied only when you save your users 3-digit number of minutes per month.
Related Posts: