Archive for July, 2009

Giving users what they want… or what they need

My preschool son loves all the Herbie movies. He gets excited anytime he sees a VW Beetle and yells “Herbie!” and then proceeds to tell us all about him: “Herbie is a racecar.” “Herbie’s wheels and lights.”  You get the idea. We’ve been toying with the idea of getting him a Herbie of his own and finally decided to do it after a string of really good accomplishments (sleeping better, being good in preschool, potty training, etc.).

Two nights ago, we were walking downtown and saw a red, vintage Beetle. My son gets so excited that we run across the street to say “hello.” He proceeds to tell us to get the keys and get in the car. He wanted to drive. He wanted this Herbie. Little did he know his own version of Herbie was coming in the mail the next day.

Herbie - "first release"However, his version of Herbie is not a full size car. It’s a small ride on. It’s not exactly the right style (more like a modern VW). It’s not even the right color. Also, it has a parental override…. a remote control so we can make sure he’s safe. This is not what he asked for…. but its what he needed.

He still loves it. It’s the right size for him. He can reach the pedals. He can steer. It has a funny horn sound and blinking lights. He is disappointed in the color. So, for the “next release” we will update his new toy with a white paint job and Herbie decals – already arrived from Ebay. However, overall, he is thrilled with it.

Now, I’m not saying that all users are like preschoolers. However, as usability professionals, we know our users will sometimes ask for more than they could want or need. Some features, no matter how cool they sound, are just not the right thing to include. Some features would actually hinder the user’s interaction with the software. For example, would it make sense to give my little boy a full sized VW? No way! Its much too powerful and big for him. His new little bug is just right!

Leave a Comment

My 2nd Axure Experience

After my first experience with Axure, I was very excited to try a real world scenario…. something other than the set demo that worked so well. So, I pulled out a wire frame I put together as a quick mock up (PowerPoint, my favorite mock up tool) and started recreating it.

At first impression, I thought it was pretty quick. Putting the page together was easy. Most things work as expected. After the demo walkthrough, I felt like I had a pretty good handle on some basic actions. I immediately jumped into making my master items. I have always loved using masters, which is one reason why PowerPoint has worked so well for me in the past. It was a bit odd that the sitemap node on the page tree was called “Home” rather than “Sitemap.” However, it is the “Home” of the prototype, so I let that slide. Besides, once you figure out that it doesn’t behave like a normal page, its easy to see its true functionality.

Then, I ran into a few annoying features…

Choosing colors: The color picker is a little clunky.  I wanted to use a custom color from a websafe chart, but when I toggled between my chart and Axure, the color picker is lost.  Ok, so you can find it again via Alt-Tab, but why isn’t it forced to stay up. I wouldn’t be quite so picky if this were an open source project, but I expect a $600 application to be a little more polished. This isn’t a HUGE issue, but it does get frustrating when you’re going back and forth between windows.

Second level bullets: It’s very easy to drag and drop widgets onto the page and configure them. Most formatting tools work as expected. However, I tried for about 10 minutes to create a second level of tabs within my text widget. Yes, I could’ve created a second text field and just moved it over, but I preferred to keep it as one big text field. I even went into the help system for the first time. When I clicked on the “Bullets -> Add” topic, I was told how to add a widget to the page, nothing to do with bullets. So, I gave up and just used dashes and spaces. Not an awful work around, but still frustrating.

Embedded links: So, how often do we as designers have a link in the middle of a sentence? All the time! This is my largest issue with the application so far. It is the type of thing that will make me groan every time I need to do it, until I figure out a better work-around. You cannot select text from a text widget and make it a link. You can make the entire text widget a link, but this is not useful for usability testing or for explaining the design to your team. Plus, if you have more than one link you are stuck. You can break the text into little bits, but then you have to constantly align things and deal with all the little widgets. I opted for creating links with the exact text and size of my links and overlaying them. I wasn’t completely happy with my workaround, but it wasn’t too bad. And, once you line it up and group it, everything stays in place unless you resize anything or change the text… Then its a matter of ungrouping, realigning and grouping again. As a workaround, its not awful. And, given the potential of the application, I was happy to let it slide… until I generated the prototype.

Within Axure:
linklabels_inapp
Prototype:
linklabels

Energizer bunnyThis does not mean I’ve given up on the product. All products have their flaws. I’m going to keep going and see what happens.

Comments (5)

Persuasive Personal Informatics

Today, I saw an interesting Tweet by IATV. He seems to post some really good links, and I think he may become one of my favorites to follow.

This afternoon, he posted a link to a presentation on Persuasive Personal Informatics. The presenter, Matt Jones, is one of the designers at Dopplr. I wish I had the pleasure to see his presentation in person and chat with him about it. The presenter had a great sense of humor and shared a lot of interesting stories and designs. Its only 35 minutes long, so its definitely worth a watch:

