Choosing the Right Feedback: Indicators, Validations, and Notifications Explained

State feedback is essential for any system’s success, and knowing when to use the three common communication methods—indicators, validations, and notifications—helps keep users informed.

Indicators

Indicators highlight a page element (content or UI component) to draw attention to something that has changed. They are visual cues that do not require user action.

Often implemented with icons that are easy to recognize.

Typographic changes such as bolding unread emails or coloring stock symbols.

Size enlargement or animation (e.g., vibration) can also serve as indicators.

Figure 1: Yelp uses a green label in search results to indicate a special deal in the tea market.

Indicator characteristics:

Context‑related: placed close to the associated element.

Conditional: shown only under specific conditions (e.g., stock price up or down).

Passive: does not require the user to take action.

When deciding to use an indicator, consider the importance of the information, its frequency, whether users want to see it, and the impact of omitting it.

Validations

Validation messages are error information related to user input. They tell users that data is incomplete or incorrect and guide them to fix it.

Figure 3: A complex validation message on cobragolf.com; a clearer message would be “Enter a valid email address.”

Validation characteristics:

The user must act to clear the validation.

The information is context‑specific, tied to the problematic input field.

Messages should be explicit and suggest a solution (e.g., “Please enter your street address”).

Combining an icon indicator with a validation message can further clarify which input needs correction.

Figure 4: BestBuy.com provides a helpful validation message with an icon and color to attract attention.

Notifications

Notifications inform users about system events that may not be directly related to their current actions. They can be contextual (tied to a specific UI element) or global (covering the whole system).

Figure 5: Facebook shows a contextual notification that a new story has been added.

Notification characteristics:

Not triggered by direct user behavior.

Convey events that have significance for the user.

Two types of notifications:

Actionable notifications require user response (e.g., modal dialogs that must be dismissed).

Passive notifications are informational and do not require action (e.g., badge icons or brief non‑modal pop‑ups).

Figure 6: macOS uses a notification for a system update that requires user action.

Figure 7: Adobe Creative Cloud shows a non‑intrusive passive notification for an app update.

Figure 8: Uniqlo.com uses a passive notification to confirm an item added to the cart.

Designing notifications is challenging because they must provide enough context without interrupting the user’s current task.

Choosing the Correct Communication Method

Using the wrong method can harm user experience. For example, a green label indicator in Yelp’s search results conveys a relevant deal, whereas a generic notification about the same deal would be ignored or annoying.

Actionable notifications should be used sparingly and only when immediate user response is required; passive notifications are suitable for informational updates.

Conclusion

Remember the key differences:

Indicators provide additional information about dynamic content or UI elements and appear conditionally.

Validations are tied to user actions or input and require correction.

Notifications focus on system‑related events, either requiring action or being purely informational.

Figure 9: Table summarizing the differences among indicators, validations, and notifications.

Understanding when and how to use these feedback tools ensures consistent communication with users.