The desktop, literally


“Layered Desktop,” by Gabriel Radic.

The desktop has been the primary GUI metaphor of operating systems for the last thirty years. Over that time, newer operating systems have stretched the desktop metaphor pretty thin, in the interests of better usability and faster task completion.

For example, remember when Apple’s System 7 would open each folder in a new Finder window, creating a cascade of windows that quickly became unmanageable? That was a literal interpretation of folders on your actual desktop. Fortunately, we now browse the contents of multiple folders within a single Finder window, an activity that doesn’t transfer to the stack of folders sitting next to me.

I found the wallpaper above really interesting: someone created a solution for organizing desktop icons which makes your computer screen look more like a desk, even though the design trend has been to move away from such literal interpretations. It’s not right or wrong—lots of people find it useful, judging by the comments—it’s a creative solution to a desktop organization problem.

A brief overview of website optimization

Courtesy of the Google Analytics blog, an introduction to website optimization and how (and when) you should use it on your site.

In summary, here’s how to optimize a poorly performing page on your website:

  1. Find your high value landing pages
    What pages on your site have high entrances and high bounce rates? These are the “high value” pages that are begging to be optimized.
  2. What’s the desired goal (or conversion) for the site?
    In other words, what is the ideal outcome of a visit to your site? Some common online conversions include account signup, new lead generation, joining a mailing list, or purchasing a product.
  3. Set up a goal in Google Analytics to track how well your landing page is funneling people toward your desired conversion
  4. Create a new design for the landing page you want to test
  5. Test it!
    We were told at the LunaMetrics training session that you can expect actionable results within about a month, depending on the traffic to the page being tested. You could see statistically significant results in as little as two weeks in some circumstances.

Talk to Caleb or me if you want to know more about website optimization or if you have questions about the jargon. We’ve been scouting a few pages on our sites in need of optimization and could always use more practice.

Finally, the Website Optimizer team has a blog that’s worth a look. I recommend starting with this case study, in which conventional wisdom about the use of imagery on the homepage is tested.

Everyone’s an information architect on the new Facebook?

I’m very curious.

My off-the-cuff prediction is that casual Facebook users will see this as just one more piece of clutter and heavy Facebook users will embrace the flexibility. But just because it makes things messier or less consistent visually doesn’t necessarily mean its a bad design idea. It seems like a clever way to allow users to experience the page layout freedom they had on MySpace, but within the constraints of a rigid Facebook UI. Whether that’s what Facebook users want remains to be seen—Facebook has had more than its share of problems pushing unwanted features out to its user base.

How to be a UX team of one (and other presentations from the 2008 IA Summit)

This year’s IA Summit just wrapped up in Miami and as usual there are several sets of slides that made me wish I had gone. Not surprisingly, I was drawn to Leah Buley’s presentation “How to be a UX team of one.”

SlideShare

A bunch of others look really interesting too, and relevant to others outside of the IA/UX practice:

The Page Paradigm, a.k.a. “users don’t care where they are in the website”

This is a classic blog post I rediscovered today. Totally worth reading, even if you’ve seen it before and even if you’re not an information architect.

Users don’t much care “where they are” in the website. So-called “breadcrumb links,” which show the user the exact hierarchy of the website as they click further down, are a nice but mostly irrelevant technology. It’s not that users don’t understand the links; it’s that they don’t care.

Let me say it again, Max Bialystock-style:

USERS DON’T CARE WHERE THEY ARE IN THE WEBSITE.

I emphasize this because Web developers often waste time worring about “where content should live.” Should it be in section B? If so, we need to put big links from Section A to Section B. And then the secondary navigation will list Sections A through C, which are part of category D, because users might need to see the relationship between C, B, and the sub-tertiary wormhole that just opened in the site map!

Meanhwile, the user is on the site thinking, “Do they have it in size three?” and ignoring every element on the page that doesn’t appear to take them toward that goal. All the site-organization links, so carefully consistent with their display in other areas of the site… totally ignored by the user.

The 2008 Bad Usability calendar is here!

badusability calendar: january
badusability.com

Account sign-in mistakes to avoid

From Jared Spool’s excellent webiste, User Interface Engineering. Check out the links for detailed descriptions of each mistake:

Account Sign-in: 8 Design Mistakes to Avoid

  1. Having a Sign-in In The First Place
  2. Requiring Sign-in Too Soon
  3. Not Stating the Benefits to Registering
  4. Hiding the Sign-In Button
  5. Not Making “Create New Account” or “Forgot Your Password” a Button or Link
  6. Not Providing Sign-in Opportunities at Key Locations
  7. Asking for Too Much Information When Registering
  8. Not Telling Users How You’ll Use Their Information

8 More Design Mistakes with Account Sign-in

  1. Not Telling Users the Requirements for Username and Password Up Front
  2. Requiring Stricter Password Requirements Than The NSA
  3. Using Challenge Questions They Won’t Remember In A Year
  4. Not Returning Users to Their Desired Objective
  5. Not Explaining If It’s The Username or Password They Got Wrong
  6. Not Putting A Register Link When The Sign-In Is An Error
  7. Not Giving the User A Non-email Solution To Recover Their Password
  8. Requiring More Than One Element When Recovering Password

Pagination examples and good practices

A supplement to a conversation that has come up a couple of times: Pagination Gallery: Examples and Good Practices

The author lists seven keys to good pagination:

  1. Provide large clickable areas
  2. Don’t use underlines
  3. Identify the current page
  4. Space out page links
  5. Provide Previous and Next links
  6. Use First and Last links (where applicable)
  7. Put First and Last links on the outside

There are tons of screenshots of both good and bad pagination, which makes this a great reference.

ice rocket pagination

Getting people to contribute

By now, you’ve probably read about Knol, Google’s attempt to create a database of high quality user-generated content similar to Wikipedia. Community and collaborative systems fail if users see no incentive to contribute, which is why Knol is so interesting. Google obviously thought hard about this and came up with two key incentives to people to contribute that Wikipedia does not offer:

  • Google will clearly highlight the author of the article
  • Google shares ad revenues with the author of a knol

Check out the screenshot of a knol entry on insomnia. Incentives for use are one of the most important things to consider when building a collaborative application. It will be interesting to see whether Google hit the sweet spot.