Frequency: Tell me how often you do it and I’ll reveal your expertise level

Designing for a touch screen kiosk ≠ designing for a touch screen phone/tablet

Hey! This isn’t that kind of blog.

Last week, we discussed location issues in touch screen kiosk design. This week we’ll talk about how frequency of use impacts the user’s needs.

1.    Location
2.    Frequency
3.    Adaptation
4.    Applications
5.    Hardware

Expert Users

Do you use your mobile phone every day? I know I do and not just for phone calls. I keep all my appointments in it and important lists. I know all my phone’s quirks and the work arounds necessary to get it to do what I want. Through daily usage I have become an expert user of my mobile phone.

Don’t you hate the learning curve when you buy a new phone? It’s awkward at first and mentally remapping the new phone’s work arounds over the old ones takes awhile. After about a week though, you’re an expert user of your new mobile phone.

This expert user is willing to take the painful learning curve for the perceived rewards the new phone/tablet brings. Apple’s innovative approach to the iPhone and iPad depends on this type of user. Even though the buttons are too small and the interface breaks all previous mental models people line up days just to be the first to have the latest version.

Casual Users

Even business travelers that fly every week using a check-in kiosk can only ever be considered casual users. Two minutes of usage twice a week does not add up to expertise. For these users, they’re forever at the beginning of a new phone learning curve. Yeah, they’ve used a kiosk before but each time they’re guessing what to do based on previous experience with other kiosks.

Many kiosk users only approach a kiosk one time, if ever. Think about airport info directories, office building directories, etc… You have to assume that every time a user approaches a kiosk there’s a very high probability that this user has never used it before.

As a designer, you can help by sticking to well-established design patterns. This helps reinforce the user’s mental model of how the kiosk should work for them. This is no time to reinvent the wheel much (and, if you must, at least don’t make it square!).

“Do you want fries with that?”

Previously we discussed “One Unambiguous Interaction Per Screen” for the user. This is my golden rule for the touch screen kiosk interface design. The exception is the expert user of touch screen kiosk. You’ve seen them but you don’t think of them as a kiosk interfaces. Many retail stores have employee touch screen interfaces these days and many of the kiosk interface rules do still apply.

Customers as end users cannot be trained. But employees are trained to user these interfaces and they use them 8 hours a day.

One interaction rule would slow them down due to numerous server calls and waiting for the next screen to load. This would give them plenty of down time to plot my grisly death, so let’s not go there!

The employee user wants to complete as much of the transaction on each screen as possible. They need contextual fields grouped together plus an intuitive navigation through the interface that minimizes movements that could lead to repetitive stress injuries.

As you can see frequency of usage plays a big role in deciding which approach you need to take with the end user. Being very clear on which user persona you’re dealing with can make the difference between success and failure on a touch screen interface project.

Next time we’ll discuss how well the mobile software and the kiosk software adapt to the user.

Posted in Best Practices, Touch screens, UI Design, Usability | Tagged , , , , , | 1 Comment

Location, Location, Location: Where is your touch screen?

Designing for a touch screen kiosk ≠ designing for a touch screen phone/tablet

Just because a kiosk has a touchscreen, do not mistake it for an over-sized smart phone or tablet. The user experience and usability issues are vastly different. This is the first in a series of articles discussing the user persona differences you need to keep in mind when designing for a kiosk interface versus a mobile interface.

1.    Location
2.    Frequency
3.    Adaptation
4.    Applications
5.    Hardware

Public Spaces

Kiosks live in public spaces. Period. You’ll never find one in your house, your car, your office cubicle or a bathroom stall (You know who you are and let me just say, “Gross!”).

Public spaces like malls, airports, hotels, trade shows, and so on are all noisy, chaotic places that induce stress in the end-user. Nothing says stress like checking in with kiosk at the airport while simultaneously keeping one eye on your luggage and plugging one ear against the crying baby of the traveler next to you.

Given all the challenges, why do people use kiosks? Necessity. They’re not playing “Angry Birds.” They need to perform a task and the kiosk is there to help them with that task.

One Unambiguous Interaction Per Screen

Loading up the screen in the hopes that fewer screens will make the process seem faster will backfire every time. In this environment, showing the user a screen crammed full of text and buttons will stop them like a deer caught in headlights every time. Let’s not add to their stress. One simple decision or process per screen allows the user to focus and answer appropriately then move on to the next screen. The user feels confident in the process and their progress.

Sorry, I can’t help you about the crying baby.

Sound Effects—Just Say No

It has been suggested to me more than once that sound feedback from a kiosk would be a great idea for accessibility issues. Hey, it works on slot machines what could be bad about that? Exactly! Keep in mind the location of the kiosk when making this decision. The lobby of a quiet office building might be able to pull off sound effects but remember the Las Vegas airport has banks of kiosks and slot machines. We wouldn’t want the user to get confused and try to upgrade a seat from a slot machine now would we?

