commentary-dev Design Effective Forms
Start with the decision or data need. Remove any question whose answer will not change routing, action, analysis, or a defined record.
Design principles
- Ask one concept at a time in clear, neutral, concrete language.
- Make closed choices mutually exclusive and collectively useful; provide an honest unsure or other path when needed.
- Put easy, engaging questions first. Defer difficult, demographic, or sensitive questions unless they are required for eligibility or routing.
- Group related questions logically. Use visible progress for multi-step flows and avoid deep branching.
- Keep labels and instructions visible. Do not use placeholder text as the only label or constraint.
- Prevent errors where possible, accept reasonable input formats, and explain how to recover near the affected control.
- Design mobile-first with predictable controls, readable widths, restrained hierarchy, semantic color, and no decorative complexity that disrupts field order.
- Pretest the complete form in its intended delivery mode for both comprehension and interaction.
For question and flow details, read references/form-practice.md. For respondent-specific follow-ups, read references/adaptive-personalization.md. The industry basis is recorded in references/source-notes.md.