Think about how the questions flow and group them in a way that makes sense to the user.
Begin prototyping with 1 thing per page
Follow the GOV.UK principle of each page containing just 1 thing, for example:
- 1 piece of information you're telling a user
- 1 decision they have to make
- 1 question they have to answer
User research will tell you when you can merge pages together. For example, if you’re designing a service for staff who need to repeat and switch between tasks quickly.
Watch out for "double-barrelled" questions
Make sure you're asking 1 question at a time - not 2 or more questions in 1.
2 questions in 1:
If you have an email address, can we contact you about research?
4 questions in 1:
If this questionnaire has highlighted any problems, how difficult have these problems made it for you to do your work, take care of things at home, or get along with other people?
Get your filter questions in early
Filter questions help you route people to the questions that apply to them, so use them early on.
For example, start with questions that let users know if they’re not eligible for the service, so you do not waste their time.
Start with essential, common, and easy questions
Start with essential questions ahead of optional ones.
Design for the most common scenarios first. You should have a good idea what they are from your discovery.
It may help to start with easy questions (consider the effort involved in answering) and to save more difficult or sensitive questions for later.
Group similar topics
Talk through the questions and listen for natural pauses between topics. Think of the form as a conversation.
Your user research will show you how best to group topics. For example, you may need to group them according to where users will get the answer. Is the information something they know well, like their date of birth, or will they have to go looking for it? It often helps to group contact details together and account details together.
Test your questions to understand what order to put them in
You need to understand which questions your users expect first and how they group them. One way to do this is with a card sorting exercise. Test the order again when you prototype your form.
For example, do users expect to give you personal details at the start or do they want to deal with the task first and give you personal details at the end?
Would you like to contribute to this guidance?
Please let us know how this has worked for you and, in particular, if you have research findings to share. This will help us improve it for everyone.
Before you start, you will need a GitHub account. It's an open forum where we collect feedback.
If you have any questions, you can message us on Slack. You will need a Slack account if you do not have one. Or you can contact us by email.
Updated: November 2019