Learn more about my newest book, "Designing the Moment"!

Hack the publishing system

If you plan to buy my new book, Designing the Obvious, please consider buying it today. A small collective effort today could get it back onto the Amazon bestseller list, even if only temporarily, which means that the book will be seen by more people, and the ideas contained within the book will be given a better chance to spread a little further.

The Amazon sales rank for this book rarely drops below 20k, which is fantastic, but the Amazon bestseller list gets seen by a lot more people, so if we can get it back up there even just for CyberMonday, it’ll help the design virus spread.

Help the effort to make the world’s web apps more usable. Buy the book today!

Thanks, and happy Cyber Monday!

Posted by Robert on November 27th, 2006 | Permanent link | No Comments »

How Amazon changed my career

Amazon does this great thing - we’ve all seen it - where they keep track of what you’re buying and make recommendations based on your buying habits.

About a year or so ago, when I was still doing a lot of Flash development work, I logged in to make another purchase and noticed Amazon was recommending a whole lot of books on the same topic, and it wasn’t Flash development. It was interaction design.

I hadn’t really noticed how obsessed I’d become with the subject. After all, I was still a Flash geek by profession. “But you know”, I started thinking, “what I’ve always loved about Flash is that it’s great for developing rich interactions for the web.”

Then I remembered that my entire history in this business had been as a designer, and I only eventually became a developer to learn to build the things I designed. And I remembered that interaction design has been part of every job. User research, product definitions, wireframes for whole interfaces, use cases, task flows - I’d done it all, and gotten quite adept at it, and it was always my passion.

I never meant to become a programmer. I did it to further my design abilities. Eventually, though, it took over and I really wasn’t enjoying it.

Upon seeing Amazon’s recommendations, though, I decided it was time to get a job doing interaction design work exclusively. Amazon showed me what I already knew. I’m supposed to be an interaction designer. It’s what I love doing.

The moral of the story is that seeing what’s right in front of you is not always easy, so if you get to a point where you’re complaining about your job a lot, you might check Amazon to see what it recommends. Could be that whatever you’re buying the most books about is what you should be doing.

Thanks, Amazon.

Posted by Robert on November 24th, 2006 | Permanent link | 2 Comments »

“Designing the Obvious” web presentation tonight

Just a friendly reminder that my “Designing the Obvious” web presentation is tonight. After the jump: details on the start time, how to access the presentation, and the topics.

See you then!

Posted by Robert on November 22nd, 2006 | Permanent link | No Comments »

Down with choice.

What do Jared Spool, Kathy Sierra, Luke Wroblewski, Donald Norman, Marissa Mayer, and Joel Spolsky, and I have in common?

We all agree that too many choices equals a bad user experience. I highly recommend these articles/blog posts on the subject:

Choices = Headaches

The Sweet Spot for Buying

The Sweet Spot on the Curve

The Paradox of Choice

Three of them are from Luke, but they’re aggregates. All of them reference other people talking about the same thing.

Sorry about trashing your plans for the morning.

Posted by Robert on November 22nd, 2006 | Permanent link | No Comments »

When you listen, listen carefully

Yes, I constantly advocate ignoring users. No, I don’t mean you should ignore them forever. I mean that you should avoid letting users guide your design. I mean you should stick to your own vision and focus on supporting an activity instead of an audience.

Once you’ve done that, feel free to start listening to your users. Just don’t act on anything until you’ve listened to a lot of them, filtered out all the really nasty comments, and looked past the ranting to see the little nuggets of truth that exist there.

It’s our job to figure out which comments should actually compel changes in our apps. It’s up to us to decide how to deal with conflicting wishes, conflicting feedback, and so on.

Yesterday, I heard two comments about the same application, in response to the same survey question. The question was, “What do you like the most about the new version?”. One answer went like this:

“Nothing. The old one worked just fine and didn’t look like dog
vomit. Fire the idiot that came up with this piece of junk. Absolutely
unusable.”

The other went like this:

“The new interface plain out rocks. It runs faster, and is much more
intuitive. I really like how you have a tool bar, but always know what
you are working on and those things stick around. It behaves more like
an application that a stateful webpage, which is a huge plus. Thanks
Guys, keep up the good work!”

The only way to decide which person to listen to is to measure these comments against all the others, filter out the rants, and look for the truth behind the comments. Some of them are legitimate complaints, and some are legitimate compliments, but you need to look hard to determine which is really which so you can decide what to do with the information.

On a related note, Kathy is talking keeping our emotions in check while reading some of these comments.

Posted by Robert on November 21st, 2006 | Permanent link | No Comments »