Persuasive Personal Informatics

Enjoy!

Leave a Comment

The Axure adventure begins….

I’ve decided it is time for me to learn Axure. Since it’s a product that I’m sure others are curious about, I thought I’d chronicle my adventures….

Currently, my Axure adventures include installing the free trial and going through its 30 minute tutorial. I love exploring new software, so this is a lot like playtime for me. Axure made it even easier. When you go to install its free trial, it provides links with a quick 30 min .pdf file and starter .rp file to help you with the tutorial.

My current favorite prototyping tool is PowerPoint. I have it down to a science and have been asked for my HTML code because the image look so real. Additionally, I am able to make quick walkthroughs, so the user can pretend to use the site. There are a couple bugs in PowerPoint when you attempt this, but overall it works. Axure reminds me of my favorite tool and adds on even more, great functionality. The masters are powerful and quick to use. Interactions seem to be pretty intuitive so far. And, it’ll even generate my specifications for me!

I’m not 100% sold until I try to build some real world scenarios, but I have to say… so far I’m intrigued! Plus, I’ve still got Protoshare to check out.

Leave a Comment

In Stock or Out of Stock?

I had an interesting experience trying to buy a discontinued  item over the weekend (on a side note, I did finally find a place that had one in stock! yeah!). What amazed me is how many of these sites would say “in stock” and then have it become “out of stock” in the cart… or after you try to pay and you get an email a day later. However, my “favorite” site really decided to go with mixed messages:

Is it out of stock or in stock???

Is it out of stock or in stock???

What’s wrong with just putting “Out of stock” or “Discontinued” on the page?

Leave a Comment

World Usability Day, 2009

WUDlogo

I am very excited about this year’s World Usability Day (WUD) topic:  Sustainability. For those of you not familiar with WUD, it is a day for usability practitioners to spread the world and teach their communities what they do and why it is important. I am working with my local usability group (Gateway CHI) to organize another wonderful, interactive day. I will post updates as our plans become more solidified. Until then, I hope any UCD people out there who have not gotten involved will do so. Mark your calenders: Thursday, November 12th.

Until then, check out their website and take the Global Transport Challenge.gtc-logo

Leave a Comment

Conducting Interviews with 3-4 Year Old Children

Over the years I’ve had the opportunity to interview a wide range of users.  Each group has their own special needs, especially the younger ones. Through trial and error, I came up with a successful strategy:

  • Dress comfortably. If you go to interview a CEO of a large corporation, you might want to dress up. With children, make sure you’re comfortable. If you’re comfortable, they’re more likely to be comfortable. Plus, they will think of this as a “play session,” so make sure you’re dressed appropriately
  • Guardian. Allow a parent/teacher to stay in the room if it will not interfere with your study. This will make them more comfortable. Make sure the guardian has something to keep themselves busy. You do not want them interfering with the session. Classroom teachers are wonderful because they can work with the other kids while you are conducting your interview.
  • Location. I found it best to conduct the preschool interviews in the classroom, in a tucked away area. If we were too far removed from the class, the child felt nervous and would clam up. If we were too close, the other children would try to join in all the time. Having an quiet area that is a “safe” distance from the rest of the class worked well. I still had other children peeking in at times, but it was not a huge disruption to the session. And, it actually made the subject more willing to participate.
  • Time. Make sure the session is short. Remember, these kids have a limited attention span. I planed for 30 min per child. Additionally, I made sure we did a variety of activities in that time to keep their attention.
  • Flexibility. If a child does not want to play a game you’ve shown them, don’t make them. You’ll get better data if he/she is being cooperative. Plan multiple activities. If the child doesn’t want to participate in one activity, go on to the next. You can always go back to the original one later, if time allows.
  • Helpfulness. Sometimes, even with adults, it can be difficult to watch your user struggle with an interface. With young children it is even harder. It seems to be part of our instincts to jump in and help a child. In order to keep me from interfering with the data and to alleviate too much frustration for the child, I chose a very specific helping system, based on the activity:
    1. Do nothing. Offer encouragement.
    2. Ask what they are looking for.  This will help you know if they understand what they are supposed to be doing.
    3. Offer verbal help, e.g. “Does it want you to find the hammer?”
    4. Point at the object on the screen/toy that is needed.
    5. Complete the task for the child.
  • These steps also made it very easy to have a numerical measurement for the ease of use of various tasks I had planned.

  • Verbal abilities. Remember children of this age may not be overly verbal, especially with a stranger. Be prepared to have other methods of gathering data. Rather than asking what you like about the toy/software, ask specific things – Do you like A/B? Sometimes a follow up “Why?” will give you more details. Also, use cues like smiles/laughter/frustration to gauge their likes/dislikes. I was even able to gather useful data from a child the did not speak English well. Pointing can be a very strong tool in a situation like this.
  • Stranger anxiety. If possible, spend some time in the classroom/home/with child before your interviews. Even a few minutes of reading and talking before you go into the activities will help put them at ease.
  • Have fun!

