usability archives

For a lesson in why customer experience matters, read Mark Hurst’s Why Amazon sells used diapers (and Diapers.com doesn’t).

posted by ted on Wednesday, Feb 13, 2008

Have user skills improved on the web? “Even though users are remarkably good at repeated tasks on their favorite sites, they’re stumped by the smallest usability problems when they visit new sites for the first time.” Jakob Nielsen’s recent study suggest that usability guidelines remain constant.

posted by emmy on Thursday, Feb 07, 2008

8 More Sign-In Design Mistakes from Jared Spool, following up on his previous sign-in design article. My pet peeve out of this new list is Mistake #10: Requiring Stricter Password Requirements Than The NSA. I hate sites that make me think of a password so cryptic that I can’t remember it myself! Especially if I don’t think the data is worth safeguarding in the first place!!!

posted by ted on Wednesday, Jan 16, 2008

Spool on Sign-In Design

Jared Spool writes in a recent article, “Designing an account registration and sign-in process that doesn’t frustrate users turns out to be very difficult to achieve. It looks easy at the outset, but a pile of subtleties can sneak up on your experience, making something that should be simple become stressful for the users.” He’s right; something that should be so easy is so easy to get wrong. Here’s a summary of Spool’s “8 Design Mistakes to Avoid” for account sign-in, along with a few of my own observations:

For more discussion and examples, see the full article . Also see Aaron Cannon’s post on the impact captchas could have on disabled users as part of a sign-in process.

Also see Spool’s follow-up article with 8 more sign-in design mistakes.

posted by ted on Friday, Jan 04, 2008

“I look at that thing and I get a visual dial-tone on my face…”
A customer, describing his reaction to a confusing (third-party) application

posted by ted on Wednesday, Dec 19, 2007

Two great finds today! The first is this video from Victor Tsaran at Yahoo. He gives a very in depth demonstration of how a blind person uses a screen reader, like the kind I wish I could have done during my presentation if I had had more time.

The other find is a study which is nearly five years old, but still gives some great advice which is as relevant as ever. Basically it’s a government sponsored study which tries to answer the question “what helps and what hinders screen reader users?”

posted by cannona on Friday, Dec 07, 2007

Wroblewski: Web Forms in the Wild

UIE recently sent out a two-part article by Luke Wroblewski outlining the Top 15 things to remember when designing an online form. It’s an excellent review of solid design principles:

  1. Don’t hide forms when you want people to complete them.
  2. Be explicit about what each form is for.
  3. Use smart defaults whenever possible.
  4. Don’t treat customers like records in a database.
  5. Always present messages in context.
  6. Make sure key messages are prioritized visually on each form.
  7. Always give people a way to easily recover from errors.
  8. Be vigilant about keeping the data people enter into your forms.
  9. Explain why you are asking for data that may not seem relevant.
  10. When input fields have a high potential for errors, consider providing inline validation.
  11. Visually distinguish errors from the rest of a form.
  12. Remove any unnecessary inputs.
  13. Illuminate a clear path to form completion.
  14. Remove secondary actions whenever possible.
  15. Emphasize calls to action that lead to success (form completion).

For additional explanations and examples from Fairmont Hotels, Boingo, and British Airways, see Part I [covering items 1-8 above] and Part II [covering items 9-15] of the User Interface Engineering article.

posted by ted on Monday, Oct 15, 2007

Great article from the extremely useful site, Smashing Magazine.

10 Usability Nightmares You Should Be Aware Of

posted by rick on Thursday, Sep 27, 2007

“I’m not averse to riches or profit, but not at the expense of the user.”
Jim Buckmaster, Craigslist CEO
via Reaction

posted by sam on Wednesday, Sep 26, 2007

To correct wrong ideas about usability (or anything else, for that matter), you had better not repeat the wrong idea you are trying to correct.

The University of Michigan found that 3 days after reading an article from the CDC aimed at correcting myths about the flu vaccine, participants misremembered 40 per-cent of the myths as facts.

