Destructive actions

Friction in the user interface is often regarded as something to avoid or resolve. However, it can be useful when preventing a user from completing a destructive action when the consequences may be unknown.

In cases where we are prioritizing error prevention, we can take steps to:

  • Assist users from accidentally clicking a destructive action.
  • Help users to understand what happens after they confirm their destructive action.
  • Provide alternative options to potentially resolve their problem without resorting to destructive action.

Severity guidelines

Depending on the severity of destructiveness, we can implement the following friction patterns.

High severity

If a destructive action is difficult to undo or data will be lost permanently, strongly consider implementing a modal to confirm the action or guide the user to an alternative route.

  • A modal used for confirming a destructive action should use the danger button variant to confirm the action.
  • Require input confirmation of the deleted object's name when the action removes additional resources within. For example, when deleting a project.
  • All caps text should not be used in the modal header or body, unless the all caps styling is typical in the context (for example, README).
  • Body content can use bold styling to draw attention to the consequences of the destructive action.
  • Avoid using alerts to emphasize the content inside a modal.
TODO:
Add an example of a high severity modal confirmation. Create an issue

Medium severity

Destructive actions can introduce annoyance to the user when performed unintentionally. Recovering from these actions are difficult and will, therefore, have an emotional impact on the user. Consider assisting the user with an additional step to prevent accidentally clicking this action. A real example would be to put this action within a dropdown requiring a minimum of two clicks.

Low severity

The destructive action can easily be undone and no actual data was lost. Consider adding no friction at all in order to streamline the interface, especially in places where the action needs to be performed in bulk. These kinds of destructive actions can be exempt of being elementary styled and can instead be neutral styled buttons.

References

Last updated at: