The expanded use of icons in macOS Tahoe menus prompted web designer Jim Nielsen to question whether interface teams are adding symbols because they improve comprehension or simply because a template provides room for them. His critique focused on inconsistent patterns in Apple's system menus and the cognitive cost of decoding decorative imagery.
Nielsen did not argue for removing all menu icons. Instead, he drew a distinction between symbols that communicate a result and those that merely sit beside an already clear label. In a Finder menu for arranging windows, he found the visual representations useful because their shapes immediately showed layouts such as top-left placement or quarters. Reading those arrangements in words would require users to imagine the result.
His criticism centered on menus where that benefit is unclear. In Safari, some commands carry icons while neighboring commands do not. The Settings item has a symbol, for example, while Privacy Report does not, even though Safari uses an icon for Privacy Report elsewhere in its interface. Some menu groups are indented because they contain symbols and others remain aligned with text. Toggle items can display both an icon and a check mark, adding another visual element and complicating alignment.
That mixture, Nielsen argued, makes the system's rule difficult to infer. A symbol can speed recognition when users already understand its meaning, but an unfamiliar drawing may require separate interpretation before the label is read. His suggested design posture is therefore conditional: start without an icon and add one only when the team can explain what practical assistance it provides in that specific context.
The essay contrasted Tahoe's menus with older Apple guidance. Nielsen cited versions of the company's human-interface guidelines from 1992, 2005 and 2020 that discussed a limited set of standard menu symbols and warned that arbitrary ones could introduce clutter or confusion. He viewed Tahoe's broader use of iconography as a departure from that earlier restraint. The comparison is his interpretation of the current design rather than an explanation from Apple.
Google Sheets served as another example of the icon-by-default approach. Its File, Edit, View and context menus place symbols beside each command, a pattern Nielsen described as extra noise. The concern is not confined to one operating system; it is about a design process that can turn filling a reserved icon column into a routine task instead of an evidence-based choice.
The debate illustrates a persistent tension in interface work. Consistency can make a product feel orderly, yet consistent decoration is not automatically consistent meaning. Nielsen's examples support a narrower standard: use visual language where it conveys spatial or functional information, while allowing text to stand alone when a symbol would duplicate it.