So the best way to correct ideas about, say, user’s willingness to scroll down a page, is to say, “Users are perfectly willing to scroll.” And leave it at that. Don’t handicap your readers by re-stating things that are false.

Via Science Blogs

posted by sam on Friday, Sep 07, 2007

Google Calendar Rocks!

OK, I may be behind the curve here, but I just set up my Google calendar last night—actually my first set of calendars, one for each of the major roles I interact with at Church on Sundays. It was kind of like eating from that proverbial bag of potato chips—I couldn’t have just one!

The background is that I’ve recently been called to serve as an executive secretary serving several local congregations. (This is an unpaid calling, not my full-time job here in Salt Lake.) As such, I’m responsible for scheduling a lot of meetings, not just for myself, but for other very busy people. I thought Google Calendar might be a good way to coordinate.

I haven’t had a chance to “roll out” the calendars to others yet, but even if I just keep it to myself, I think it’s going to save me a ton of time and hassle. My only complaint was that it was not immediately clear how to get started (by signing up for a new Gmail account for each person I wanted to make a calendar for).

Things I like about it:

The most repeated word above is, of course, “Easy”. I’m sure I’m only beginning to discover all the cool ways I can use this tool, but all the coolness is not overwhelming. It’s Easy, and out of the way till I need it.

Just what you’d expect from a Google Calendar, I guess.

posted by ted on Thursday, Aug 09, 2007

Spool: Learning from the Facebook Mini-Feed Disaster

Jared Spool writes about lessons learned from the Facebook Mini-Feed Disaster, caused by the release of a new, innovative feature that kept users abreast of the activities of their Facebook friends. Instead of initially embracing the new feature, users revolted.

Interestingly, the offending feature was itself responsible for helping propagate a protest group against the feature that grew to 750,000 people.

A summary of Spool’s main points:

The full article is a good read on the importance of communicating with customers, understanding context of use, and doing your field work—especially if you are working in social contexts where people are defining their individuality.

posted by ted on Monday, Jul 16, 2007

posted by ted on Monday, Jun 25, 2007

Jakob Nielsen has responded indirectly but thoroughly to many of the exceptions I took to his debunking of the Genius Designer myth. I agree with most of his pros and cons, but he still hasn’t accounted for agile development processes, with frequent releases obviating the need for extensive usability testing, at least under certain conditions.

posted by ted on Monday, Jun 25, 2007

“If the user ain’t happy, ain’t nobody happy.”
Levitation Design

posted by ted on Thursday, Jun 07, 2007

Nielsen: The Myth of the Genius Designer

Jakob Nielsen has recently written to debunk the idea that all you need to do is hire a Genius Designer, and all will be well. Certainly he’s got a point. But the longer I work in an agile development environment, the more caveats I find. (OK—I, a former usability engineer, have officially drunk the Agile Design Kool-Aid.)

Nielsen starts his Alertbox article with, “I often hear the following argument against usability: Just hire a great designer, and you don’t have to worry about that pesky user testing.” He moves on to rebut that argument with some good points. I won’t re-hash all of them here, but some of his statements that need qualification.

“You must run your projects with the team you actually have, not the team you wish you had.” His point is that you may not have the luxury of working with a Design Genius; therefore the designs might have more usability problems. Sure. But “the team you actually have” might not include a dedicated usability person. Doing the best with “the team you actually have” in many cases means doing a solo act. That doesn’t necessarily mean no user research or testing, but it may very well mean another hat for designers to wear, at least some of the time. Since Nielsen has historically been a big proponent of programmers conducting their own usability tests, surely he would agree that designers could also perform this function.

“Design is an inexact science; even if you have a superb designer, not all of his or her ideas will be great.” I guess that’s true. It’s also true that not every usability engineer is created equal, nor are all studies by a given usability professional of equal validity or usefulness. But all in all I guess it’s a valid point; Good Designers can certainly produce Bad Design some of the time.

