For those not familiar with Google Reader, it is a RSS aggregation tool. Basically, every blog I keep track of (some 120+ blogs) is added to a list that then goes out grabs my RSS feeds from all my various sites and puts them in one nice window to read. There are two viewing modes. One is the ability to view the entire RSS text, or I can view the title of the post in a quick list. I personally found viewing all the text at once a much better way to get the maximum amount of valuable knowledge crammed into my brain.

What Makes Google Reader Great?

I never thought this simple application could be so powerful, but I use it every day and in different ways. The application for me has expanded beyond a simple one-sided user experience.

In any given day I may use it for any of these multiple activities:

• Discovering new blogs and more content in my field
• Locating new and exciting applications
• Keeping up with the latest trends
• Driving adoption of my own blog
• Research
• Keeping track of interesting stories
• An archive..

One of the greatest features I use all the time is archival tagging. I frequently have about 400 posts+ a day to read.  I use the tagging feature to mark research that is relevant to me. For example my tag list contains articles on “CSS Fixes, UX Methods, and my favorite “Web Applications: Category.”  I basically identify new exciting or interesting applications and tag it to the category it belongs.

For Example: Application discoveries are tagged as followed:  Web applications social, web applications shopping, web applications crm, etc.(see image to right).   This is a very valuable tool because I may need to view reference applications for ideas, new patterns, etc.  I simply click the tag and BAM! I get to see all blog posts I have ever tagged with this category. Now that is research power in your hands!

What’s Keeping Google Reader From Excellence:

• A good IPhone application that will synch seamlessly
• Better management to skip through groups of posts. I generally click the “All” button to read through an entire list of my newest posts. If you close your browser, jump into a new window sometimes the application forgets what is “new.” When you have 400+ posts staring back at you this can be overwhelming. I have to click next 40 times to get through what I’ve seen or already categorized. I want a button next to “next” that allows me to choose the number to skip. IE: Skip 20, 40, 60, 100. That way I can get back to truly reading just the newest posts.
• The ability to recognize posts that are titled the same and have the same source will eliminate duplicate entries for reading. This generally happens when you subscribe to a RSS blog aggregation site. There tends to be a lot of overlap with blog posts and a way to filter would be awesome.
• Better ability to connect with fellow bloggers
• Social grouping abilities (I’m not sure what this would be but it may be neat) Consider I spend a lot of time in this tool compared to facebook, myspace, etc…

What Makes An Application Exceptionally Indispensable

In the case of Google Reader it I can sum it up like this:  The application allows me to expand usage beyond it’s original design. It allows me to adapt it to my own work-flows, patterns, thoughts, ideas and creativity. The indispensable application allows me to use it how I want, when I want and, where I want. 

The indispensable application is the  simplest invention that allows for uses beyond it’s intended purpose. The application becomes so ubiquitous that we don’t even think about how it works ,we just know that it does work. You never question the wizard behind the curtain who is pulling the levers. You simply accept its ease of use and hope it never changes. That is the challenge we face when building exceptional UI. The search to find that happy medium is the difference between adoption and failure. It’s a hell of a lot easier to find the failures.

Life In The Fast Lane

I’ll leave you with just one more tidbit of information. If you are a UI designer always ask yourself, no matter what application you are building. Would I use this? It doesn’t matter that the application doesn’t personally apply to you. You can still assess the interactions. Is option A too cumbersome for even you to grasp? Is option B time consuming? Does option C have more steps involved, but causes less confusion? Does option D break accessibility? Does option E completely eliminate future steps?  It’s up to you to decide how to drive the experience. After all the user is just along for the ride and they can easily hop a cab, hitch-hike or walk. You you really don’t want them to do that now do you?

Related articles:

1. Blog Respose: Bowman Leaves Google
2. UI Design Series 1: Web Application Design Where’s The Vision? What’s The Value?
3. UI Design Patterns: Exploration of Data and Visual Imagery in Application Design