Just keep in mind that the user must go to the kiosk location to conduct their task. The environment is a huge factor in their success or failure in completing this task. The least we can do as UX designers is make sure the interface doesn’t exacerbate the location problem.

Next time we’ll talking about how the frequency of use impacts the user. Meanwhile, please don’t call or text me while you’re in the bathroom stall!

Posted in Accessibility, Best Practices, Touch screens, UI Design, Usability | Tagged , , , , , | 1 Comment

All I really need to know about UX I learned from my mom

In these confusing days of user experience design, it’s easy to get lost in a sea of constantly shifting vocabulary. Every company and designer with whom I speak has a different definition for taxonomy, information architecture, usability testing, iterative design, etc…

Something’s getting lost. Oh yeah! It’s the user.

My approach has always been simple and direct. User interface design should be fast, efficient and pleasant. When the average person interacts with a web application that’s all they’re looking for…and they’re shocked when they actually get it. I learned that from my mom.

Only the design industry and teenage boys want cool, incomprehensible graphics. And then, only the design industry sighs over perfectly beveled CSS3 corners. When did we become such an elitist crowd spouting off the most rarefied prose? Why have we started designing for ourselves and not the end-users?

I read an article many years ago. (I’ll link to it if I find it.) The basic premise was that websites are either masterpieces or forks. Masterpieces are beautiful but non-functional. Forks are utilitarian. My goal is to create the most beautiful fork I can. I know it sounds odd coming from someone with a fine art degree, but hey, I have a whole other website filled my art work. When it comes to design, I give myself over to the end-users’ needs.

“If you can help, you should.” — my mom

My mother is a perfect example of true customer service. In her job as an accounts receivable clerk, she bends over backwards trying to help customers with their accounts. Then she takes copious notes so that the next clerk helping that customer will know exactly what happened and the steps she’s taken to resolve it. Even though her hard work is rarely acknowledged, she takes pride in do her job well because that’s how she’d want to be treated as a customer.

Whenever I’m working out a UI design, the end-user is foremost in my mind. First, “How can I make the functionality of this screen as fast, efficient and pleasant for them as possible?” I also take pride in my work. I worry about taxonomy, information architecture and so on, so they don’t have to.

I always keep in mind that it’s not about me. It’s about them (the end-user). I learned that from my mom too.

P.S. Happy Mother’s Day Mom (from your favorite)

Posted in UI Design, Usability | 3 Comments

8 Must-Have Features for A Killer Social Media Aggregator

I don’t know how some people and small companies do it. I only participate in 3-4 social media sites and I can’t keep them all up-to-date simultaneously—at least, not if I want to keep my job and occasionally sleep!

I recently went on a tiny rant about companies abandoning their websites to focus on building their social media pages. I’m not really a social media hater so I wanted to see if anyone was working on a solution. I knew that some sites had two-way connections. For example, I can have tweets automatically post to my LinkedIn status and vice versa. I think we need a much bigger solution, like a one-to-many connection.

I did some sleuthing around the internet and it seems that several development companies are working on a content management solution (CMS) for social media. The idea is that you can input your dynamic content (blogs, news/announcements, events, etc…) and the CMS will post the items not only to your website but also to your social media pages as well.

Awesome! A solution that maintains the website AND the social media presence. Type it once and let the application spin it out where you want it to go. Think about the possibilities! Search engines will once again love your website because the content is fresh. New customers will find your website because of all the search engine love you’re now getting. Old customers will once again come to your website because there’s something new to see on a regular basis.

Yeah, awesome…if they get it right.

Based on my experience with WordPress, I’m sure any solution will handle the basics:  adding images and multimedia, allow users to add, modify and delete content and allow the user to select an alternate language. It’s going to take much more than that to be the next big CMS killer app.

Here’s my list of must-have features for any social media input aggregation.

  1. Allow the user to input publish and removal dates for each post. This will allow the user to set up content to be released on a specific date or even maintain a continuous flow new content without scheduling writing time everyday.
  2. Figure a way for the interface to allow for the automated removal of out-dated content (like past events) from the social media pages.
  3. Allow for multiple authorization levels. Authorization should be configurable by type of post and editing permissions of each user.
  4. Provide a method for the user to select a subset of the social media sites for each post to get published. Not everything is tweet-able nor does every tweet belong on your LinkedIn status. (You know who you are.)
  5. Create short URLs without leaving the interface. A bit.ly widget or something like it within the interface would do the job nicely.
  6. Provide a smart solution for posts to meet the maximum character limits for each type of social media site. Yeah I’m still talking about you Twitter!
  7. Support translated posts in multiple language for internationalized websites.
  8. Sync resumes. (I soooo need this feature.) It might be easier to sync from a site like LinkedIn to a website, but I leave that decision in the hands of a capable developer.

