The biggest effect you can on a form's effectiveness is to ask the right questions, and only the right questions. Every piece of information you ask for is another hurdle for your user to get over before they complete the process.

When designing a form, you can ensure you are gathering only pertinent information by always invoking the question protocol. The question protocol forces you — and your organisation — to ask yourselves why you are requesting a piece of information from a customer. Getting to the bottom of why you’re asking a question means determining precisely how you will be using the answer, if at all.

Each piece of information you ask for has two costs:

  • Firstly it is an impairment to accurate completion of the process;
  • Secondly there is a time and money cost of collecting, storing and processing any additional information, and handling situations where the information is false or inconsistent.

With this in mind, the question protocol asks the following of any information that you are asking:

  1. Why do you need this information?
  2. Who will use the information, and what decision will be made or action taken based on the information collected?
  3. How will you validate the information that is submitted?
  4. What happens if the submitted information is false or made up?
  5. What’s the impact of the information not being submitted?
  6. What happens if the information goes out of date?
  7. Can a customer update their submitted information? Should they be able to?
  8. Are you allowed (legally and ethically) to collect this information?
  9. How is it shared? With whom? What are the privacy implications?
  10. How securely does it need to be stored?

Asking those questions should lead you to answering the ultimate one: “Is the question really necessary?” In the long run following the question protocol can save money and improve conversions and process completion.

You can watch our other #TinyLesson videos here

Related thinking

  • Tiny Lesson

Designing a Utopian layout grid: working with fluid responsive values in a static design tool.

Read the story