Design · 7 min read
Design systems for growing products: start small, stay consistent
A design system is not a giant Figma file. We explain how to build one incrementally with tokens, components and documentation that designers and developers both use.
Priya Nair · 6 October 2026
Why products drift
Every product that grows past a handful of screens starts to drift. Buttons come in four slightly different shades, spacing varies from page to page, and each new feature reinvents a modal. The result is slower development, harder onboarding for new team members and an interface that feels less trustworthy, which is especially costly in fintech and trading products.
A design system addresses this by giving designers and developers a shared set of decisions and building blocks. It does not need to be large to be useful.
Start with tokens
Design tokens are named values for the most basic decisions: colours, typography, spacing, radii, shadows and motion. Name them by purpose rather than appearance, for example color-text-muted or color-surface-raised rather than grey-500, so themes and dark mode can change values without renaming.
Define tokens once and use them in both Figma variables and code, typically as CSS custom properties or a Tailwind theme. When a token changes, it changes everywhere.
- Primitive tokens: the raw palette and scale values
- Semantic tokens: purpose-based aliases that components reference
- Component tokens only where a component genuinely needs its own override
Build components from real screens
Resist designing a library in the abstract. Audit existing screens, find the components used most often, such as buttons, inputs, selects, tables, cards and dialogs, and standardise those first. Each component should cover its real states: default, hover, focus, disabled, loading and error.
In code, build on accessible primitives such as Radix UI or React Aria rather than starting from scratch. Keyboard navigation, focus management and ARIA attributes are hard to get right, and inheriting correct behaviour saves a great deal of effort.
Accessibility is part of the system
When accessibility lives in the components, every screen benefits automatically. Check colour contrast against WCAG 2.2 AA when defining tokens, make focus states visible, ensure touch targets are large enough on mobile, and support reduced-motion preferences.
Document these decisions alongside the components so they survive team changes.
Documentation and governance
A component no one can find will be rebuilt. Keep a living reference, for example in Storybook, showing each component, its props, usage guidelines and do's and don'ts. Link it from the Figma library so designers and developers look at the same source.
Governance can be lightweight: a named owner, a simple process for proposing new components, and regular review of one-off patterns that keep appearing. The system should evolve with the product, not freeze it.