Writing interfaces for moments of uncertainty

People need particularly clear language when something has failed, is still processing or requires a decision with consequences.

Say what happened

Use a specific description of the current state. If a file was not saved, say that directly. Avoid vague labels that ask the person to infer whether the action completed.

Explain the next useful action

Place recovery guidance near the affected control. State which information is retained and what the person needs to repeat. When the system cannot recover automatically, provide an honest route to support.

Test the uncomfortable states

Review errors, long waiting periods and missing information with the same care as the successful flow. A product’s voice should remain respectful when it cannot do what someone expected.

For example, a failed upload should identify the affected file and explain whether the person can retry it. Retain the other completed fields and offer a clear alternative if the file type or size cannot be accepted.