The sign of a good interface for a product meant for general public consumption is when the audience it’s designed for is delighted to use it. This includes but goes beyond simple matters of usability, architecture or aesthetics, and lies at the heart of how people are wired to interact with the world around them – and their attitudes and reactions both when they see it and after they interact with it. Failing to design it right can make your website seem cold and lifeless.
Think of the last time you shook someone’s hand. When you looked the other person in the eye, did he look back at you? Did his smile seem sincere, warm and friendly? Could you feel the heat radiate from his palm as his fingers gently squeezed around the ridges of your hand? Did it last a couple shakes – at least three seconds?
What makes such interactions pleasant is that they are welcome, warm and inviting. We find comfort in their predictability. We like it when people react and respond to us appropriately, and we are either bored or shocked when they do not.
Unlike people, computer interfaces (including websites) don’t think on their own. They can’t identify others’ intentions and sensibilities to respond appropriately. They require people – designers and programmers – to identify, predict and enable responses to user behavior so that the system works predictably, intuitively and in a way that inspires the appropriate emotion.
Put another way, designing a handshake is more complicated than designing something that looks like a hand. A fake hand may resemble something you can interact with, but without the intelligence and warmth behind it, it insufficiently reflects the humanity it represents. It doesn’t matter how much you try to make it look human. You can attach a wrist and arm – heck, the rest of the body. You can dress it up and even take it to a dance. But without that intelligence, without that interchange of appropriate responses to your actions, in the end, you’d just be dancing with a dummy.
Use People-Speak, Not Computer-Speak
Computers are part of our lives and, as such, the distinction between our languages has blurred a bit in recent years. They have changed the way we communicate. Did we say that we’re “processing” something before the popularization of the computer? Without context, we don’t know what a person is talking about when they mention a “desktop” or a “mouse.”
Whenever possible, let your interface do your talking for you. Don’t say “Click to submit” if your interface is obviously clickable (the words “Click to” in this case just act as a barrier between sight and cognitive understanding). Just let them know what it’s doing in their terms, not the computer’s.
And for goodness sakes, pay attention to your error messages.
Caption: Very few ordinary users will understand what this means or what they should do about it. Whether the system commits an error or a user does, the system should help the user recover from it. To do that, it must use language the user can understand.
Give Instantaneous Feedback
For a response time to feel instantaneous, it must take place within one-tenth of a second. A one-second response time, while noticeable, still leaves the user feeling like they are in control. Depending on the request, 1-10 seconds may be acceptable, but at 10 seconds, people lose attention and interest.
Once again, there are a number of tricks you can employ if there’s a possibility that something can take more than a split second.
In such cases, utilize the quicker interactions you have at your disposal – rollover states and latency notifications can be the difference in that first 10 seconds.
Caption: Apple’s navigation design helps people understand that what they are doing is having an effect on the system. Even if network conditions or connection speeds cause the next page load to take a few seconds, the user does not need to wonder whether they did something wrong.
If it’s longer than 10 seconds, be empathetic to your audience’s short attention span. Give them something to watch, read or do in the meantime.
Caption: BounceApp’s whimsical loading animation keeps users from thinking about how long it’s taking to process their request. While this exact approach won’t work for every brand, it fits (and helps define) BounceApp’s personality.
Make the Interface Predictable
Variety may be the spice of life, but inconsistency in interface and interaction design can be a major cause of frustration for the intended audience. Not only do people expect all interface elements to work the same on your own website (internal consistency), but also the way they work on other websites (external consistency).
Caption: One of the early usability critiques of the iPad is that the lack of conventions forces users to learn independent interaction rules for each application they use.
There are a number of methods we can use to make sure an interface is predictable (such as through typography, language, shape, color and placement); it doesn’t mean everything on every website always has to look exactly the same.
There are very few hard-and-fast rules of interface design that cannot be bent for a higher purpose. All design involves a series of trade-offs. It’s just important to understand the principles involved and to intentionally choose which trade-offs you’re willing to make.
The key to making your website (or any interface, really) feel like it’s an extension of you is to make it more life-like and less like a computer.
It is not enough to give attention to shapes, colors, sizes and dimensions. Plan the experience so that the entire system is sensitive to how people interact with it over time, providing appropriate responses to user activity so that the user feels like they are shaking the hand of a real person, not just grasping at a dead fish.
Related Links
First Principles of Interaction Design
The Design of Everyday Things
About Face 3: The Essentials of Interaction Design
No Comments | Trackback | Categories: Planning, Tips and Tricks | Email This Post
Leave a Reply