Forms & Multi-Step Wizards

Overview

Every field costs conversion; every ambiguity costs trust. A form is a conversation with one question at a time, not a database schema rendered to screen.

When to Use

• Any data-entry surface: signup, checkout, onboarding, settings, application forms, filters-as-forms
• Splitting a long form into a wizard, or deciding whether to
• Reviewing a form with drop-off, error-rate, or support-ticket problems
• NOT for: search boxes and single-input inline edits — no form chrome needed
• NOT for: command palettes and query builders — interaction patterns, not form patterns

The Proven Flow