[Sigia-l] Forcing practice
Yogesh Tadwalkar
yogesh at microusability.com
Tue Sep 30 03:51:12 EDT 2003
Hi Peter,
You said:
> 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.
Much has already been said about testing to investigate why users are making
errors and then fixing the root cause through redesign and contextual help.
But I read what you said >We can't change the app.<
I had encountered a similar situation before. And providing examples of
'right and wrong' data entry right at the place where data would be entered
resulted in reducing the number of errors to a great extent.
Of course, this increased the overall clutter and affected the 'look'. But
users in a
'task-oriented' mode did not seem to mind it too much as long as they could
get their job done.
To reduce the clutter, only 'right' example could be provided.
And of course, not all instances of data entry need to have an
example. Furthermore, as users get used to the app., the examples can be
phased out.
I do not know whether this can be applied to your app. Can it?
with warm regards,
Yogesh Tadwalkar
More information about the Sigia-l
mailing list