Re: Locking out "stray input" on a Pocket PC
- From: "Beverly Howard [Ms-MVP/MobileDev]" <BevNoSpamBevHoward.com>
- Date: Wed, 09 Aug 2006 10:58:18 -0500
Thanks for the response.
>> We had a declarative vocal response from almost every tester (all between the ages of 65-85) that... <<
Again, I point you back to the users... the age different _is_ significant, so, consider refocusing on your (the programmer's) relationship with the users.
As I programmer for almost a quarter century, I found (eventually) that sitting with the users (and keeping my mouth shut) was one of the most important part of my job designing software.
Watching them use the software, my goal was not to "educate" them on how to use my product, but to let them educate me on how they wanted to work and how they _expected_ the program to function to help them do the job where _they_ were the expert. In addition to watching, I'd have extended dialogues with them to help _me_ understand why what I had produced was not working as well as it could to help them achieve what they need to accomplish.
You indicate that you are getting feedback, but it appears that it's advesarial feedback... a focus on the negative rather than the positive aspects of what you are trying to achieve.
If the users are drawn into the development process, the answers to this and future problems will be there... for example, asking why something is confusing and solidifying that by asking what they would do to deal with the problem. If they are invested in the project and begin to see their input and suggestions implimented, you both will make progress.
>> that color differences and screens made them feel they had broke something. <<
This is a "defensive response" ...it's easier for a user to place blame than to admit inability to deal with the program in the first place, which points back to getting them invested in the design so they can "deal with the program." With advancing age, it's exaggerated by cases where you are faced with the increasing ability to do things you once could with ease... and denial that you can't or that somthing else is responsible for that is an easy "out"
If the screens changing create confusion, handcuffing them so they can't do anything is going to create more confusion... pointing back to the original problem, they are taking action against what the device is doing which they seem to be disconnected from.
You give their age range (fwiw, I'm near the bottom of the ages,) but what is your age and the age of others involved in the project? What kind of personal and social interaction do you have with them beyond the tech details? How do you get feedback?
Beverly Howard [MS MVP-Mobile Devices]
.
- References:
- Locking out "stray input" on a Pocket PC
- From: JadeBlueSkies
- Re: Locking out "stray input" on a Pocket PC
- From: Beverly Howard [Ms-MVP/MobileDev]
- Re: Locking out "stray input" on a Pocket PC
- From: JadeBlueSkies
- Locking out "stray input" on a Pocket PC
- Prev by Date: Re: How to check mail2web email from Desktop Outlook??
- Next by Date: Re: Removing Phone App from Device
- Previous by thread: Re: Locking out "stray input" on a Pocket PC
- Next by thread: Re: Locking out "stray input" on a Pocket PC
- Index(es):
Relevant Pages
|