Turning a black-box design system into a consumable, scalable foundation.
- ROLE
- STAFF PRODUCT DESIGNER
- COMPANY
- Dell
- TIMELINE
- 2025 – 2026
- SCOPE
- Design tokens · System architecture · Enablement · Collaboration model
CONTEXT
Dell’s DDS served a huge ecosystem — but ran as a black box: contributing was hard, visibility low, and requests piled up with no clear path.
- DDS — a system of systems
- B2C · B2B · internal · global
- Ran as a black box
- Parallel component libraries
THE CHALLENGE
Leadership read it as “lack of governance.” The real blocker was architecture, ownership and the rollout path.
Misread as governance
The foundations were strong — the gap was architecture & ownership, not process.
Built for designers, not consumers
Token naming ignored front-end engineers — the real consumers — with no export pipeline.
Quietly forcing parallel rebuilds
The collaboration model pushed teams to rebuild the system themselves.
WHAT I DID
Investigation & alignment
Discovery across design, engineering & architecture — settled who consumes tokens (front-end first) and one decision path.
Token architecture + pipeline
A simplified Carbon-style hierarchy: core + semantic tokens, light & dark, exported as JSON and CSS.
Enablement + collaboration
From gatekeeping to enablement — workshops, work sessions and a branch-and-approval co-creation model.
01 · DESIGN LANGUAGE
Dell Design Language (DDL) gives structure and coherence to everything we build — from typography and photography to color and animation. Not just a set of rules, but our shared visual and behavioral DNA.
02 · FOUNDATIONS + CORE TOKENS
To create alignment at scale, DDL is structured in two layers. Foundations define our essence — how we sound, look and feel. Core Tokens translate that into actionable, scalable values that power every product experience.
03 · SINGLE SOURCE OF TRUTH
DDL is our singular source of design truth. Any new system, theme or UI variation aligns with it — not a restriction, but the enabler of interoperability, consistency and speed across a growing constellation of design instances.
04 · THE DDS CORE
To build a theme, teams align with DDL principles — adopting semantic tokens, supporting multiple modes (light / dark / high contrast), and defining clear access points. It sounds like a lot, but no one starts from scratch: that’s where the DDS Core comes in.
05 · A SYSTEM OF SYSTEMS
Themes orbit the DDL. Core DDS sits closest, enabling foundational modes — light, dark, high contrast, AI and more. From there, branded or product-specific DDSs (Alienware, Corporate, DSA…) orbit farther out, each free to spawn sub-themes of its own — a system of systems, all aligned to a single sun.
01 · DESIGN LANGUAGE
Dell Design Language (DDL) gives structure and coherence to everything we build — typography, photography, color, motion. Not a set of rules, but our shared visual DNA.
02 · FOUNDATIONS + CORE TOKENS
DDL is structured in two layers. Foundations define our essence; Core Tokens turn it into actionable, scalable values powering every product.
03 · SINGLE SOURCE OF TRUTH
DDL is our singular source of design truth. Any new theme aligns with it — the enabler of interoperability, consistency and speed.
04 · THE DDS CORE
To build a theme, teams align with DDL — adopting semantic tokens, supporting multiple modes, and defining clear access points. No one starts from scratch: that’s the DDS Core.
05 · A SYSTEM OF SYSTEMS
Themes orbit the DDL. Core DDS sits closest; branded DDSs (Alienware, Corporate, DSA…) orbit farther out — a system of systems, all aligned to one sun.
THE TOKEN CHAIN
How one design decision flows through the system — from a raw value nobody should touch, to a name a component actually uses.
VALUES
The raw ingredients
No meaning. No context.
CORE TOKEN
Raw values, organized
Simple meaning — but no clue where they’re used.
SEMANTIC TOKEN
Names humans understand
Point to core tokens, but add meaning — they tell you why the value exists.
COMPONENT TOKEN
Scoped to one component
Precise — but heavy to maintain. Many teams skip it.
OUTCOMES
Tokens went from a stalled initiative to a shippable foundation — live across dell.com.
Shipped & live
A consumable token foundation across all dell.com surfaces.
Reliable for engineering
Consumed straight from JSON/CSS plus documentation.
Less rework
Alignment cut rework and sped up component modernization.
WHERE TOKENS LIVE
Tokens are just data — stored in Figma, JSON and CSS. Collections group them by category, variables and modes resolve semantic to core, library binding turns them into element properties, and Dev Mode exposes the exact code.
WHAT I LEARNED
Systems must be co-created
A design system fails when it can’t be co-created.
Governance enables speed
It should enable progress, not block it.
Naming is a product decision
Optimize for the real consumer, not the author.
Broken collaboration → parallel rebuilds
And production pays the price.
Results
THEME MODES
DELL.COM SURFACES
DUAL PIPELINE
“A design system fails when it can’t be co-created.”