About HFI   Certification   Tools   Services   Training   Free Resources   Media Room  
               
 Site MapUser Experience for a Better World   
Human Factors International Home
Free Resources
Bookmark and Share

Ask Eric: Questions & Answers

Each month Dr. Eric Schaffer answers selected questions on usable interface design. Recent Questions
Archived questions and answers about ...

Knowing Users and Testing Interfaces

December 20, 2004 – submitted by Rahul Prabhaka of Bangalore, India

Question: How can we pick out flaws in our documentation using Usability Testing?

Eric's response: You can certainly include the documentation in your usability test. Simply make the materials available and allow users to access them as needed. I think you may find that they are rarely used. But if they are used there should be plenty of insights.

Alternatively you can specifically test the documentation by giving the user tasks such as "Find the installation procedure in the manual."

Top

November 8, 2004 – submitted by Leona of Malaysia

Question: I would like to know more about usability testing, especially how to conduct a usability test for a Web site. Thank you.

Eric's response: User-centered design takes much more then just a usability test. Usability testing is the way that we 1) fine-tune our design and 2) verify that the design is working. We have two types of testing that correspond to these two objectives. Formative testing helps us fine tune designs. It's a dentist having you bite down on carbon paper and grind your teeth to see where the teeth must be smoothed out. Like this, we have users try to use the site and see where they get stuck. In summative testing we have criteria for success and we test the user to see if these benchmarks can be reached. For example: we know a competitive site allows users to sign up for an account in 3 minutes. We test to ensure that our new site is more efficient.

Top

October 9, 2004 – submitted by Heidi Bush of Clearwater, FL

Question: I am part of a team developing a new Web site and application. The marketing manager would like to "test" many versions of the home page in a live environment – meaning once the site has been built. The home page is not just a static page, but incorporates many programmed elements that, with each change, will require substantial programming rework. The testing aspect will be critical to determine what layouts, colors, and ads/offers work best to boost sales and the marketing manager feels that testing it with "real" users is critical. Are there any testing methods that could be used to yield valuable results and eliminate the need for these real-time changes to the live site?

Eric's response: The live site testing idea is very useful. There is no way to get data as good as live site data; particularly if you have a split site model. By running two versions of your site (and randomly assigning people to each version by cookie) and comparing results, you will really have unbeatable data.

However, before getting to the live site work you SHOULD apply the developmental methods. This includes a user-centered design process. It includes in-depth data gathering and application of research-based principles. It also includes formative usability testing. In this way the first version of the site will be excellent and you can use the live site process to continuously improve it. If you do not do this you will find you are trying to evolve the site from a weak start. This will be long and painful.

Top

September 29, 2004 – submitted by John of Greece

Question: What factors influence how quickly Web pages are retrieved from the Internet?

Eric's response: There are a whole set of factors that affect the bandwidth. This includes the type of connection (dial-up, various broadband choices, etc.) There are also factors related to the positioning of the server and its level of connection to the Internet backbone. Then there is a major factor of the page weight (number of bits in the page design).

Interestingly, the actually page display time is not as important as we initially thought. The way that the page displays is important (if you can get the user working, say by displaying test first, then the fact that the download is continuing is not that important). In addition, a useful and engaging page will be SEEN as faster, even if the actual download is slow.

Top

August 17, 2004 – submitted by Jasleen Kaur of Malaysia

Question: How do I define and relate usability to a Web site for kids which are 4 to 6 years old?

Eric's response: It does not really matter the nature of the users. The process for kids is the same as any other group. You complete a user-centered design process. Identify their needs and structure the site to fulfill these needs. Focus your efforts on the important user performance and experience objectives. That means speed, accuracy, self-evidency, satisfaction, and/or safety. In the case of a kids site I would focus on safety, self-evidency, and satisfaction in most cases.

Designing for kids in this age range certainly has specific challenges. Consider their reading capability, attention span, domain of interests, etc.

Top

June 18, 2004 – submitted by Julie Christensen of Green Bay, WI

Question: We would like to measure how much time savings there is before our portal implementation and after. Is there any industry average on how long one mouse click takes? We thought if we could measure how many clicks were saved with the portal we could put a time/dollar figure to that.

Eric's response: Indeed you can measure the average time for a mouse lick or keystroke. However this is a small fraction of the time spent at a portal. The primary time is spent scanning and reading. So measuring the physical movements won't be very interesting. If you want to make a comparison to show the change, develop a 'basket' of representative tasks (e.g., "find new employee's phone number", "find HR site"). Then run a usability test contrasting the original situation with the portal. I think this will be most meaningful.

Top

June 7, 2004 – submitted by a student in Toronto, ON

