Confirmation copy must name the consequence and the object

What it is

Even a confirmation used in the right situation can still be empty. “Are you sure you want to delete?” never says which thing, or what remains true afterward. Specific consequence and object means a recognizable name in the copy, plus the result that will still hold when the action finishes: which document, which payment, who can see it, whether it can come back. The button label should be the action itself (Delete “Annual budget”), not OK. The dialog’s job is to put the world-that-will-happen in front of the eyes, not to collect another gesture of agreement.

Why it happens

When the dialog opens, working memory holds the intent of the click just made, not necessarily the object’s full identity—especially after a run of list actions, with the name on the previous screen. If the dialog only repeats the verb, people match intent to question, the match succeeds, and they press; the object was never checked. A concrete name forces recognition: is this the one I think it is. A consequence sentence forces prediction: no trash, 30 members will be notified, money leaves today. Recognition and prediction are the only cognitive work confirmation still has; strip them and the dialog is only a face for habituation to drive through. Vague copy also makes two acts with different consequences look the same, so habituation spreads across object boundaries.

Where it stops holding

When there are too many objects to list in a title (“delete 40 files”), pair the summary with an expandable roster that shows at least some names—not a number alone. A name that is an internal id, or too long to parse, is not a name; show the human title and leave the id for a detail. When the true consequence depends on the server and the client cannot know, an honest ceiling (“may not be recoverable”) beats fake precision, but the ceiling is not an excuse to fall back to “Are you sure?” In translation, button width will pressure the verb; wrap rather than drop the object.

Applying it

• Put the object’s display name in the title or body; label the button with action plus object, not OK / Cancel as the only words.
• State the consequence in the present: unrecoverable, who is notified, how money or permission changes. Do not write “this cannot be undone” without saying what cannot be undone.
• For bulk acts, give a count and a scrollable list; if the default selection is not what the user thinks, the copy must expose that.
• Verify by screenshotting the dialog, hiding the page behind it, and asking what will be deleted and what remains afterward. No name, or the wrong aftermath, means the copy is empty.

Related

• Within the group: E6.05.1 Confirmations work only for irreversible, high-consequence actions · E6.05.2 Frequent confirmations are clicked through automatically
• Adjacent: E1.06 Button labels · E4.05 Inline and bulk actions · E1.03 Destructive action buttons
• Search terms: confirmation copy · named object · consequence statement