More segments squeeze labels until they cannot be read
Aliases: label crush · too many segments · truncated segments
What it is
Segment width is an equal split of one track. Add segments and each share falls, until labels truncate, shrink, or become private abbreviations. When label crush hits, exclusion still works, but people can no longer tell from the words what each face is; they rely on memory or probe taps. More than about six two-character Chinese labels already collide on a phone width; long English words collide sooner. This is a geometry failure, not copy that was not clever enough.
Why it happens
Track width is fixed by the container; segment count is the divisor. When the quotient drops below type size × character count + padding, layout can only sacrifice type. Padding goes first, then tracking, then truncation. Truncation concentrates discriminability in the head of the word, so near-synonyms (“Completed / Closed”) become indistinguishable “C…”. Abbreviations that are not already conventional signs (D / W / M for day week month) turn reading into decoding.
Horizontal panning looks like a way to add segments, but panned-away segments no longer form one complete track with the visible ones; the sense of peers dies, and people do not know how many segments exist or which index they are on. That is no longer a segmented control; it is unmarked tab-scrolling.
Studying it
Increase segment count inside a fixed container width, log the steps from full label to truncation to abbreviation, and run a recognition task: after a brief presentation, pick which segment was lit.
Independent variables: segment count, container width, language (two-character Chinese / long English), whether panning is allowed. Dependent variables: recognition accuracy, confusions with a neighbour, how many people pan before discovering hidden segments.
Use real product labels, not “Segment one / Segment two.” Near-synonyms are what expose truncation damage.
Where it stops holding
Icon-plus-text can keep two or three segments alive on a narrow screen if the icons are already learned; six novel icons are no better than six truncated words. A large display pushes the threshold out, so the same component can work on desktop and fail on a phone — change to a select or tabs at the breakpoint rather than sharing one count. Three or four segments used daily can teach abbreviations; an occasional filter bar cannot. Numbering 1–8 avoids truncation but erases view names, unless the number is the dimension (a rating).
Applying it
- Lay real labels into the narrowest target width; if any segment ellipsizes or drops below readable size, cut segments or change control.
- When more faces are needed, use scrollable tabs, a select, or a list; do not treat in-segment panning as capacity.
- Allow abbreviations only for signs the domain already shares, and give the full name on first sight.
- How to check: capture the narrowest width, hide the content, and have someone read every segment. Unread or misread segments were killed by crush.