skip to content

A retail bank's brand team insists its exact teal sit at the middle step of the palette ramp, but the ramp looks uneven; how do you build consistent brand and extended palettes?

level: seniorimportance: should knowfreq 38%

answer

  1. brand value is not always mid-ramp
  2. match the step by lightness
  3. shared targets for every hue
  4. extended hues as a family
  5. screen value versus print value

basics

~20 s

Put the exact brand teal at the step whose shared lightness target it matches, not automatically the middle, and build all other steps and extended hues from the same targets, so the brand color stays exact and the palette even.

solid answer

~50 s

The unevenness comes from forcing a color into a position its lightness does not fit: if the brand teal is fairly dark, calling it the middle step squeezes the dark half of the ramp and stretches the light half. I would measure the teal's lightness in a perceptual space, place it at the step with the nearest shared **lightness target** - perhaps step six or seven - and keep that value exact, nudging only that step's target if needed. The **extended palette** - reds, ambers, greens and other supporting hues - is then generated from the same lightness targets and chroma rules, so step six of every hue has similar lightness and the palette reads as one family. I would also check that the brand's print-defined teal has a proper screen value. The brand team keeps its exact color; the system keeps an even, predictable palette.

go deeper

for a junior

Recall the difference between brand hues, which carry identity, and extended hues, which serve interface needs, and that both are delivered as ramps.

for a middle

Explain why a brand value belongs at the step matching its lightness, and why every hue should share the same lightness targets.

for a senior

Resolve the brand-team conflict with a measurement, build extended hues with per-hue chroma, hue shifts and gamut mapping, and confirm the brand color's screen value.

for a principal

Decide how large the extended palette should be and who may add hues, balancing brand distinctiveness, product needs and the cost of every ramp across modes and platforms.

## Brand palette and extended palette A design system's color palette usually has two layers of raw material: | Layer | What it holds | Who cares most | |---|---|---| | **Brand palette** | The hues that carry identity - for a retail bank, its teal and perhaps a deep navy - plus the neutrals | Brand and marketing teams | | **Extended palette** | Supporting hues the interface needs - reds, ambers, greens, blues, purples - each as a full ramp | Product designers and engineers | The extended palette is still raw material. Which red becomes the error color, which green means success and which hues feed charts are decided afterwards in functional roles and data-visualisation palettes. The job here is to make the ramps themselves consistent. ## Why forcing the brand value to the middle breaks the ramp A ramp's steps follow **lightness targets** - for example ten values from nearly white to nearly black. A brand color has a fixed lightness of its own. If the teal is fairly dark but is declared to be the middle step: - the steps between it and black must be squeezed into a short lightness range, so the dark steps look almost identical; - the steps between it and white must be stretched, so the light steps jump; - the teal ramp no longer lines up with the other hues, so step five of teal is much darker than step five of red. The brand team's goal - the exact teal, used as-is - is legitimate. The mistake is equating 'exact' with 'middle'. ## The fix: anchor by lightness 1. **Measure** the brand teal's lightness in a perceptual space such as OKLCH. 2. **Find the nearest step** among the shared lightness targets - perhaps step six or seven, not five. 3. **Anchor** the exact brand value at that step, nudging only that one step's target if it differs slightly. 4. **Generate** the remaining teal steps from the shared targets, with chroma tapering toward the ends. 5. **Show the result** to the brand team in real screens: the exact teal where it matters, with a smooth ramp around it. This turns an argument about aesthetics into a measurement both sides can check. ## Building the extended hues as a family The same shared targets are used for every extended hue, so step numbers mean comparable lightness across the whole palette. A few extra adjustments are common practice: - **Chroma per hue.** Each hue's peak chroma is set so the extended hues feel balanced with each other; some systems keep them a little below the brand hue so the brand still stands out. - **Hue shifting.** Some families look wrong at the extremes if the hue angle is held fixed. Darkening a yellow at a fixed hue tends to read as olive or muddy brown, so dark yellow steps are often shifted toward orange; light blues are sometimes nudged slightly toward cyan. - **Gamut mapping.** Each step's chroma is reduced where the display cannot show it, which affects bright yellows and deep blues most. - **Coverage, not abundance.** Add an extended hue only when the interface has a need for it; each hue is one more ramp to maintain across modes and platforms. ## Screen value versus print value Many brand colors were first defined for print. A print-defined teal may have no exact equivalent on screens, or its published screen conversion may look duller than the printed swatch. A senior answer checks this early: - agree an official **screen value** for the brand color with the brand team; - if the product targets wide-gamut displays, decide whether a more vivid variant is used there with a standard fallback elsewhere; - document which value is canonical for which medium, so the ramp is anchored to the right one. This applies equally to a native mobile app and a web product: both render in screen color spaces and both need the screen value, not the ink recipe. ## What to deliver - A brand ramp anchored at the brand value's true lightness step. - Extended ramps built on the same lightness targets and chroma rules. - A short record of the decisions: targets, per-hue chroma, hue shifts, and which step holds each brand value. - A regeneration process, so adding a hue or adjusting a target rebuilds all ramps consistently instead of being done by hand.

  • The brand team rejects any step labelled six for its hero color and insists on five; what can you offer?
    Separate the label from the lightness. The name of a step is a token-naming decision; the lightness each step holds is the palette decision. You can offer an alias or name the brand value however the brand prefers, while the ramp's actual lightness targets stay intact. What should not change is the evenness of the ramp to satisfy a label.
  • How do you decide whether a new extended hue, such as a purple, belongs in the palette?
    Ask what interface need it serves that existing hues cannot: a distinct product area, a data series, an illustration need. If the need is real, build it on the shared targets and chroma rules like every other hue. If it is decoration for one screen, a local choice or an existing hue is cheaper than a ramp the system must maintain everywhere.

saying these in an interview costs you the question

  • The brand color must always be the middle step of its ramp
  • Extended hues need no relation to the brand ramp's lightness steps
  • Holding a fixed hue angle keeps dark yellows looking yellow
  • A print brand color can be used on screens without checking
  • More extended hues always make the palette more useful