My latest Designing the Obvious Clinic article is up over on InformIT.com, and this time, it’s about a whole technology: RSS.

The purpose of the series is to measure a few web applications against the principles I talk about in the book. In this case, I took a look at the problems with RSS, why it has eluded mainstream success, and what can be done to improve the subscription process.

Check it out!

Do the Right Thing officially launched today.

If you haven’t seen it yet, the site is aimed at keeping companies in check by enabling users to rate the social impact of the company’s actions. If a company does something you find offensive, simply post a story about it so others can rate how important it is to them. If a company does something you find respectable and good, and do the same thing. Either way, find out which companies are doing the right thing so you can be more informed as a consumer.

DTRT is a brilliant idea and a noble cause, and I’m very proud to have been able to work with Rod and the rest of the team to improve the design of the site. They are to be commended for their commitment to influencing companies to uphold the highest moral standing and to do what’s best for the world, and for giving credit where credit is due.

Congratulations to the DTRT team! Keep up the great work!

Josh Viney, via the IxDA discussion list, has a great explanation for what “it” is all about.

“Elegant product design requires an understanding of people, the business
requirements, and of what is actually possible. It amounts to creating
products that are like professional athletes, products that make the
extremely difficult look easy. It ultimately takes a lot of work and some
serious talent.

Many companies and people don’t know how to build elegance. It brings to
mind technology companies that focus too much on their frameworks or
advertising agencies that focus too much on pixel-perfect design. Neither of
which tends to have much empathy with the user.

Anyway, my goal is to build elegant products. The products that don’t make
people think when they should be doing, make people think when they should
be learning, compel them by relating to them, and simply work.”

Regardless of whether you use BBC News, CNN, , Yahoo News, or some other page as your primary news portal, you’re constantly faced with the same type of solution. These pages contain lists of links, sorted by time, relevance, popularity, or some other criteria. And this is a good thing, because it makes information relatively easy to find.

That said, even the most basic and standardized designs can be improved. So recently, when I needed to add such a list of links to a home page for a new application, I decided to take a fresh look at the standards yet again.

I started with the usual suspect. I created a simple list of links.

For this design to really be complete, it needed to communicate to users that the order of the links was determined by the order in which the articles were posted. To do this, I could have included a bit of instructive text that said something like, “Sorted from newest to oldest”. Or I could simply have numbered them from one to five and called it a day. I could also have stuck a small “New!” icon next to the topmost link to imply the order. But having recently read the Boxes and Arrows article, “The design behind the design”, by Ross Howard, I felt inspired to try something a little different.

See, it’s always bothered me that the web has no sense of age. An article I wrote two years ago, for example, can very easily come up as a top search result today. Hence, I get email occasionally from people who have questions about something I haven’t thought about in two years. Their question is fresh. My answer, however, might be a little rusty. But if the web showed signs of age, the user reading the two-year-old article would clearly see that the article was old, and might therefore seek more updated information elsewhere, or at the very least, adjust his question while writing to me. (There are many other reasons that indicating age could be helpful to web users, but I’ll save that for a different post.)

So to communicate the meaning of the sort order in this case, I decided to try to communicate the age of each link. I started by changing the font size for each link based on its popularity. The link for the most recent article used the largest font, and the font size decreased with each link as the articles aged.

This alone changed things quite a bit. The larger font not only stood out more in terms of size, but also in richness of color. The larger font appeared darker and heavier, which made it stand out even more. Hmm.

This reminded me of something I saw in Google Reader. Jeffrey Veen recently wrote about some design work he’s done for Reader, and upon checking it out, I noticed a tag cloud unlike the others I’ve seen around town. This one used color changes as well as font size changes. It looked like this.

It included instructive text that said, “The more items a tag has, the bigger it appears. The more of those items you have read, the darker it is.”

I thought this was a bit convoluted for instructive text, but I also thought the dual-purpose tag cloud was a great idea. So I rolled with it.

Modifying my link list, I changed the color of each link to from from dark to light as the list descended from newest to oldest.

Yes, this meant the developers would have to write some more code, but in this case, they liked the format of the list so much that they didn’t care. (In other words, I got lucky.)

Is this use of ambient signifiers going to make a big difference on the resulting web page? Probably not. Will some people be annoyed by the tiny font used for the last link in the list? Possibly, but I can always adjust how much the font size decreases so this doesn’t happen. Am I saying you should immediately run out and do this on your own page? No.

The point is that ambient signifiers are a great idea, and almost completely untapped on the web. So take a look around and see what you can come up with. How can you use ambient signifiers to make a page more understandable or a task flow more intuitive?

Want to see another idea? Consider the recent Boxes and Arrows redesign that brought a tag cloud to the forefront of their persistent navigation.

Have fun!

Update from Etre: “Dao Gottwald ’s “Aging Tabs” Firefox add-on makes unused tabs fade with age - thereby making it easier to identify those pertaining to the current task.” 

Part of believing that people adapt to technology is realizing that we also need to understand how people adapt to technology. So when something new comes up, or when we come up with something new ourselves, there’s a lot of value in running usability tests to determine how easily people will adapt to it, if they will adapt at all. There’s value in finding out if it’s desirable. And there’s also value in the things you can learn from usability tests that you never intended to learn, like the fact that they keep ignoring the giant Help button.

But some companies test almost religiously. Once they decide to start caring about user experiences, they start running usability tests constantly because they think it’s the only way to learn anything and be sure about it.

What they typically find out, however, are the exact things a good designer could have told them without pestering eight of the company’s most valued customers. A good designer should be able to tell you most of what’s wrong with an application once its built as well as how to fix it, and should be able to design something that prevents most of the issues in the first place.

Instead of spinning your wheels researching things your designer should already know, save your strength for the strange things. The things no one else has done before. Test those.

Spend the rest of your time finding a good designer and keeping him happy.