Effort: Low
What to notice
Explain use and optionality where each piece of information is requested.
Where it fits
- Fits
- People completing applications or settings with unclear field purposes.
- Use it when
- When actual uses and storage can be explained and unnecessary fields removed.
- Avoid it when
- When explanations misstate retention or conceal required fields.
How to build it
- Check necessity and purpose for every field.
- Explain purpose, storage and optionality near the field.
- Verify that skipping optional fields still allows progress.
Measure
- Main metric
- Share of eligible users submitting necessary data with understood purpose
- Guardrail
- Unnecessary data collection and questions caused by purpose confusion
- How to measure
- Allocate comparison groups before exposure and use equal follow-up and eligibility. Track Share of eligible users submitting necessary data with understood purpose alongside Unnecessary data collection and questions caused by purpose confusion.
When it backfires
An explanation does not justify collecting unnecessary personal data.
Alternatives
Theory behind it
Psychological reactance
Freedom-threatening messages can prompt anger and counterargument.
Well supported
Recognition over recall
Make necessary options visible rather than requiring users to remember them.
Practitioner framework
Evidence limits: An editorial web application; conversion effects on this interface are unmeasured. This usability guideline does not recommend an unlimited list of choices. Check information overload as well as memory demands.