Stepper & Wizard Patterns

When to Use

• Process requires 4+ inputs that can be logically grouped
• Order matters (setup before configuration)
• Users need context about progress and remaining effort

Design Rules

1. Show step count and current position (Step 2 of 4)
2. Step labels are descriptive ("Payment Details" not "Step 2")
3. Allow going back without losing data
4. Validate each step before allowing forward progress
5. Save progress so users can return later
6. Summary/review step before final submission for important flows