Wording confuses the newbie

[tmdavenport]

We are using DHPOS 6.32b and have receipts set to ask, and it does at the end of the sale.

Just wanted to voice the concern of 2 of my workers. They only work occasionally, and when they do seem to be stuck on the fact that after you press +, Item 3 says "Print receipt, complete sale"

The stumbling block arises because they don't want to print a receipt, but they want to complete the sale.

If you could, just re-word it to say "Complete sale, Print Receipt (Optional)" or just leave the Print Receipt part out until the end when it asks if you would like to print a receipt.

Real trivial, but I can see where new users or people who have trouble thinking outside the box, may have issue with it.

[Andrew]

I don't see a big deal with this - I mean, if you're training these people they will know you don't print receipts all the time, and that the option will appear on the next screen anyway.

[Tina]

Did I miss a beta somewhere along the line? Does 6.32b exist yet or is it a typo?

Tina

[Andrew]

It's not a typo, it does exist.
http://www.dhpos.com/discuss/phpBB2/viewtopic.php?t=745

[tmdavenport]

Andrew,

You're absolutely right, it's not a big deal. I've been in the customer service business for over 11 years now though and have found that usually, it's the little things that really make a difference between something functional, and something memorable in a positive way.

A little bit can go a long way to help those computer users who are scared of the computer. If they are constantly having to hurt their brain to figure things out, that to them don't seem logical, it doesn't make their experience any better.

As technicians, we take so much for granted that to us is 2nd nature. To someone who barely knows how to turn on a computer, it's an almost insurpassable hurdle.

Trent

[Andrew]

Well I think DHPOS is one of the most user-friendly applications I've seen. Dale has used plain language throughout the program where possible.

This case is a good example, as soon as someone presses enter on the option to complete the sale and print receipt, the next menu they see asks if they wish to print a receipt or not.

Surely - after training on use of the system (which shouldn't take long given the ease of use), an operator would remember that menu is set to appear, and give them the option to print or not.

It's like riding a bike - you never forget. I used to work in a supermarket, had another job for about 4 years, and had to go back to another store - which used the same POS application. Within a couple of hours on checkout, I'd remembered most of the shortcuts and menus of that system.

[tmdavenport]

Andrew,

Doesn't sound like you've worked much with typical users and computers though. I was the Internet manager for the cable company where we had 2000 clients. I would get phone calls day after day from the same handful of users that couldn't remember how to open their email.

If you're technically inclined, it's a snap. If you're not, less confusion means happier employees.

Trent

[Andrew]

I was a tutor at a computer training centre for 4 years, with students who jumped when you said "mouse" to students studying computing and business administration level courses.

If that job didn't teach me something about average computer users - I don't know what would.

[Guest]

i dont see the harm in changing it. some people are stupid w/computers

[Dale Harris]

I have done my best in making the instructions on the screen as simple and clear as possible. But it is a "no win" situation.

No matter what instruction I write they will confuse someone. For example I was once told that the "[+] = Total" instruction was confusing because the users wanted to end the sale not just total it. I then suggested "[+] = End" and was told that they would then think that pressing [+] would just erase the sale. All right, how about "[+] = Complete" and was told that the sale was all ready complete when the last item was entered so "[+] = Complete" would logically do nothing. So screw it, I just left it the way it was.

Then you have to take into consideration that different users use different features. If I had the instruction read "[+] = Enter customer info" that would not be useful if your register does not take customer info or you take customer info before you start the sale.

Yesterday I received an email telling me that the program had too many instructions and I should take some of them out completely. You just can't win.

[smckane]

There comes a point where some-one will moan about every aspect of the program. I like it how it is, sure there are bits I'd like worded differently and coded differently, but isn't that the way with Office, Windows and every other bit of software you've ever used?

Dale, I like it. I like the constant addition of new features. I like the inclusion of the user base. I like that it feels as though I have input. The software has a human touch to it.

Nothing is ever perfect for everyone, would we like it if it was?

[tmdavenport]

Dale,

Love the program, could afford a till and am very happy I found your software. I am running POS on a networked DOS only 486 machine with a keyboard based bar code scanner and a serial printer, which fires my cash drawer.

You are absolutely correct, it's a no-win situation.

Some day when you just feel like a major overhaul, maybe introduce user customizable parameters, then people could just make it say anything they wanted. That's likely the only way it would be suitable to cover all eventualities. I've seen some programs with this ability but don't suspect it would be easy to change.

Anything you do to the program is awesome. Thanks.

Trent