Which of the following best describes design tokens in a design system?
AReusable UI components like buttons and cards
BThe raw named values — colors, spacing units, type scales — that components are built from
CDocumentation pages explaining when to use each component
DA version-controlled code repository of shared assets
Design tokens are the foundational layer: the named raw values (e.g., color-primary: #0057B8, spacing-md: 16px) that feed into components. Components are built from tokens, not the other way around. Conflating tokens with components is a common source of poorly structured systems.
Question 2 True / False
A well-maintained component library is sufficient to constitute a complete design system.
TTrue
FFalse
Answer: False
A component library is one artifact within a design system, but a full system also includes design tokens, documentation of usage rules, governance processes, and often accessibility and interaction guidelines. Without the surrounding structure, a component library alone cannot ensure consistent product decisions over time.
Question 3 Short Answer
Why would a two-person startup benefit from a design system, even early in its product lifecycle?
Think about your answer, then reveal below.
Model answer: Even with a small team, inconsistent decisions accumulate quickly — different button styles, ad-hoc spacing, varied type treatment. Establishing tokens and component patterns early prevents technical and visual debt from compounding, and makes onboarding new contributors faster.
The common misconception is that design systems are only for large organizations. In reality, the cost of inconsistency grows with every new screen built. A lightweight system (even just a token set and three core components) saves more time than it costs within weeks of adoption.