Leave a Comment

Usability humor always makes me smile – Medieval Book Player

I was talking with my husband the other day and remembered this great skit. The first time I saw it, I was actually working with an online book website. This one is definitely a classic. Enjoy!

Leave a Comment

EMRs – The first step to a cure is realizing you have a problem

I was reading a blog recently when I saw a post regarding EMR (Electronic Medical Records) and usability. It looks like the Healthcare Information and Management Systems Society (HIMSS) has released a report about how they will integrate usability testing into their task of getting EMRs up and running. They admit that usability is one of the reasons EMR creation and integration has been so difficult. This is definitely one of the holy grails in the healthcare world. When you look at it initially, its easy to say the industry has been very slow to make this happen. However, once you dive into the topic, you realize how complicated it actually is.

I’ve been very lucky to have completed some research in this area. There are a huge number of issues that will slow down the acceptance of EMRs by hospital staff, especially nurses. Nurses are very important to look at when thinking about EMRs because they are the ones who will be in and out of the software constantly, as they interact with patients. Following are some of the concerns that really stood out to me:

Technical Abilities

I had the pleasure to meet a wide variety of nurses during my years at Elsevier. Nurses have a wide range of technical abilities. In general, older nurses are not very technically savvy, while younger nurses are. Addtionally, working in a hospital with software firmly in place (e.g. Veterans hospitals have EMRs fully integrated), increases this savviness. Nurses, who are not quick with computers, are nervous about how their lack of skill will slow down an already too busy work day. Having easy to use software, good training, and a slow paced integration will help alleviate these issues.

Time

Without changing anything in their current work load, nurses are already short on time. The argument can be made that EMRs will eventually ease their work load. However, there will be a learning curve (think about their technical abilities) and there has to be time to get used to the software. Integrating any changes into their current work will need to be done slowly and in such a way that they can still care for their patients. Additionally, the program will need to be easy, fast, and fit seamlessly into their workflow – all traditional goals in usability engineering.

Paper

Right now, nurses have a lot of paper they use to keep track of everything (care plans, notes on how the patient is doing, etc). The paper versions are fast to carry around. The papers can be found quickly in a folder. It’s tactile and easy to read off to people. Simple notebooks are sometimes used as a shift change tool.  The head nurse can quickly flip through pages and see exactly what is happening with each patient and update the next shift quickly. Perhaps customized, overview screens can be used to replace some of the notebooks, especially for shift changes.

Additionally, in some cases, hospitals do not have enough computers for each nurse. All notes are taken on paper. Then, nurses have to wait their turns to enter information into the system. Having more computers readily available will help this situation.

Personable

Nurses pride themselves on their patient interactions. This is why a lot of them choose their careers. They are there to make patients feel comfortable and help them get better quickly. Several admitted their concern about how those interactions could be affected if they have their noses in a computer. They’ve noticed how online forms tend to become very impersonal. When they ask patients information and enter it on a computer, it turns into a question/answer session with no real interaction. The nurse is staring into a computer screen trying to get everything typed in while the patient is feeling more like a number than a person. And, if the nurse chooses to talk to the patient without the computer, they then have to find the time to enter the data in afterwards, which is another task they do not have time for. Making screens exceptionally easy to fill out (easy to find fields, in an order that makes sense, with easy selection options) will help the nurses be comfortable. Also, Tablet PCs may help make this interaction seem less like data entry and more like it currently does with a paper and notebook.

Compatibility

Some hospitals have tried to get systems implemented. In some cases, they have different software for different departments (e.g. Emergency vs. NICU). Each specialty and each staff member seems to have different needs. Getting each person to the information they need quickest has to be a high priority. Once you can make everyone in one hospital happy, then you have to figure out how to tie this data into the entire medical community. It’s a big job!  Allowing customization for each hospital/department may relieve these issues. However, there should be a common, underlying data structure that will allow for easy integration with other record systems.

The above topics do not even include big issues such as security and patient safety and integration with private physicians, all huge issues that will also need to be dealt with. Even the Obama administration is aware of the integration issues. They have earmarked billions to help research and create an integrated EMR system. However, even with all the problems. This is a goal we need to strive for. If we do manage to design a system that will speed up the administration side of hospitals, enable easy access to a patient’s entire history, and save patients lives by catching potential mistakes, we’ll be able to help more people and give staff the time they want and need to spend more time with their patients.

Comments (3)

Dilbert – follow up on “Balancing User Needs… aka Bartering”

After posting my last blog, I remembered this comic from Dilbert that came out earlier in the month…. maybe someone didn’t prioritize based on user needs 🙂

Dilbert

http://dilbert.com/strips/comic/2009-07-01/

Leave a Comment

Older Posts »