Friction, chosen.

Know what the pause protects.

A confirmation screen earns its place when it helps someone understand a consequence. Sending an application, sharing sensitive information, or deleting an important record may deserve a moment of review.

That doesn’t make every extra step helpful. Repeating an address the system already knows or making someone hunt for a cancel link adds work without improving the decision.

Start by naming the mistake you are trying to prevent. Then ask whether a review, a clear explanation, or a way to undo the action is the best response.

Replace “Are you sure?” with context.

A generic warning asks for certainty without offering information. A useful review identifies what is changing, who will see it, and whether it can be reversed.

The language should be calm and specific. The person should be able to return to editing without losing the work they have already done.

Choose one consequential action.

Walk through it from the person’s side of the screen. Find the moment they commit and check what they can reasonably know before that point.

W3C’s guidance for certain financial, legal, and data-changing submissions describes options such as reversal, checking, or confirmation. It is a useful starting point for thinking about consequences; the right interaction still depends on the task.