MockVisual
Published in

MockVisual

Designing Confirmation

Best practices and the future of confirmed action

The confirmation design pattern isn’t something to be taken lightly. If employed erroneously, or not at all, users may commit unintended havoc. This article shares guidelines and best practices for designing effective confirmations.

Confirmations ask a user to verify whether they want to proceed or cancel a requested action. Confirmations are often used for destructive actions, like deleting a photo album, or consequential actions, like publishing this article.

Medium presents a tool-tip for users to confirm their desire to publish an article.

Confirmations aren’t always needed, and can actually increase mistakes. If a user is bombarded with confirmation for every action, they will disregard it. Confirmations shouldn’t be used for actions that are easily reversed or inconsequential.

Good practice:

  1. Present the action as a question in the header

2. Explain the outcome of the action in the body

3. Restate the action in the confirmation button

Avoid:

  1. Ambiguous questions like “Are you sure?”
  2. Non-descriptive body copy
  3. Yes/No actions
  4. “Cancel” can cause confusion. When committing a destructive action, like discarding changes, users may mistake “cancel” for the intended action instead of canceling the confirmation dialog.

Confirmations can include multiple interactions to make the outcome explicit to the user. Examples include checking boxes that indicate the intention or entering a password.

Invision’s confirmation modal requires checking boxes that indicate what will happen when a user deletes a prototype.

Confirmations can be presented in a number of ways including inline, modal, and tool-tip. Feel free to download the sketch file below and use these designs in your next project.

Confirmation dialog presented in a modal, tool-tip, and inline design component. Download Sketch File

The future of confirmed action

In 2014, I wrote an article on building a better button. It was in response to the “Flat Design” trend. Buttons were looking less like buttons, and I worried that users would unintentionally invoke harmful actions. The idea was to create a button that required a more intensive interaction than a click or tap.

Now, we are on the verge of 2017. Virtual reality, augmented reality, wearables, and gesture/voice-based interfaces of all kinds are going mainstream. We are moving to a future where the dexterity and context of an interaction is vastly different. Easier. Does this change the way we think about invoking action?

How do you think confirmations will change? What new best practices will emerge?

Find me on Twitter, and Dribbble.

--

--

--

https://mockvisual.com/

Recommended from Medium

What is business design?

WordPress Website Development Services

HOW MICROSOFT TOOK A THOUSAND LIVES: ETHICAL OBLIGATIONS IN SOFTWARE UX/UI DESIGN

Introduction to Stairs

10 Mind-blowing Entryways By Top Interior Designers — TrendBook Trend Forecasting

Freebiesketch

freebiesketch recent resources

Complexity vs Complication

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Andrew Coyle

Andrew Coyle

Building @mockvisual (YC S19) • Formerly @Flexport @Google @Intuit • Interested in platforms

More from Medium

Theoretical base on coloristic for UI/UX designer

2022 Guide to Information Architecture in UX Design

What is Design Thinking & how is it applied?

What is Design Thinking & how is it applied?

The Optimal Way to Display Modals on Mobile Screens