[Sigia-l] Forcing practice

[Anne Miller]

there are a number of fairly simple solutions that can help to reduce the
problem:

1. I suspect that users have to complete a process (?) Make the process
visible by a) telling them how many steps there are. You can do this by
providing text instructions on the interface itself at the beginning of the
process  and  b) by numbering each of the steps event to the level of text
box labels. Numbered tabbed windows are a similar solution.

2. If data entry is a problem then give an example of the the format you
require above/beside the text box  eg ../../.... as for dates,; use text box
masks, such as the date slashes to indicate how you need the data to be
entered; put in the currency sign and decimal points if relevant.

3. Hiding problems is like taking down the signs around a mine field - keep
the signs up. Tell users what the likely errors are and their effects, again
by including a simple message at or near the site of potential error for
example 'Please enter your staff number and remember to include a space
between the 4th and 5th digit. If you dont include the space your pay will
not be processed'. Dont worry about these messages making the application
clumsy (It already is) or giving users the idea that the application is
problematic - again it is and they will find out- tell them where the issues
are and at least they'll know that you're trying.  Popup boxes in this
instance are a less than satisfactory solution a) because they are annoying;
b) because people dont read them (because they're annoying); c)when you
realise that you should have read the popup you cant get it back.

Up front forcing practices wont help and tutorials are only marginally
better. Users need advice at the point where the error might occur - connect
information with actions

I agree with the other contributers that a usability evaluation is about the
only way to really identify the kinds of errors people will make. Based on
outcomes you can start thinking about the kinds information needed to avoid
the problems. A good copy writter here is invaluable.

Hope it helps

Anne Miller
Coordinator
Human Factors Online
Key Centre for Human Factors
University of Queensland
http://www.humanfactors.uq.edu.au

-----Original Message-----
From: sigia-l-admin at asis.org [mailto:sigia-l-admin at asis.org]On Behalf Of
Peter VanDijck
Sent: Tuesday, 30 September 2003 1:11 AM
To: sigia-l at mail.asis.org
Subject: [Sigia-l] Forcing practice


The situation: an online application that has to be used by many users.
The probability of them entering wrong information is high because of
the complexity of the app, and the app cannot catch all data entry
errors. We can't change the app.

Part of the solution: when a user visits for the first time, a popup
forces them through a learning process. The goal of this is to minimize
the errors once they get to the app.

My question: what form should that learning process take, and how can we
ensure they actually learnt something and didn't just click through the
popup?
All ideas welcome - go crazy!
Peter
------------
When replying, please *trim your post* as much as possible.
*Plain text, please; NO Attachments

Searchable list archive:   http://www.info-arch.org/lists/sigia-l/
________________________________________
Sigia-l mailing list -- post to: Sigia-l at asis.org
Changes to subscription: http://mail.asis.org/mailman/listinfo/sigia-l