I think that the addition of a "I don't know" function would depend on the particular question. If you were asking me "Are you going to retire at 65?" I could easily see "Yes", "No", and "I don't know" since I might be considering future economic changes that are not entirely predictable (I can actually see "I don't know" as being the most common answer for some age groups). So, I think that a good answer to your question would require specific knowledge of the questions.
Chauncey On Fri, Aug 29, 2008 at 5:56 AM, सोनल Sonal Nigam <[EMAIL PROTECTED]> wrote: > Hi > > I would like to know about the drop down values for the forms that I have > been creating recently. The values are only Yes and No for the dropdowns > varying from 5-9 in number in a single form. I just want to know how best it > is to provide the user with a YES, NO and I don't KNOW as the values for > dropdown? Any best practices regarding whether the I dont know should or > should not be provided to the user? Will it confuse them? Assist them? > > > > The app is a financial application helping user choose the best financial > product suiting their needs. All comments welcome!!! > > Cheers > Sonal > ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... [EMAIL PROTECTED] Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