Question: I'm a college student in an internship for New Media. I have been given the task to write my *own* user testing method for a small scale software. I'm not very familiar with in-depth testing methods – are there some guidelines that I can follow to write my own usability test?

Thank you.

Eric's response: Well if you want to develop your *OWN* method don't ask Eric. I only know methods I learned from other people... And maybe a couple I developed myself.

If you want a book for "inspiration" I can heartily recommend Handbook of Usability Testing: How to Plan, Design, and Conduct Effective Tests by my old friend Jeff Rubin.

If you want to just read one sentence...

Make up a set of representative tasks and tell a sample of
representative users to each complete the task without
help, while you watch, and then see where they get stuck.
Top

May 14, 2004 – submitted by Audrey Klarzynska of United Kingdom

Question: I am a Corporate Data Manager and would welcome your views on the following. I recently requested that a supplier currently developing a COTS prototype for the organization provide feedback on the level of compliance against the corporate policy and standards. One of the policies to be looked at was the Usability Policy. In the comments, I stated (perhaps unadvisedly) that implementing a COTS solution puts the organization at a disadvantage regarding usability as a truly usable system can only be achieved by designing it to meet the needs of the specific user group(s) involved, i.e. bespoke. And that using COTS means that a compromise must be reached between the solution offered and the users' perception of how information should be presented. This was stated in the context that the design of the COTS product could not be customized to any large extent. I would welcome your views on this as the project manager has taken umbrage and said that COTS are "more usable than bespoke".

Eric's response: Audrey, I am sorry that your supplier took offense. However, in general you ARE correct. Without question the wider the target population and taskflow, the harder it is to make a solution that is ideal for all users. Since I think it is safe to say that COTS packages must accommodate a greater diversity of users, taskflows, and environments, they have a much harder time being usable. On the other hand, if a COTS development company invests enough in usability work their result can be BETTER then a company doing a customized job without the benefit of a mature usability operation. So rather then depend on generalizations it is best to evaluate the supplier based on the quality of their process and product. Check carefully how well the product meets your needs.

Top

May 13, 2004 – submitted by Sarah Worden of USA

Question: One of the fundamental principles of usability is to "know your user". Giving specific examples, what is the importance of user profiling as part of interface design.

Eric's response: Very fundamental question! Let's take some examples....

A medical application for doctors can have more complex language then for patients. It can also include more graphic images and blunt assessments.

A site selling banking services for high net-worth customers will be different then a college credit union. It will have to have more sophisticated investments available. It will be able to use more complex terms. The font must be larger (as the users will be older and therefore generally have worse vision). The style must be different (due to the required difference in branding and also due to differences in population preferences).

An online marketplace might work for customers in the USA. But in Japan it fails because they do not use credit cards. Also they make decisions in a group process that makes the timed auction difficult. Of course translation to Japanese and Yen is important. But color preferences are also different.

In user-centered design we design for specific ranges of users. The wider the range, the harder the job. Without knowing the user, the design has little hope of success.

Top

March 26, 2004 – submitted by Jeff White of Charlotte, NC

Question: My company is finally redesigning their corporate Web site. They are striving to be more "customer-centric". Toward this end, they plan to hold focus groups, and focus groups alone to determine our user needs, and from that determine feature sets and functionality requirements for the site. The plan is to hold the focus groups and then let internal line of business reps determine the feature set for the new site.

I am a big proponent of User-Centered Design. I am thrilled that our executives are finally striving to be customer focused, but I am petrified of relying of focus groups alone, and then letting internal staff run with the data.

I know focus groups often produce misleading, biased results and I foresee them causing some big problems in the long run unless we adopt a more robust UCD process that includes other research methods such as contextual inquiry, task analysis, user profiles, etc.

What advice can you give me, or what resources could you point me to that will help me convince my bosses that we need a larger variety of research techniques to accurately get a picture of our target audiences?

Eric's response: Well it is common today and a good thing that executives are understanding that usability is mission critical. However, as your case illustrates beautifully; this understanding of criticality does NOT translate to an immediate understanding of the HOW of user-centered design. Their focus group approach is virtually certain to fail. It is pathetic. What is WORSE, you may find that they decide that user-centric design is of limited value when they find that a focus group does not translate to a great Web site. (Sigh).

The very best thing you can do at this moment is get the executives educated. Don't expect them to listen to you from within the organization. They will only listen to ultra-credible outsiders. My book "Institutionalization of Usability: A Step-by-Step Guide" is a good bet. It gives a clear outline of the requirements for mature usability work. It also specifically addresses the focus group problem. Also consider getting them in touch with a usability consultant who can guide them to a proper understanding and plan.

