Via design.org: The UX Design Success Ladder: Achieving Meaningful Product Design.
Product success envisioned as rungs of a ladder, that you climb up from the bottom: functional, usable, comfortable, delightful, meaningful.
I first heard this concept last year at WordCamp Phoenix in a presentation by Ward Andrews; the article showcase examples of products or services at each level.
Takeaway message: don’t stop at functional and usable. Set the bar higher.
If your software product’s user interface doesn’t support _____, or support them well — your data won’t include _____ in your access logs. You could think they don’t visit often enough to include them in your team’s decisions about the interface. Instead, you can focus on segments of the population based on device, browser, OS, language and location, or any other criteria you feel are important and worthy of attention. It’s simple: make it work for the majority.
This is a blind spot. I call it the bias of the absent visitor. Since they’ve never come by, you can easily fall into assuming they don’t want to or need to use your interface. You might think you can just ignore them safely.
The reality is that they might have stopped by once or many times, had a terrible and unwelcome first experience, and have never come back. They could have seen a blank, white page instead of your carefully crafted design and content. Might have even told their friends not to bother.
This is one of my biggest blind spots. I hope that writing it down will motivate me to remember that the absent visitor is just as valuable as the typical one.
I love web design like this. Both beautiful and useful: footnotes in context so you can read and return without leaving your current place in the text. Two examples—that work in desktop down to mobile—from Upstatement: NPR Code Switch and the newly redesigned Harvard Law Review.
Hat tip: Jack Lenox.
In Benefits of Plain English URLs, the folks at Gadgetopia have added more fuel for the fire of why you should use beautiful URLs. For me, any two of the many reasons should enough to convince the maker or your CMS or weblog software to make nice URLs a default in their setup.
When picking URLs, we envison [sic] someone at the client’s firm reading the URL to someone over the phone. How easy is it going to be?
I especially like this idea of reading someone the URL over the phone and asking them to write it down, remember it, or type as you read. Great URL design and implementation makes this interaction painless and pleasant.