Confirmation messages
Confirmation messages are feedback elements that verify user actions, especially for important or irreversible operations. They provide users with a sense of control and help prevent unintended actions.
Benefits and Use Cases
Prevents errors. Confirmation messages can stop users from accidentally performing unwanted actions.
Example
In Cluster, show a confirmation dialog when a user attempts to remove a team member from a project, ensuring they didn't click the button by mistake.
Provides reassurance. Confirmations reassure users that their intended actions have been completed successfully.
Example
Display a confirmation message in Cluster after a user successfully shares a content piece, confirming who it was shared with.
Improves user confidence. Clear confirmations help users feel more in control and confident when using the interface.
Example
Show a confirmation message in Cluster when a user changes their account settings, reassuring them that their preferences have been updated.
Clarifies consequences. For complex actions, confirmation messages can explain the results of the action before it's completed.
Example
When a Cluster user tries to merge two content clusters, show a confirmation message explaining what will happen to the content and permissions of both clusters.
Psychological Principles Supported
Uncertainty Reduction Theory. Confirmation messages reduce uncertainty about the system's state and the results of user actions.
Example
After scheduling a post in Cluster, show a confirmation message with the exact date and time it will be published, reducing uncertainty about the scheduling process.
Feedback Loop. Confirmations create a clear feedback loop, helping users understand the direct results of their actions.
Example
In Cluster's AI-assisted writing feature, show a confirmation message each time the AI successfully applies a suggested edit, creating a clear feedback loop for the user.
Locus of Control. By giving users the chance to confirm or cancel actions, confirmation messages enhance their sense of control over the system.
Example
When applying bulk actions to multiple content pieces in Cluster, show a confirmation message allowing users to review and confirm the changes before they're applied.
Implementation Guidelines
DON'T
Overuse confirmation messages for trivial or easily reversible actions
Use technical jargon or vague language in confirmation messages
Rely solely on confirmation messages to prevent errors (also use good design to prevent mistakes)
Make confirmation dialogs overly complex or hard to understand
Forget to provide a clear way to dismiss or act on the confirmation message
DO
Use clear and specific language in confirmation messages
Provide options to confirm or cancel the action when appropriate
Position confirmation messages close to the triggering action
Use consistent styling for confirmation messages across your interface
Include relevant details in the confirmation (e.g., what was changed, who was affected)