Heuristic Traps
Oversimplifying Dropdown Labels
Let's take these three examples of a drop down menu, when paired with a control label.
The following advice assumes you do have control labels. If there’s no label because the context is crystal-clear — or if the menu items are unambiguous and specific to this interface — you can safely ignore what follows.
Option 3 is a classic case of over simplification.
Users often scan interface controls vertically — looking down the list of values — rather than reading a label, then the dropdown, then the next label, and so on. If someone scans this list and lands on a value like “Width”, it’s unclear what that refers to without looking left to the label. This forces users to bounce their attention between the dropdown and its label to make sense of the context.
This slows users down, especially:
- For beginners
- In high-cognitive-load interfaces
- When using software in a second language
With dropdowns, there’s an easy fix: repeat the context inside the options themselves.
This repetition improves:
- Clarity (the meaning is embedded in the item itself)
- Recognition (repeated terms reinforce memory)
- Scanning efficiency (especially when repeated words align vertically)
But repetition should be strategic. Option 1 is overly verbose and redundant. Option 3 is too minimal. That makes Option 2 the sweet spot — repeating only the necessary words to maintain clarity without noise.
🏆 With a label: Option 2 is best
🚫 Without a label: Option 1 is needed