theme selector

light blue screenshot grey screenshot navy screenshot dark green screenshot red and black screenshot

by Tony Chang

All opinions on this site are my own and do not represent those of my employer.

Creative Commons Attribution License

innovative interfaces

Sep 30, 2005, 02:29am EDT



pie menu One of the main points in User Interface Design For Programmers or any other book on user interface design is that you should design interfaces based on user expectations. I agree with this for the most part, but it makes me sad. It makes me sad because it means that innovative interfaces are likely to fail even though they’re “better.” For example, there are plenty of studies that show that pie menus are superior to traditional linear menus, but they’ll never take the place of context menus. Why not? Because they’re too different from what people have come to expect when they right click.

So to make the most immediately usable product, all you can do is make incremental improvements. But to make a really innovative interface, we need to stop listening (literally) to users. We need to look past what the user says she or he wants and look to what goal the user is trying to actually accomplish. There is always a lot of risk in doing this because lots of people simply won’t get it. They won’t want to take the time to learn a new interface even if it will save more time in the long run and they’ll return to an interface that is familiar.

I see this happen a lot with Gmail. Walt Mossberg recently had an article in the Wall Street Journal comparing Yahoo mail (beta) to Gmail. He concluded that Yahoo mail was better because it more closely replicated the desktop experience (i.e., Outlook). He complains that Gmail doesn’t provide folders, which he has come to expect. It doesn’t matter that most people only have one level of folders [1] making them identical to labels. It breaks his expectations of how to organize email.

So when people say they want folders, what do they really want? In most cases, the goal is actually to find messages quickly; folders are used to aid in the search process. So when users say they want folders, what they really want is a fast way to find email. When I’m trying to find a message, I don’t really care how my email is organized, so long as I understand the structure and can quickly find my email. But labels (and search) provide this functionality, so why do users still complain about the lack of folders?

The other reason people want folders, is because they like to be in control. People understand folders and thus using folders provides control. Labels feel slippery to new users (there’s no structure! there’s no hierarchy! oh no!). It’s not that folders are better, it just makes some (anal retentive) people feel better.

So what does that mean? It means that some people will love the new Yahoo mail and hate Gmail. But that’s ok, that’s just the physics of passion.

[1] In the current Yahoo mail, you can’t nest folders anyway making them identical to labels. Is this the case in Yahoo mail beta?

DC at Sep 30, 2005, 09:22am EDT

I think there’s an added problem here and that is that user tests can only get a person’s immediate reaction. It’s really hard to do a study where you find out how someone will work with software after they’ve had it long enough to get used to it. In fact, I think qualitative user tests are often totally flawed for just this reason (and I do such things all the time). It was interesting to do my own personal evaluation versus the other guy’s because I felt like he had used Gmail for testing purposes and not to the large degree necessary to really “get it”.

One other note is that it is really easy to introduce some error that won’t become apparent through user testing. So, I’m sure that they did testing on the “conversations” feature, but it was only after I had used it for over a year that I realized that sometimes I just miss emails if there is more than one new one in a conversation (I read the first one and think it was the only one because the others are scrolled off the page and/or below my reply box). How could they predict that? (And more importantly, how will they ever fix it?)

Of course, there’s always the “have both ways” way. I think mouse gestures in firefox is a good example of this one. Unfortunately, as you’re thinking, this won’t work for everything. Maybe what we really need to do is create a “funky” program (like an mp3 player or something) and introduce a lot of weird interface features into it - just to get people used to them for later products that we care about.

allowed HTML: a, blockquote, ul, ol, li, dl, dt, dd, b, i, strong, em, code, abbr, acronym, sub, sup, span, pre

allowed HTML: a, blockquote, ul, ol, li, dl, dt, dd, b, i, strong, em, code, abbr, acronym, sub, sup, span, pre