A form should make the next step clear
By Gyata Tabiri · Revised November 2, 2026
Every form question asks someone to do a little work. Before adding another field, I want to know whether its answer is needed now or whether it belongs in the conversation that follows.
Distinguish an introduction from a brief
On this site, Contact now asks for a name, email, reason for writing, and message, alongside the existing spam check. A detailed Creative Request remains available. Someone sharing a role should not have to define a project budget and scope before making an introduction. That is a design choice, not yet a measured conversion result.
Keep instructions where they can be used
Persistent labels explain what each control is for. Required fields need a clear reason, and an example should help without replacing the label. If a question can reasonably produce “I do not know yet,” the form should not pretend a precise answer is necessary to begin.
Let the response describe the actual event
Server acceptance, owner notification, and a visitor’s copy are related but separate outcomes. If one succeeds and another fails, the confirmation should explain that difference. Claiming everything was received before the process establishes it gives the visitor the wrong basis for deciding whether to try again.
Make correction less expensive
If an answer is missing or sending fails, preserve appropriate input and explain the next step. Review the flow with keyboard use, enlargement, and relevant assistive technology as well as successful submission. The difficult state is often where the quality of the form becomes most visible.
A useful form respects both the information needed and the effort required to provide it. Its job is complete only when the person understands what happened next.
Read alongside: The promise in a submission control · The message after the interaction.
Reference: W3C forms tutorial.