Component Design for Design Systems
Component design is the work of specifying reusable interface parts, from core components such as buttons, inputs and modals to composed patterns such as forms, navigation and empty states. Each component needs defined anatomy, variants, states, behaviour and rules for when to use it, so teams build interfaces without reinventing pieces.
Stage: Components · Part of the Design System roadmap · Last reviewed 19 November 2026
What to learn in Component Design
- Define the anatomy, variants and states of a button component
- Specify hover, focus, disabled, loading and error states
- Decide which props a component exposes and which it hides
- Compose atoms into patterns such as a search form
- Write usage guidance covering when not to use a component
- Design for content that is longer or shorter than expected
Component Design interview questions
How do you decide whether something should become a component?
Look for patterns that appear in several places with the same purpose and behaviour. A component earns its place when reuse saves effort and consistency matters. Avoid promoting one-off layouts, which add maintenance without enough reuse.
What is the difference between a variant and a separate component?
A variant is a controlled variation of the same component, such as primary and secondary buttons that share structure and behaviour. A separate component is warranted when the structure or behaviour differs enough that one API would become confusing.
Where Component Design fits in the Design System roadmap
Component Design belongs to the Components stage (intermediate level), which takes about 14 hours. Build the library.
Other units in this stage
Back to the full Design System roadmap