We're developing a form which may have a variable number of follow-up questions (based on user answers to an earlier question). Depending on user response, there could be between 0-13 follow-ups.
We are debating between using a single page with all of the follow-ups (however many appear), or a page for each of the 0-13 follow-ups.
My preference would be for more questions on a single page, to avoid extra clicking and to avoid confusing users who may not be expecting to be presented with multiple very similar pages.
However, I fear with this approach users may have issues when the form validates -- they now have to scroll through to find any questions they forgot to answer, where if each question is on its own page it is trivial for us to validate before we move to the next question.
This UX matters article seems to also agree with the long page idea, but it is aimed more at normal web pages rather than forms.
This question is similar, but I don't feel it applies because we aren't talking about a number of related items in a few categories, but rather a number of very similar items which all belong to the same logical category.
Assumptions: users are highly likely to be unfamiliar or uncomfortable with technology. They are likely older, perhaps disadvantaged. Also, while the entire range of question counts are valid (0-13), we suspect but do not have data to prove that the bulk of respondents will receive 1-6 questions.
Answer
I think given the target user, single pages for each follow up is probably best. "Chunking" such as this simplifies task completion. Moreover, less chance for users to be surprised by the page changing (and confused about what has actually changed).
Another plus of the single page per follow-up approach is that you can give users a sense of the total length for the process as soon as the first page has been completed. Perhaps you can frame the first page as a kind of "tailoring the process"/"qualification" step.
Regarding accordions, you might be interested in this article from the Baymard Institute in which they reported common user difficulties with this style of page interaction: http://baymard.com/blog/accordion-style-checkout. As an example, they saw some people use the "back" button in the browser to go back to another section, and consequently lose work. That was partially an implementation failure, but it reflects a broader issue with the accordion model.
Hope this helps,
Jessica
No comments:
Post a Comment