Take the 2-minute tour ×
User Experience Stack Exchange is a question and answer site for user experience researchers and experts. It's 100% free, no registration required.

I am trying to design a UX that allows random visitors on a website to quickly give us information about what books they/their child are reading in school. The site itself is a company that provides audiobooks for students with learning disabilities.

Some ideas that have been floating around is things such taking a picture of your books and upload it, some sort of incentive for telling us which books your using.

Some of the complications are that the best data for us to collect would be ISBN number, bookshelf number, publisher, etc.. this is quite clear that it is not user friendly.

Are there best UX practices for asking users for data that do not just seem like a regular form on a site page?

share|improve this question

1 Answer 1

up vote 4 down vote accepted

To be the least intrusive I'd just ask for only the title of the book; anything more likely requires actually getting the book, plus filling out more form fields. If I'm reading Where the Wild Things Are to my kids I'll almost certainly know the title of the book (especially if I'm reading it several times). Other information requires good knowledge of the material (author) or pretty much requires the physical book (who remembers ISBN numbers offhand?).

Insert a little flavor into your form; "What are you reading tonight?" or "What books do your kids love?" are much more engaging than "If you could spare a moment of your time...". If you can make it sound a bit more personal; how personal depends on your audience, but sites for parents of children with disabilities tend to be fairly lighthearted.

Sending pictures is kind of a cute idea but may not get the participation rate you're hoping for. It might be an interesting way to engage people though; send pictures of your kid's book collection or something. (A possible problem would be eReaders and audiobooks; hard to take pictures of those). It would be a more complicated endeavor than an exit survey or similar though; I imagine it'd work much better with a closely knit community. I can see this working for a community library but maybe not the New York Public Library. Actually people are often fairly passionate about libraries in general, so it may not be as unfeasible as with some industries.

The thing about effective survey collection methods is that they put the burden of work on your staff, not the user. As with most things in UX, the more you can do for your users the better, because 10 hours of your work might save 10,000 users 10 minutes of their time, it ads up fast, and in this case it may well be the difference between completing a survey and abandoning it.

Collecting ISBNs would make the process automated at your end, but you'll get a lot less responses. Instead have someone ready some time to go through the supplied titles by hand (there may be typos) and locate that data on your own; only ask for what you can't find based on title. It's possible you may be unable to locate certain books, but throwing out a few extreme mispellings or obscure books from a large body of replies is better than a perfectly organized but much smaller body of replies.

share|improve this answer
    
This was great, I appreciate the insight. I am completely aligned to your thinking as well. My suggestion would be only Title for quickness and less cognitive load as whole submission. The audience can be very enthusiastic about our work, especially since we are a non-profit. But I would most certainly not disregard the fact many new/random users may not have that full trust/passion for our mission. The copy with the adding flavor into the form is a very interesting suggestion. I would only be afraid of being too specific and turning off other possible entries because of wording. –  Kyle Mirro Nov 15 '12 at 20:03

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.