The House that Jack Built…Is Crumbling Down

Let’s say you are a contractor building a new home for an unknown family. Looking at your deadline you realize you aren’t going to make it on time. It’s time to do something to solve the problems. What can be cut first?

Perhaps you get cheaper wiring, maybe the concrete on your house didn’t dry before the rest of the foundation had set. Because you are behind schedule you feel the only way for you to “catch up” is to cut corners. Cut one corner and you have opened up Pandora’s Box. It’s so easy to cut more and more. You begin a process of jamming things in just to meet the deadline. One year later the house catches fire and you are sued because you cut those corners.

Elevate Your UI Design To Another Level

The same holds true in UI design and in the UI design process. Frequently you can get rushed to put an unfinished design to the test with real users, even though you are aware of other issues with the design. It may be slow, it isn’t usable, lacks cohesiveness, tries to do too much, is hard to understand, is missing key features of a process. All of these are symptoms of a rushed and hurried design. You can see this in pretty much any application.  Your goal is to minimize this but how?

Give Your UI Time To Mature

This is one of the big concern designers have with an Agile development process. The same can also hold true in a Waterfall management process. The rate of development and design is fast and it’s extremely tricky for the UI designers to stay ahead of the development cycle. What’s even scarier is if the business fails to understand the importance of re-factoring and retesting a design. Rarely, is a UI design perfect the first time. It should and must be tested preferably by the people, person, that are going to be using the application. The problem is getting those that have direct interest in the application to buy-in( I’ll cover more about this later).

Dress your UI Design For Success or Send it Back to the Orphanage

It’s important to somehow let the client know that the first impression of an application is the most important. This is your adoption point (your such a cute design yes you are). If your customers don’t like the product at this point you have to work three times as hard just to gain them back!

Please Come Back I’ll Do Better Next Time I Swear!

Think about the last time you purchased a product and were dissatisfied with the outcome. You probably returned the software, car, clothing, food, etc.. and refused to ever purchase that product again. You probably even refused to purchase a different product made by the same company. This is especially important to your web application and UI design. Yes, features are important, but if my car has 3 steering wheels, 5 extra tires attached, and everything is labeled in Japanese are you going to think it’s usable?

Act Like The Customer Think Like the User

A customer tries to answer two quick questions about your software before purchasing, or using it.

1. Does it do what I need it to do?
2. Can it do it easily?

These are simple core concepts, yet look how many UI designs struggle with this. Look how many Interaction Designers wrestle with these ideas. Think back to the last piece of software, or product you have used. Do you have it in your head? Now think back to the reason you purchased it.

For myself the last item purchased was a tennis racket. These were the thoughts going through my head.

1. Can it hit a tennis ball? – Question Answered – [FEATURE]
2. Is it lightweight, balanced, and does it feel right to use? – [USABILITY]

If I was able to answer the above questions and after repeated use (learn-ability, memorability) could continue to perform and even excel then the design was in essence “great for me.” Why did I put this in quotes? Well as UI designers we have to find that common ground to support the vast majority of users. Are you really really going to find a UI Design that supports 99.9% of your users. You may find a a design that meets all the goals of your (persona’s -fake users), but even that is a rarity.

So What Makes a Design Great?

It’s the combination of a great feature set that has a high level of usability and has an aesthetically pleasing design. It’s about a design that delivers direct answers to the questions.

Does it do what I need it to do?
Can I get it done easily?

So the next time someone says just jam that feature in to the design. Feel free to send them to this post so they can see what really happens and how many aspects of the software you effect because of quickly rushing a design. Your adoption point or the first release of your application is your first impression. Fail at making a good one and what was the point of even producing the software?

Related articles:

1. User Experience Design in an Agile Development Cycle
2. UI Design Series 1: Web Application Design Where’s The Vision? What’s The Value?
3. UI Design Lessons: Are You Driving Your Application Usability Off A Cliff?