Brand Identity Design: From Strategy to Visual SystemColor, type and supporting visual systems · Lesson 7 of 18
Brand color systems and design tokens
Video lecture
Brand color systems and design tokens
The narrated lecture is in production
Every chapter is scripted and ready. Browse the chapters and read the full transcript now — the video will appear here when it’s published.
Chapters
Transcript of the narration, chapter by chapter.
0:00 Brand color systems
Think of a brand you can recognize from across a room, before you can read a single word. Often, it's the color. A particular red, a particular teal, a particular purple. That kind of recognition isn't luck. It comes from choosing a signature color carefully, defining it precisely for every medium, and using it consistently for years. In this lecture, you'll learn how a brand color system is structured, how to choose a signature color, how to specify colors for screens and print, how to build ramps and an accessible pairings matrix, and how design tokens carry the system from Figma into code. By the end, you'll build a color system that works on a phone, a box and a billboard.
0:53 Why a system
Why a system, not just a palette? Because a brand palette has to work everywhere, for everyone, in many hands. Screens, print, fabric, signage, partner materials, dark mode, and people with low vision. A mood board of pleasant colors can't do that. A system can. Think of a paint company's color card for a house. It doesn't just say blue. It gives the exact mix, where to use each shade, and which trims go with which walls. A brand color system does the same, so any designer, printer or developer can get it right without guessing.
1:35 Structure
Here's the structure. A primary or signature color: the recognizable brand color, usually one, sometimes two. Secondary colors: two to four, supporting variety in layouts, campaigns and illustrations. An accent: one, for calls to action and highlights. Neutrals: three to six, for text, backgrounds and borders. And functional colors: success, warning, error and info, for digital products. Here's the key idea. The signature color must appear consistently and prominently enough to become associated with the brand, while secondary colors add range without overpowering it. Signature, not wallpaper.
2:13 Choosing the signature
How do you choose the signature color? Five considerations. Differentiation: how does it compare with competitors on your landscape board? Personality fit: do its hue, saturation and value express the personality sliders? Practicality: can it be reproduced consistently on screens, in print, on fabric and on signs? Very vivid screen colors may be impossible to match in CMYK. Accessibility: can it carry text, or will it need a darker or lighter variant? And cultural context: are there associations in your key markets that help or hinder? Then specify it everywhere: hex, RGB, CMYK from a printer proof, a spot color if you use one, and its token name.
3:00 Ramps and pairings
Now ramps and pairings. For each main color, create a ramp, for example from fifty, the lightest, to nine hundred, the darkest. That gives designers light backgrounds and dark text versions that are still on brand. Perceptual color tools help the steps look evenly spaced. Then build an approved pairings matrix: every text color against every background, checked against WCAG two point two, with four point five to one for normal text and three to one for large text. Mark which pairs are approved. Designers then choose from approved pairs instead of testing each time, and failures stop creeping back.
3:43 Worked example 1: a yoga studio's lilac
Worked example one, simple. A yoga studio in London uses a soft lilac everywhere, including for text on white. It looks gentle, but body text fails contrast badly. The designer keeps lilac as the signature, because clients recognize it, and builds a ramp. Lilac one hundred becomes a background tint. Lilac five hundred stays for large shapes. And lilac eight hundred, much darker, becomes the brand text color on white, and it passes. The pairings matrix makes the rule clear: lilac five hundred never carries small text. The studio keeps its recognizable color and gains a readable website.
4:26 Worked example 2: a Dubai property creator
Worked example two, a business scenario with illustrative details. A property content creator in Dubai uses gold, black and white, just like every luxury competitor. Gold text on white fails contrast, and the screen gold prints muddy on brochures. The new system: a warm sand base, a deep teal signature that stands apart, and a restrained brass accent used only for large graphics or on dark backgrounds. For print, the brass gets a spot or metallic specification, proofed physically, because automatic conversion won't match. For digital, everything becomes semantic tokens with light and dark modes. The result feels premium, looks different from competitors, and works on screens, paper and signs.
5:14 Watch me do it: color tokens
Watch me do it. I'm setting up tokens in Figma. I create a primitives collection with my ramps: teal fifty to nine hundred, navy nine hundred, sand fifty and coral five hundred. Then a semantic collection with light and dark modes. Color text default points to navy nine hundred in light and a warm off-white in dark. Color background canvas points to sand fifty in light and navy nine hundred in dark. Color action primary points to coral five hundred in both. I apply only semantic variables to the templates. Then I export the tokens as JSON for our developer, who transforms them into CSS variables. The lesson shows both formats. One source of truth, from design to code.
6:06 Color in print
Let's talk about print, because this is where brand colors go wrong. Screens mix light, and print mixes ink, so some bright screen colors, especially vivid blues, greens and oranges, can't be matched in standard CMYK. Automatic conversions can be noticeably off. So proof physically. Ask your printer for a proof on the actual paper stock. For critical colors, consider a spot color system, like Pantone, and specify it in the guidelines. And remember materials. The same color looks different on coated paper, uncoated paper, fabric and acrylic signage. Add material-specific notes when a brand uses many surfaces.
6:49 Common mistakes
Common mistakes. Choosing colors because the founder likes them, not for differentiation or personality. Copying the category's color, so the brand disappears. Too many colors with no roles. Using the signature color for everything. Using brand colors as text without checking contrast. Trusting automatic CMYK conversions. Typing hex values by hand in every file. And forgetting dark mode. The fix is a system: roles, ramps, a pairings matrix, specs for every medium, and semantic tokens that designers and developers share.
7:24 Recap and try this now
Let's recap. A brand color system has roles: signature, secondary, accent, neutrals and functional. Choose the signature for differentiation, personality, practicality, accessibility and cultural fit, and specify it for every medium. Build ramps, an approved pairings matrix against WCAG two point two, and print specs proofed physically. Then carry it all into semantic design tokens with light and dark modes, shared between Figma and code. Try this now. Build a color system for a brand, with roles, a ramp for the signature color, a pairings matrix checked with a contrast tool, and at least six semantic tokens.
From favorite colors to a system
A brand palette is not a mood board of pleasant colors. It is a working system that must deliver recognition, hierarchy and accessibility across screens, print, merchandise and partner materials — and be easy for others to apply correctly.
Structure of a brand color system
| Role | Purpose | Typical count |
|---|---|---|
| Primary (signature) | The recognizable brand color | 1 (sometimes 2) |
| Secondary | Supports variety in layouts, campaigns, illustrations | 2–4 |
| Accent | Calls to action, highlights | 1 |
| Neutrals | Text, backgrounds, borders | 3–6 |
| Functional | Success, warning, error, info (for digital products) | 3–4 |
The signature color should be used consistently and prominently enough to become associated with the brand. Secondary colors add range but should not overpower it.
Choosing the signature color
Consider:
- Differentiation — how does it compare with competitors' colors (from your landscape board)?
- Personality fit — does its hue, saturation and value express the personality sliders?
- Practicality — can it be reproduced consistently on screens, in print, on fabric and signage? Very vivid screen colors may be impossible to match in CMYK.
- Accessibility — can it carry text, or will it need a darker/lighter variant?
- Cultural context — are there strong associations in your key markets that help or hinder?
Specifying colors for every medium
Each color should be defined in all the systems it will be used in:
Color: Signature Teal
HEX #0F766E
RGB 15 118 110
CMYK per printer proof (conversion is not exact — proof it)
Spot Pantone/other spot reference if used for print
Usage Headlines on light bg, key shapes, app icon background
Text White text passes AA on this color at normal sizes? verifyAlways check CMYK and spot matches with physical proofs; automatic conversions can be noticeably off, especially for bright blues, greens and oranges.
Tints, shades and ramps
Create a ramp for each main color — for example 50 to 900 — so designers have lighter backgrounds and darker text versions that are still "on brand". Many digital teams generate ramps with perceptual color tools so steps look evenly spaced. Mark which steps are approved for text on white and on dark backgrounds.
Accessibility built in
Include an approved pairings matrix in the system:
| Text / Background | White | Sand-50 | Teal-700 | Navy-900 |
|---|---|---|---|---|
| Navy-900 | ✓ AA | ✓ AA | ✗ | — |
| White | — | ✗ | ✓ AA | ✓ AA |
| Teal-700 | ✓ AA | ✓ AA | — | ✗ |
(Verify each pairing with a contrast checker; the table above is an illustration of the format.) Designers then choose from approved pairs rather than testing each time.
Design tokens
Design tokens are named, platform-agnostic values for design decisions — colors, type sizes, spacing, radii — used consistently across design tools and code. A simple structure:
Primitive tokens Semantic tokens
teal-700 = #0F766E → color.brand.primary = teal-700
navy-900 = #0B1B34 → color.text.default = navy-900
sand-50 = #FBF7F0 → color.bg.canvas = sand-50
coral-500 = #F26B4F → color.action.primary = coral-500Semantic names ("text default", "action primary") make it easy to update the system later, support dark mode, and help developers and designers speak the same language. Tools such as Figma support variables that map to tokens, and many code frameworks consume token files.
Dark mode and backgrounds
Plan how the palette behaves on dark backgrounds — for apps, video end cards and dark-mode social feeds. Dark mode is not a simple inversion: saturated colors can vibrate on dark backgrounds and may need adjusted variants.
Worked example: palette for a Dubai-based property content creator
- Signature: deep emerald (differentiates from competitors' gold and black).
- Secondary: warm sand and soft stone for backgrounds; a muted sky blue for charts.
- Accent: a brass-gold used only for calls to action and key figures.
- Neutrals: ink, charcoal, mid-gray, off-white.
- Tokens: color.brand.primary, color.action.primary, color.bg.canvas, color.text.muted.
- Pairings matrix: white on emerald ✓; brass on off-white ✗ for text (used only for shapes and buttons with ink text).
Common mistakes
- Too many "primary" colors competing.
- Only specifying HEX, causing inconsistent print and merchandise.
- No accessible text pairings, leading to low-contrast designs.
- Naming tokens by appearance only ("light-blue-2"), making future changes painful.
Hands-on: brand color tokens from Figma to code
- In Figma, create a Primitives collection (
teal/50…900,navy/900,sand/50,coral/500) and a Semantic collection with Light and Dark modes (color/text/default,color/bg/canvas,color/action/primary…) that reference primitives. - Apply only semantic variables in designs and templates.
- Export or sync tokens for developers. Many teams use a JSON format based on the W3C Design Tokens Community Group specification (check the group's site for its current status), via a plugin or Figma's variables features/API, then transform it for CSS, iOS and Android with a tool such as Style Dictionary.
{
"color": {
"teal": {
"700": { "$type": "color", "$value": "#0F766E" }
},
"text": {
"default": { "$type": "color", "$value": "{color.navy.900}" }
},
"action": {
"primary": { "$type": "color", "$value": "{color.coral.500}" }
}
}
}:root {
--color-teal-700: #0F766E;
--color-text-default: #0B1B34;
--color-action-primary: #F26B4F;
}
@media (prefers-color-scheme: dark) {
:root { --color-text-default: #F5F2EC; }
}(Hex values are this lesson's illustrative palette.)
Brand color spec template
COLOR: Signature Teal (primary)
HEX #0F766E · RGB 15 118 110 · CMYK: from printer proof · Spot: if used
Token: color.brand.primary → teal-700
Approved text pairings: white on teal-700 (verify ≥ 4.5:1); teal-700 on sand-50
Not for: small text on navy; large fills in print without a proof
Share of use: ~30% of a typical layout (signature, not wallpaper)Before/after: a Dubai property creator's palette
| Before | After | |
|---|---|---|
| Colors | Gold, black, white — like every luxury competitor | Warm sand base, deep teal signature, restrained brass accent |
| Accessibility | Gold text on white failed contrast | Pairings matrix; gold/brass used only for large graphics or on dark |
| Screen gold printed muddy | Spot/metallic spec for print, proofed physically | |
| Digital | Hex values typed by hand | Semantic tokens with light and dark modes |
Summary
Structure the palette by role, specify each color for every medium with physical proofs, build ramps, publish approved accessible pairings, and express decisions as semantic design tokens.
Key takeaways
- A brand color system assigns roles — signature, secondary, accent, neutrals, functional — rather than listing favorite colors.
- Choose the signature for differentiation, personality fit, reproducibility, accessibility and cultural context.
- Specify colors for every medium (hex, RGB, proofed CMYK, spot) and build ramps plus an approved WCAG 2.2 pairings matrix.
- Proof print colors physically; automatic CMYK conversions can be noticeably off.
- Carry the system into semantic design tokens with light/dark modes shared by Figma and code.
Check your understanding
Quick questions to lock in the lesson. They don’t count towards your certificate.
Put it into practice
Build a color system for a brand with roles, a ramp for the signature color, a pairings matrix checked with a contrast tool, and at least six semantic tokens.
Enrol for free to save your progress
Reading is always free. Enrol to keep your place, take the final assessment and earn a verifiable certificate.