Users need to know whether their actions worked. In this lesson, Carlos Sanabria explains how feedback around uploads, payments, saved changes and form errors contributes to trust in a product.
These interactions may be small compared with the core feature, but they help a person decide whether to continue, retry, wait or correct a mistake.
What you'll learn.
- Show the status of an action while the user waits.
- Confirm outcomes without leaving people to guess.
- Explain errors at the point where the user can act on them.
Make system status visible.
A file upload is an obvious example: after selecting a file, the user needs to understand whether the transfer started, whether it is progressing and whether it finished. Silence creates uncertainty.
The same principle applies to less visible work. If a product is saving changes in the background, communicate that state clearly. The person should not have to navigate away or repeat an action to discover whether their work was kept.
Confirm the outcome that matters.
A payment confirmation should answer the questions created by the action. Did it succeed? Where did it go? Does anything remain to be done? A visual response is useful when it communicates the actual state.
Carlos gives examples ranging from a completed task celebration to a successful transfer. The appropriate treatment depends on the context. A decorative animation cannot substitute for an accurate confirmation, and a simple message can be enough when it gives the user what they need.
Make errors actionable.
Feedback is also important when an action fails. A form can explain that an email address is invalid while the user is still in a position to correct it.
Review the moments where users are most likely to hesitate or repeat an action: submitting a form, saving work, paying, uploading or moving between steps. Describe what occurred and provide a practical next action. This helps the person recover without having to infer what the system is doing.
Review the complete workflow.
The recording uses the troubled HealthCare.gov launch as a cautionary example of users being unable to complete an important enrollment journey. It illustrates the stakes of an experience that fails at the task it exists to support.
A large launch failure cannot be explained by micro-interactions alone. For your own product, examine feedback alongside functionality, reliability and the complete workflow. Test whether a person can finish the task and understand the result, including when something goes wrong.
Trust grows when the product’s behavior is understandable. Give users clear progress, accurate outcomes and useful recovery steps so they can act with confidence.
