GUI screens are good for the occasional user who doesn't know the
appropriate values for a field on the screen. However for the heads down
data entry users it actually causes problems that can not be detected.
Since drop down lists always ensure a valid value (not necessarily the right
value) an operator entering "OF" instead of "OR" in say a State drop down
box winds up in Ohio instead of Oregon and the entry person doesn't even
know it happened. No beep no error message just wrong data.
Tim
-----Original Message-----
From: Peter Osborne [mailto:[log in to unmask]]
Sent: Monday, March 08, 2004 4:37 PM
To: [log in to unmask]
Subject: Re: [HP3000-L] Old vs. New or Browser vs. View
Once someone is used to a GUI based data entry screen, should it not be just
as fast? If the screen is written an intuitive manner, couldn't one use TAB
to advance fields and pulldowns should advance to the proper item when the
user types in the value the same way better web browsers work? If a GUI
screen is written properly, an experienced user should not have to reach for
the mouse.
Pete
On March 8, 2004 04:22 pm, Shahan, Ray wrote:
> Hi all,
>
> I was watching some testing being done on the latest in technology
> <ahem>. The new screens are GUI/Browser-based/add-latest-term-here
> screens, and as I watched, I saw a couple of interesting situations. One
> was the entry person using the mouse to ENTER the screen (remove hand from
> keyboard, grab mouse, move mouse to ENTER, and click), but the other was
> really a gaping issue. Since this is a new system, they are using some
> entry folks that are very good at what they do on the old system...these
> folks however, had issues with the drop-down menus for State, Dates,
> Company Codes fields in the new screens. They were flustered by the time
> it took to navigate these pull-down menus because they were used to VIEW
> screens and heads-down data entry. When these folks voiced their concern
> over the time it would now take to key an order received by mail/FAX, they
> were told that the new screens would be more accurate since you couldn't
> key bad info in, thus the time to key orders would be quicker overall (no
> one mentioned that just because you have a drop-down menu doesn't mean you
> can't still pick the wrong selection).
>
> So, has anyone else ran into this and if so, did the keying time
> for batch input actually get quicker or slower?
>
>
> TIA,
>
> Ray Shahan
>
> Life is not a journey to the grave with the
> intention of arriving safely in a pretty and
> well preserved body, but rather to skid in
> broadside, thoroughly used up, totally worn out,
> and loudly proclaiming:
>
> -- WOW!!! What a Ride! --
>
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
