Brief
- Product
- Fast-growing startup (pick fintech, logistics, or edtech)
- Task
- Define foundational design system elements from scratch
- Output
- Tokens + core components documented in Figma
User & problem
Designers ship screens with one-off styles. Engineers copy-paste UI from old frames. New hires ask “which button is the real one?” Leadership wants consistency without freezing velocity.
Goals
- Foundations
- Color, type, spacing, radius documented
- Core UI
- Button, input, and one card/list pattern defined
- Handoff
- Engineers know where to look and what is out of scope for v1
Scope
In scope: foundations page, button (states), input (states), one content pattern, usage do/don’t.
Out of scope: multi-brand theming, full data viz library, code package.
Deliver
- Figma file with Foundations + Components pages
- Naming rules in one short write-up
- Defense: what you deferred to v2 and why
Defense
If a designer invents a new button tomorrow, how does your system stop that without blocking a ship date?