🎓 Build User-Friendly Modules

Use Multi-Input nodes to group related questions, such as demographic information like name, birthday, or job title. This helps users quickly review their responses and reduces input errors.

For long answer options (with more than 7 entries), consider using dropdown lists and place optional inputs at the bottom or use conditionality within Multi-Input nodes.

👎 not good	👍 good

• Phrase input prompts, if possible, as questions with question marks, e.g., What is your name? not just Name.
• Avoid abbreviations that can create misunderstandings.
• Use headlines to summarize question content briefly.
• When providing guidance or explanations, use info blocks at the end of questions. Do not title the info block with Info. Instead make the subject matter clear (e.g., Limitation of liability).
• Use active voice for conversational modules and keep answer options concise and easy to understand.

• Use placeholders to provide examples of answers. If requesting numeric input, use example values in placeholders (e.g., 50,000). You should not repeat the question in a placeholder text.
• Consider setting default value for options that are likely to be selected by most end users. Default values can be used for summary nodes, allowing end users to confirm or amend input without additional screens.

• For Single Select or Multiple Select questions, limit the number of answer options to 5-9, considering Miller's law, which states that the span of immediate memory and absolute judgment are both limited to around 7 (plus/minus 2) pieces of information.
• For longer lists, use dropdowns or horizontal layouts. Prioritize simplicity and ease of selection.

👎 not good	👍 good

• Use headline formatting for question descriptions, especially in Multi-Input fields with multiple questions on one page.
• Format comments or additional notes as italics.
• When using links, select descriptive words for the link text.

👎 not good	👍 good

Create a meaningful start or welcome page that sets expectations, describes module benefits, and motivates users to complete it. Include a title, introduction text, estimated completion time, and information on required documents.

The results page is the final impression for users.

• Use a headline to summarize the result briefly.
• Provide a solid explanation of why the result was achieved. Offer background information, reports, or next steps.
• Include contact details if necessary.
• A response summary listing questions and answers enhances transparency.
• Conclude with a clear message like Your answers have been saved.

👎 not good	👍 good

Test modules on mobile devices to ensure they are easy to use, as many users access applications from mobile phones.