TECH Signal 477
Martin Kleppmann argues against Yes/No/Cancel dialog buttons due to ambiguity and user confusion
↗
Illustration only Photo by Dharaneeswaran R on Unsplash
Martin Kleppmann's usability blog argues that labeling dialog buttons Yes, No, and Cancel creates ambiguity because the meaning depends on the question's phrasing, forcing users to stop and think.
For engineers building software, ambiguous dialog buttons degrade the user experience and can lead to unintended data loss. The issue arises because these dialogs often conflate two separate questions, such as whether to save and whether to quit, into a single three-button choice. Designers must instead ensure the consequences of each button are immediately clear.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
Martin Kleppmann introduces his usability blog by criticizing the use of Yes, No, and Cancel button labels in software.
The ambiguity of these labels forces users to stop and think, especially when different dialogs phrase the underlying question differently.
The problem stems from asking two distinct questions simultaneously while only offering three possible actions.
THE CLUSTER