Okay this last one’s a not a wishlist item but please come up with a better acronym than I did! CMS-SM, ugh.

Hey, I’m a user experience designer not a developer. From my perspective, this is what it will take for a CMS application to be the next big deal. Can anyone add to my list? What do you think is a must-have feature?

Author’s note: I’m not affiliated with any of the development companies working on a CMS for social media application so I can’t discuss or recommend any of their products.

Posted in Internationalization, Social Media, UI Design | Tagged , , , , , , , , | 2 Comments

Bonus Tip for Creating a Color Palette for Color Blindness

I meant to start this article with tips on touch screen interfaces for color-blindness accessibility but my bonus tip ran on too long. So today it’s dessert first! I’ll get back to the touch screen entreés on the next article.

I’ve wanted to design a website for a color-blind client for a long time. Weird right? I think up odd challenges for myself all the time—occupational hazard I guess. The goal is to create a site that the client can see the site exactly the same as a non-color-blind person. I had an epiphany on how to succeed last year and I’ve been dying to try it.

When I worked with Ernst & Young many years ago, we printed our Powerpoint proposals on a Docutech color printer. I’ll wait while you quit shuddering…

Better now? Good.

After much frustration with the final output I finally decided to print the Powerpoint RGB color wheel on the Docutech and use it as my guide in picking colors. On screen the document looked like cotton candy but in print, fabulous! It was so successful, when my coworkers found out how I was doing it, they asked me to print out the dreaded color wheel for them too.

Why not use the same process as a guide to the color-blind challenge. With all the web tools available to test a site for color-blind accessibility, it’s possible to reverse engineer a color palette at the beginning of the design process. Take a color wheel image and run it through one of the accessibility site tools and now you have a viable color palette for your client.

Let me guess. You’re thinking the colors will be ugly. Well I just don’t believe that. There are no ugly colors, only people calling themselves designers that know nothing about color theory. True the site won’t be fully saturated but there are many beautiful sites with limited color palettes.

So why bother? Call me a perfectionist but I want 100% stakeholder buy-in. How can my client be 100% sold on my design when he can’t see it the way I do? Maybe they don’t know that with a conscientious designer, they can have a design that appeals to the masses that they can also fully appreciate.

I think this is a faster horses moment. If a client isn’t aware of what’s possible he doesn’t know to ask. I can never be satisfied with giving my client a faster horse when I know he needs me to invent a car.

Maybe he doesn’t want to draw attention to the fact that he’s color-blind. Trust me. No one will ever guess from the website and my lips are sealed.

Posted in Accessibility, Client Communication, UI Design | Tagged , , | 1 Comment

Form Versus Function: Can’t They Just Make Up!

My touch screen interface work for the past four years has been about e-commerce and function over form. As a formally-trained fine artist, the form versus function argument rankles a bit. I chafe at giving up one over the other. Why can’t you have form and function!

A few weeks ago I had a different kind of touch screen experience. Form definitely ruled here. I took my niece to the Kimball Art Museum in Fort Worth to see the Fiery Pool: The Maya and the Mythic Sea exhibit. They had a large touch screen laying flat with an oval border over the top creating the appearance of a pool. There was room for eight or more people to interact with the pool simultaneously. Talk about multi-touch!

The screen displayed a rippling pool with animal silhouettes swimming through the water. Touching one of the silhouettes caused an interface to open up and float on the surface of the water. The interface displayed images of all the exhibit pieces that referenced that animal and text about the symbolism of the animal in Mayan culture.

I could critique the hardware and software but I’m not going to do that here. I want to focus on my user experience. Museums can be stodgy places where you can’t touch anything (as I was reminded by one of the guards). To find this unadvertised gem near the end of the exhibit made my day. I felt like a kid delighted in exploring something new.

The experience was communal and engrossing. I struck up conversations with the other patrons. We shared tips on how to interact with the interface. I spent almost as much time at the pool as I did viewing the whole exhibit. A large dose of patience was required while waiting for all of the animal shapes to swim within range.

Function will still rule over most business touch screens but the exhibit was a powerful reminder of what form can do beautifully and subtly. This pool brought a group of strangers together to learn in an interactive and entertaining way. There was no neon sign that said, “Learning – this way.” Just a table glowing seductively in a darkened room that whispered, “You can touch me and no alarms will go off. Play as long as you want.”

The whole experience has motivated me to advocate even more for form in functional e-commerce applications. (Some would say I’m already over the top as an advocate. Like that’s possible!) There must be a place in society for beauty and delight in new finds. If not then the iPad and iPhone would just be also rans in their niches and eight mature adults wouldn’t have huddled around a touch screen to poke at animal silhouettes just to see what would happen.

FYI—The exhibit closes January 02, 2011 at which point the below link probably won’t work anymore.
www.kimbellart.org/maya

Posted in Touch screens, UI Design | Tagged , | 3 Comments