News for hackers. Stuff that matters.
Re:Products For People Who Make Products For People by neilk on Saturday September 25, 2010 @03:38PM (#1727623)
There is really no mystery about UI. Yes, it requires skill and a deep knowledge of how humans process information, and even a touch of design genius.

But the real problem is that most shops can't measure usability in a fine-grained way. And yet everyone does have some idea that it's really important. Consequently they are bamboozled by anyone who purports to have such expertise.

For the most part, so-called usability experts are really just graphic design snobs. They have a certain aesthetic they like, which is arguably "cleaner" and has more white space. So the page might be better organized but that's nowhere near what true usability is.

Real usability work is about trying to understand how the user is thinking. What their mental model is. What their goals are. In what context they are trying to achieve a task. Not just how their eye is scanning for information.

Anyway my point is, when it comes to real usability work, programmers are just as (un)qualified as graphic designers, marketers, or any other kind of "product" person. Arguably the designer is supposed to have a larger toolbox when it comes to possible graphic treatments, but the programmer also has a toolbox of quantitative methods, experimentation, and a deep understanding of how the system could work.

Re:Products For People Who Make Products For People by StavrosK on Saturday September 25, 2010 @08:06PM (#1728185)
You know, I thought I had UI design mostly figured out, using a few simple rules:

* Minimise the total number of clicks needed to access the sum of the program's functionality.

* Make frequently-used functionality easier to reach than rarely-used functionality.

* Don't have more elements in the UI than is easy to parse quickly.

* No surprises.

However, after reading this article, I get the feeling that it's a more arcane art, which not many people know. What are some simple rules about good UI design, in your opinion?

Re:Products For People Who Make Products For People by neilk on Sunday September 26, 2010 @12:17AM (#1728520)
In my opinion it isn't arcane, at least, no more arcane than other "soft" design fields. But the simple rules are complicated to follow.

Your first three principles are about efficiency. That's a big part of usability. When you reduce clutter, you make it easier to use by clarifying the next action the user should take.

But "No surprises" is rather complex. It means that you not only have to explain what you are doing, but also work with the user's mental model, which might be totally wrong.

Here's an example from my current project. We are designing a web form to upload images and video to Wikipedia. In 2010, the users' model of media uploads comes from Facebook, ImageBucket, and maybe Flickr. Even after you make them click on a box that says they give up their own rights before proceeding, they don't understand what they did. Apparently people's mental model just continues on blithely until it smacks against a major contradiction.

So we've tried various metaphors. "License your work" was replaced by "Release rights", and the next iteration is going to be "Donate your work". That wording was the suggestion of a usability testing and analysis firm we hired, by the way. So it does take a certain amount of inspiration to come up with alternatives, but recognizing where the problem areas are is just a matter of measurement.

Inspiration is aided by just having a bigger bag of tricks, too -- knowing common problems and solutions. For instance, if there is so much to do on one page that users are finding it overwhelming, it is helpful to break it into multiple steps (a "wizard"). That's another approach we have taken.

Anyway, I'm not sure if my expertise with usability is so deep that I could pronounce just a few principles. Maybe "reduce cognitive load to the minimum" is one, which has been more memorably distilled by Steve Krug as "Don't Make Me Think". Since we want to avoid onerous information transfer and cognition, there are some models of communication that might be helpful here; a classic text on human communication is The Responsive Chord, by Tony Schwartz. He argued that most communication is about activating stuff you already know (at the right moment), which you can see at play in the example I gave.

But ultimately it's about motivating human behavior, so it's only about as complex as the human heart. ;)

Re:Products For People Who Make Products For People by StavrosK on Sunday September 26, 2010 @07:01AM (#1728965)
Thank you, that's very interesting. You can't get everything right the first time, but yes, it doesn't seem to be something magical that you don't have any control over (other than praying to some UX god), either.
Re:Products For People Who Make Products For People by Qz on Saturday September 25, 2010 @10:29PM (#1728371)
One of the key things about UI design these days is that it's very easy to fall into the 'widget trap'. This is where you have some content you want to interact with, and instead of really analyzing what the best way to interact with it is, you just throw the data in a standard widget, like a listbox or textarea. It might be a really nice listbox or textarea, but there may also be a much better way of interacting with the content that wasn't explored. Widgets are the typical area where this happens, but it can be generalized to any situation where people just go with pre-established conveniences rather than try to find the best solution.
Re:Products For People Who Make Products For People by StavrosK on Sunday September 26, 2010 @07:03AM (#1728968)
The problem with that is that widgets are your language, so you tend to think in them and analyse the problem in terms of widgets. It's sort of the Sapir-Whorf hypothesis applied to UX, it's hard for someone to think in widgets they don't have.
Re:Products For People Who Make Products For People by Qz on Sunday September 26, 2010 @10:52AM (#1729232)
Right, but that's what I'm talking about. Widgets should never be your language. If you think widgets are your language then you've fallen into the widget trap.
Re:Products For People Who Make Products For People by arnorhs on Saturday September 25, 2010 @10:14PM (#1728360)
Solid list.

Personally, I spend a great deal of time putting myself in the mind of the user, trying to figure out how we as humans visualize things and simplifying the actual underlying task at hand.

The list you summed up does work for 95% of all cases - especially if you're just thinking about a "website". However when you're trying to create something new or working with some new concepts you have to imagine how the user pictures things so that it matches his thought pattern as much as possible.

This also includes placing things were the user is most likely to look for them etc.

Re:Products For People Who Make Products For People by fun2have on Sunday September 26, 2010 @03:23AM (#1728739)
ISO defines usability as "the extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency and satisfaction in a specified context of use.

So your right with the number of clicks, but you also have to make sure that the user can complete the task (effectiveness), and that they are happy (satisfaction). From our own research the three; effectiveness, efficiency and satisfaction are very highly correlated together.

Re:Products For People Who Make Products For People by jimbokun on Saturday September 25, 2010 @08:45PM (#1728242)
If you nail all the things you mention, you'll probably be far ahead of most software out there.
Re:Products For People Who Make Products For People by ahoyhere on Sunday September 26, 2010 @11:01AM (#1729249)
Please don't take offense, but that's a very programmer-like approach to usability.

Usability is so much more about mental models than it is about efficiency, about helping the user feel confident & safe, than about a lack of surprises. Sensible hierarchy and visual relationships are a big thing that most people seem to forget.

Workflow, too, is critical. I've used a lot of software where every screen is mathematically, scientifically "usable" but the software overall was crummy because it duplicated a workflow from another piece of software which had got it wrong initially.

For example: 100% of email clients. Feed readers. Project management tools. They're all the same.

Surprises are actually very good in many cases. Even "ease of use" is something you don't actually always want.

My interfaces break all sorts of rules like "use standard widgets" and "conform to expectations" and "no surprises" -- but that surprise then results in an "AHA!", great enjoyment and power, and that's why people write love letters to our customer support account.

Re:Products For People Who Make Products For People by elbenshira on Saturday September 25, 2010 @05:30PM (#1727922)
You are exactly right. Making usability and user design into a science is difficult because we'd be trying to model the human mind, which is, well, pretty much impossible.

For example, in the information retrieval community, companies like Google continue to employ a lot of people to mark search results as relevant or not. Even with all this data, it's still hard for us to quantify what is "relevant" to a user. Likewise, it is hard for us to quantify what is "usable."

But even though the programmer may own this toolbox of quantitative methods and whatnot, most of them do not use it when it comes to usability. Why? Because the toolbox is quite empty. The advantage that these "snobby" designers (just like how programmers are "snobby" about their choice of programming languages and tools) have over programmers is that designers have more empathy towards the everyday man. So there is some emotion involved. Sure, there might be a science behind all of this, but since no one figured it out yet, we'll have to go use our intuition of what a good design is.

Re:Products For People Who Make Products For People by bkrausz on Saturday September 25, 2010 @06:44PM (#1728056)
Fortunately I think this is changing: tools are coming out that make running quantitative UX studies easier. Services like Optimizely, GazeHawk (disclaimer: that was a shameless plug for my company), UserTesting.com, etc are becoming more commonplace, bringing the barrier to entry for a UX consultant who is actually useful down.

In the future I imagine there being plenty of UX consultants who, rather than having a strong education in the psychology of websites, instead is experienced with the tools necessary to evaluate a design and make recommendations. Then there will be graphic designers, marketers, etc who are actually qualified to work with usability.

Re:Products For People Who Make Products For People by ant5 on Saturday September 25, 2010 @07:42PM (#1728144)
The problem here is that good UX isn't borne of qualitative analysis -- you have to build something worth analyzing to begin with.

Once you do start analyzing, what do you do with the results? You can try to make small tweaks -- it can be worthwhile if what you have is already good. If what you have is bad however, no amount of rigorous analysis is going to solve the artistic problem of coming up with a cohesive vision of something better.

Re:Products For People Who Make Products For People by ahoyhere on Sunday September 26, 2010 @11:04AM (#1729255)
Yesss.

The way I describe this to people is: "Usability science can only test a hypothesis. It doesn't give you a hypothesis to test."

Not to mention the problem of hill-climbing… you may think your test results are amazing, but you can't tell if you're really at a peak or in a valley with a lot of mist obscuring a potentially even higher peak..

Re:Products For People Who Make Products For People by jeffclark on Saturday September 25, 2010 @03:57PM (#1727668)
UI designer = "white space"

UX designer = "mental space"

Re:Products For People Who Make Products For People by alextgordon on Saturday September 25, 2010 @04:32PM (#1727750)
It's easy to redefine the meaning of a term if it's rendered as an acronym.

    User Interface Designer = "white space"
    User Experience Designer = "mental space"
Now how arbitrary is that? What is it about "Experience" that implies thinking and "Interface" that implies a lack thereof? What about all the designers unfortunate enough to come before the term "UX" was invented? I suppose Jef Raskin was only ever about white space.

Let me suggest an improvement

    Mediocre Designer = "white space"
    Good Designer = "white space and mental space"
Re:Products For People Who Make Products For People by binomial on Saturday September 25, 2010 @06:37PM (#1728044)
Well, there's also the fact that some "UX" guys don't have any great ability in graphic design, but are great when designing the use and flow of an interface. It's not necessary that an ability in the latter implies similar ability in the former.
Re:Products For People Who Make Products For People by jacobolus on Saturday September 25, 2010 @09:09PM (#1728278)
Which "UX guys" are these you’re thinking of, who don't have a competent understanding of graphic design? I posit that it is irresponsible to claim to be a "UX guy" and not try to learn quite a bit about spatial hierarchies, data presentation, human response to colors and visual relationships, etc.
Re:Products For People Who Make Products For People by binomial on Saturday September 25, 2010 @09:55PM (#1728333)
Though graphic design surely includes all those things you've mentioned, I was using it in the sense that most "web designers" might use it, as in the ability to make pretty stuff in photoshop. I'm not sure that someone who can, for instance apply Tufte's advice on data representation, necessarily also makes nice looking logos.
Re:Products For People Who Make Products For People by jacobolus on Sunday September 26, 2010 @01:04AM (#1728573)
Equating “don't have any great ability in graphic design” with “can’t draw logos” is applying a pretty narrow definition. Someone who just “makes pretty stuff in photoshop” should probably be called a “digital illustrator” or a “photo retoucher”, or a “digital imaging expert”, not a “graphic designer”.