2258 Blog: Observations on Design + Usability » 2008 » March

Archive for March, 2008

GRD Podcast with The Thirsty Developer - Designers and Developers

Monday, March 24th, 2008

I work in our Minneapolis Office, but I was in Milwaukee a couple weeks ago, and had the pleasure of speaking with Larry Clarkin of The Thirsty Developer, a podcast for developers. Larry and his colleague Dave Bost host the podcast and find various topics of interest to developers.

Larry heard about Gomoll Research + Design by word-of-mouth, and decided to call on us to discuss how developers can improve their design of products, whether through tips on doing certain things themselves, or through collaborating better with designers. The podcast is about 15 minutes long, and is geared towards designers or developers who work on improving the user experience. I hope you’ll have a listen, feel free to comment here or at the Thirsty Developer site as well.
Podcast: Dev-igners and Des-elopers

Observe, don’t just listen to, your users

Thursday, March 20th, 2008

I worked at a company that was a national company, but had grown as a collection of regional offices. The regions occasionally built their own software applications to suit their needs. Over time, people noticed that some applications were redundant as they had been built in multiple regions. Or in other cases, one region was out shopping for a product not knowing that another region had developed a product to meet the same need.

The corporate IT group was asked to ‘take over’ a regional application that could fill gaps in other regions as well. Our job was to make sure it was secure and put in our data center, i.e. all the technical stuff, and also to make it easier to use.

To that end, I went to the region and met with the manager of a group of users of the application. She didn’t quite understand why I wanted to go on a client visit with her employees and watch them use the software. She proceeded to give me a demonstration of the software. I sat through the demo, thanked her, but stated “we never know what we’ll find when we watch people use applications in their natural environments.”

Sure enough, within the first hour, I had my moment that I could take back to the manager. Users were working in the application, then going into MS Word, cutting and pasting from MS Word back into the application. This went on for 20 minutes when I asked them to think out loud and tell me in a little more detail what they were doing.

“Well,” the user said, “I share these reports that get printed out with our customers. And I’m a REALLY bad speller.”

Turns out the application didn’t have a spell-check function in it, so the users would use MS Word to spell-check and then cut pieces out and put into the various fields in the application.

2325

Whitespace and Portals

Thursday, March 20th, 2008

Recently, while designing a portal for a client, I was part of a debate about whitespace versus information density in portal page designs.

I began my career designing instructional materials for Apple, where whitespace was an essential tool we used to create a clean, simple, accessible look. Since that experience, whitespace has been part of my DNA — I don’t surrender it lightly. I know that it is underused, that it is essential to helping users parse and scan content, and that it is at the core of any visual design that strives to be light, simple, and clean. I also appreciate the prominent role it plays in branding for a wide range of corporations. That said, we have learned that in portals, it can be overdone.

In a portal (as opposed to a public site or print materials), users come to the site with efficient information retrieval as their primary task. They do not want to browse or navigate or think about site structure. They want 80% (or more) of the information to be right there, on the surface, no clicking required. Portal user satisfaction is often driven directly by the ability to retrieve target information on the portal homepage. So while the layout needs to be open and clean enough to be scanned, there are higher user tolerances (even requirements) for greater information density on a portal page.

Furthermore, portal users will, within seconds of landing on a portal page — without clicking or scrolling at all — evaluate it based on how much useful information they see at a glance. If they perceive that they are on a page that is lightweight, overly branding or marketing-driven, or lacking sufficient useful information, it will impact the likelihood that they will become frequent users of the site.

Users have also developed expectations about portal designs. Based on their personal experiences with news portals, customizable portals (e.g., iGoogle, My Yahoo!), they have come to expect a certain information density. They may be critical of or question the relative value of sites that use lighter designs based on their learned expectations with other portals.

Having said that, talented visual designers can keep a light feeling in a design, minimize rigid portlet-segmentation, and vary the weight of different portlets to break up the “gray-blur” effect one might experience looking at info-packed portal screens. But it is useful to be aware of the fact that information density is a good thing for portals. And we don’t want to use a visual design that will reduce the perceived value or usefulness of such a site.

The GRD Blog

Thursday, March 13th, 2008

If you look on the home page of our website, you’ll see our description:

“We excel in designing elegant product experiences. We’re experts in user-centered design. We can help you conduct field research, understand workflow, develop user models, build prototypes, conduct usability studies, and design humanistic and usable products.”

With that in mind, our blog posts at GRD will be about our shared experiences in our chosen field, user-centered design. Best practices, lessons learned, or thoughts on current design trends are all fair game. We’ll comment on other articles and contribute to the design conversation going on ‘in the field’, and we invite you to join the conversation as well. You can check the site for posts occasionally, or subscribe to our RSS feed.

0