Top

March 11, 2004 – submitted by Mark Simpson of UK

Question: What are the key aspects of usability and how might they apply to a test plan for a customer booking database?

Eric's response: The key MEASURES of usability are speed, accuracy, training requirements (or self-evidency, satisfaction, and safety. These then become the things you may want to test in your session. Specifically test how long it takes to do the major booking tasks. Can people in fact accomplish them? Check the error rate. See what training they need to operate the system. Also, you might have participants rate their feelings about the interface.

Top

March 9, 2004 – submitted by David Wasilewski of Manchester, UK

Question: Are there any standardized tests/research that suggests at what point that a college or university student's handwriting speed will start to adversely effect their exam performance?

I am asking this from an angle of testing for exam concessions e.g. extra time.

Eric's response: In the USA students with significant handwriting impairment get extra time in some tests. You might check the rules used. However, I think they are quite rough and probably have little scientific basis. I suspect they amount to a 'note from a doctor' approach.

Top

March 1, 2004 – submitted by Theodoros Krommydakis of Germany

Question: I'm currently developing an administration solution for a small gardener's company. Is it a good strategy to actively involve my customer in the development process, meaning to turn him into a usability tester? I was considering to provide him with the functional specification at first and give him frequent access to the evolving versions of the software in terms of testing and evaluating. Do you think that it would be appreciated from the customer, or would it leave an impression of nonprofessional acting.

Eric's response: Involving your customer is certainly a good thing. Research shows that more involvement is good. Also in Germany, the DIN standards actually require involvement of users. However, the question is HOW to involve the clients and users. The method you described may not be very effective. I recall acceptance testing which involved mailing a 4-inch-thick requirements document to the managers of the users. They could not really understand the document and just ignored it.

Your client should be involved in briefing you on the direction and vision of the interface. Then they should help work out the strategy for tuning that design based on the data gathering you do. That is about it.

Users should indeed be sources of data and should be used as test subjects. It is however VERY important not to have a single user involved repeatedly. Use a set of users to gather data. Then use a DIFFERENT set for usability testing. Once a user has participated they become 'polluted'. Their opinion and understandings are changed by their experience with your project.

So involving the users is VERY professional. But you have to involve them properly. Always remember... USERS ARE NOT DESIGNERS.

Top

February 16, 2004 – submitted by Dana Griffith of Columbus, OH

Question: Hello to all at HFI. I am searching for research on what, if any, effect privacy policy statements have on users of online account management sites. Do people avoid using sites that don't have them? Do they consider sites that do have them more worthy of trust? I would appreciate any insight you can offer. Thanks.

Eric's response: This is an interesting case where many people SAY that it is important, but almost NO ONE actually looks at it.

Top

February 2, 2004 – submitted by Ishtar Joren of United States

Question: I am working on developing a usability test plan for our product's UI. I have a list of heuristic evaluations but do not really know how it's done. Do we take a checklist and go screen by screen and put down our evaluations? I would like to know if there is any source that would give me some practical knowledge.

Thanks a lot!

Eric's response: The idea of a heuristic evaluation is to go through the screens considering each point in the heuristics. This is not very effective (catching perhaps 30% of issues). I suggest at least getting yourself some training in UI design. Then you can review the screens based on the multitude of far more specific principles and research findings. This will certainly be better.

I also wonder, based on your question, if you have a full user-centered development program. Reviewing screens is a hopeless way to compensate for lack of systematic usability engineering practices. I would hope to see definition of target users, data gathering with actual users, task analysis, task design, etc. I would hope that about 10% of the development community is comprised of usability practitioners. If this is not the case you can pretty much rest assured that the design is poor.

Top

January 24, 2004 – submitted by Umesh Persad of Cambridge, UK

Question: I would like to find out what the latest research has to say about the number of users, and type of users necessary for testing products for older users. Do we include users with all types of ailments e.g. visual, tactile, cognitive and try to optimize the product for all types? If the effects of aging are gradual, then the users chosen never remain the same, so how can we be sure that the population of older users is being represented accurately in our sample?

Eric's response: Well actually you are raising two separate issues. In testing for aging populations it makes sense to test five to ten older users. There is MUCH controversy over exactly what is considered 'old'. This is best determined by your actual expected population. If you will indeed HAVE a significant user set over 80, then test users over 80.

Specific ailments are different. They are not entirely age related (though there is a correlation). You can certainly find young users with almost every possible impairment you might find in older users. In general we manage this not so much by testing, but by designing with those limitations in mind.

Top

© 1996-2012 Human Factors International, Inc. All rights reserved  |  Privacy Policy  |   rss feed biber hapıbiber hapı