Nielsen also states that designers need empirical data on their designs to get good at design and that designers produce successful products only if their designs solve the right problems, which would require user research (my paraphrase).

Yes, testing provides some data, and for some kinds of products and development processes, it’s probably the best way to get it. But it’s far from the best data, as anybody who does field research is well aware. Real-world use is not the same as in-lab use. Under the right circumstances, the real world can provide your data instead of lots of pre-release user testing.

Before we begin development, the designers here at the Church meet with the customer, nail down requirements for a reasonably small but meaningful chunk of functionality, show them working prototypes soon thereafter, then build the real thing.

After it’s built, the customer runs through the working software and accepts it or sends it back for refinement. Because many of the products I work on are for internal release to a small number of users, a very high percentage of our user base has already seen the prototypes and given input before it is built. Furthermore, we are able to release new software about every 2 months or so to these internal customers. We start getting feedback on anything we missed pretty quickly, and have the opportunity (at our customer’s discretion) of fixing the problems and releasing the solution in another 8 weeks or less, along with our next batch of new features. You could argue that customer interviews and prototype reviews are really user research after all, but again—it can be the designer wearing that hat, not a full-time usability professional.

“Nobody’s perfect. Even a very good design can be improved when you follow an iterative process of continuous quality improvements.” I agree. But that doesn’t have to mean testing. Our process is highly iterative, meaning we iterate with prototype reviews and frequently released software, constantly delivering value out to our users where it can really be evaluated under conditions that matter.

I realize that it is not always possible to have easy access to such a large portion of your user base, nor to be able to release working software (and fixes) so frequently. Also some applications have high risk to life, limb, property, or reputation; maybe the higher that risk, the more necessary to run more extensive tests before releaseing—even if you will have the opportunity to release improvements again in a few weeks or months.

But when you have a lower risk level, frequent releases to production, and access to most of your users during development—would a robust usability program provide enough value to justify it? I do wish I had the luxury of running more tests, doing some formal contextual inquiry, and so on. But I don’t think it would be a wise use of resources in my case.

And I’m not even a Genius Designer.

posted by ted on Thursday, May 31, 2007

Nice article by Pete Whiting on managing system complexity. Lots of quotables, but my favorite: “You are more likely to be successful tailoring your system to the capabilities of your operators than tailoring the capabilities of your operators to your system.” Amen.

posted by ted on Sunday, May 27, 2007

“I have always wished that my computer would be as easy to use as my telephone. My wish has come true. I no longer know how to use my telephone.”
Bjarne Stroustrup, via Brandon Beecroft

posted by ted on Wednesday, May 09, 2007

“Choose the Right” applied to design

I appreciated Mark Hurst’s recent Good Experience newsletter. The e-mail itself (not the blog entry it pointed to, above) mentioned an experience he had in inviting an Anglican nun to speak at a conference he sponsored.

I took a chance at Gel 2007 and invited a friend of mine, an Anglican nun, to give her take on “good experience.” She turned out to be one of the favorite speakers for a number of attendees. One of her final comments was about “choosing the good,” which I think is relevant no matter what one’s profession, job title, or walk of life. By attempting to “choose the good,” we can design any kind of product – or service – or website – or organization – or life - for the better.

Besides reminding me of my good ol’ CTR (Choose the Right) ring from Sunday School, this injunction to “Choose the Good” reminded me of one of my very first NorthTemple posts: Design and the Golden Rule, wherein I outline my own motivations for entering first into usability, and now design.

Thanks for the reminder Mark.

posted by ted on Tuesday, May 08, 2007

Five Principles to Design By

Principles all designers should live by – great read!
1. Technology Serves Humans.
2. Design is not Art.
3. The Experience Belongs to the User.
4. Great Design is Invisible.
5. Simplicity is the Ultimate Sophistication.

Read complete article

posted by rob on Monday, Mar 19, 2007