The London Underground map established the core vocabulary of transit color coding in 1931: each line gets a distinct color, colors are used only to mean 'this is that line', and no color has a secondary meaning in the system. Harry Beck's insight was that map users need to answer exactly one question ('which line and which direction?') and that color should encode exactly that answer — nothing else. This single-meaning rule is violated constantly in digital design, where the same blue is used for links, information states, the primary brand color, and navigation highlights simultaneously. When color has multiple meanings in the same space, users cannot rely on it for navigation.
In healthcare wayfinding research, the most effective color coding systems use large distinct zones (whole wings or floors), limit zone colors to 6-8 maximum, and pair color coding with non-color redundancy (floor numbers, symbols, text direction). The redundancy requirement is critical: approximately 8% of the male population has some form of color vision deficiency. A wayfinding system that requires accurate color discrimination to navigate fails a significant portion of users. Zone color should confirm a direction, not be the primary navigational cue.
Digital product navigation benefits directly from wayfinding principles. Section color coding works when: (a) the section is visually large enough for the color to read clearly on the primary navigation element, (b) the section color is not reused in any other meaning in the same interface, (c) no more than 5-7 distinct section colors are used in the same navigation context. Multi-product suites (Google, Microsoft, Atlassian) use this pattern — each product has a distinct color that appears in the nav chrome, favicon, and document headers. The color means 'you are in this product' and nothing else.