Best practice for data entry

[MannyF924]

Hi Folks,

I'm looking to get opinions or expert advice on the best method to enter data on a form.
Is it better to have a user click and pick from lists and or buttons or is a streamlined data entry process of tabbing to the next field better?
Of course it depends on the data and the business model but I am interested if anyone has some insight on how they approach determining the best method. Mixed data entry modes seems too cumbersome.

Thank you in advance for your input.
Kind Regards,

MCF

 

[GinaWhipp]

Welcome to the Forum!

Hmm, not an easy question to answer but here's my two cents...

I design Forms based on the End User. So, if they are accustomed to Excel I may design a Form to look like Excel and navigate like Excel. That said Form Design has more to do with the Business Model than you think. While the above might work for looking at rows of data like Customers it's completely inappropriate for Order Entry.

Noting that you said *mixed mode* seems cumbersome, well, why? While all the Forms can be similar you will end up with mixed mode no matter what. I would not make my Order Entry Form look like my Inventory Form as the Order Entry is going to one-to-many and my Inventory Form is just going to show me a list of items in stock. However, I may also have an Inventory Form that just shows me one *part* as that part may have too many components to show in a Continuous Form.

So, in the end... determine the Business Model then determine how your End Users work (their comfort zone) and start creating Forms.

 

[spikepl]

The important thing here is to see what the front-line troops do - which forms do they use how often (=very important criterion) and what for.

The opinion of managers that do not sit with this all day long is irrelevant for the design (but unfortunately counts, because it is tough to convince managers that their opinion is irrelevant, and because they are the ones to sign off on stuff).

Clicking with a mouse in eg a search form with multiple criteria and repeated usage throughout the day is a complete PITA.

Update: Even lists, dropdowns and buttons/checkboxes can be reached by tabbing, keyboard short cuts and special keys. For foms used once in a blue moon it hardly makes any difference. But many applications have one central form from where you conduct the battle, and these are the ones that often really deserve mouse-less access.

 

[MannyF924]

Thank you Gina for welcoming me!
Let me provide a little more background. I develop using MS Access, I've worked with clients as you say from the end users perspective and that is the best way I agree.

The problem I'm running into is, as Spike points out, I'm dealing with an owner who wants it one way because it's... his way. :banghead:

I sat with the users over a period of three weeks to observe their process. My impression based on some of their feedback but also from experience is that I would design a more keyboard centric entry process than mouse based.

Spike, yes I agree, drop down lists and other objects like check boxes etc can be managed with key strokes. That's one reason why I tend to like keyboard based data entry because many scenarios can be handled that way. There may be a time and place for both click and type but I find that situation isn't necessarily a high paced one requiring quick processing or large amounts of data entry.

That is the other component - this is a fast paced, high transaction environment (care and companion workers) requiring quick response and updating of schedules and service orders. One suggestion for instance was to use buttons to enter time having one for each quarter hour for all 24 hours. That takes form space not to mention it's a visual nightmare - I believe appearance should be neat and as clutter free as possible, keep it simple for the user.

So to get to my point... I'm being pushed to build based on doing more with mouse entry and 'buttons' when I feel the best mode would be keyboard based. I was looking for some validation and or feedback on what others do so as to keep an open mind and consider other options.

 

[spikepl]

"One suggestion for instance was to use buttons to enter time having one for each quarter hour for all 24 hours" ( keyboard-centric way would fx be to allow intelligent typing; i.e. 1245 for 12:45 etc)

I'd wager it is not the guys in the firing line that suggested this. Sadly I have seen this over and over again - the troopers' wishes and desires get overriden by the desktop generals.

As to your owner: Tell him you are designing an ergonomic interface. That means that a). he will not have to pay people for repetitive strain injury, and b). he shows that he invested in the wellbeing of the employees. The inverse of this is to design a mouse-centirc interface that he has been warned about, and if you are US based laying himself open to all kinds of BS

 

[GinaWhipp]

MannyF924,

Yep... welcome to my world. However, you must find a way to *relate* to the check writer that the database is being designed for the masses not the one. What is it Spock said... "The needs of the many outweigh the needs of the one." Or use what spikepl posted but find a way or you will have a lot of unhappy Users and you'll probably end up changing it in the long run.

You could also provide a demonstration of *time saved* with what the Users need and what the manager is asking for. Some people just need to see how much time is *wasted* their way. In a fast past environment this might be a big push for you to *do it your way*.