A design system is a shared library of design tokens — colour, typography, spacing, breakpoints — and the interface components built on them, documented so that several teams, markets or agencies produce work that holds together. It earns its keep once more than one team builds interfaces independently. For a single website, a well-structured component library inside that build covers the same ground without the governance overhead.
The industrial case is usually a group with country subsidiary sites, acquired brands still running their own properties, a distributor portal, a careers site and a product configurator, each built by a different supplier at a different time. The system is what stops a specification table, a datasheet download block or a certification badge being reinvented five times with five different behaviours.
The foundation layer holds tokens: colour roles, a type scale, spacing units, radii, breakpoints and motion values, expressed once so design tools and code consume them from the same source.
The component layer sits on top: buttons, form fields, cards, tables, navigation and the patterns specific to your business. Each carries its states, responsive behaviour, accessibility requirements and usage guidance, so a decision is taken once instead of being renegotiated on every page.
Beyond the generic interface parts, the ones that repay definition are the specification table with unit handling, the product card with its certification and availability markers, the datasheet and CAD download block, the faceted filter panel, the distributor locator result, the comparison view, and the RFQ form with its part-number picker.
Those are the elements a buyer meets repeatedly. Defining them once also settles their keyboard behaviour and contrast once, which is the part that drifts when every site solves it separately.
The token layer is what allows several brands to share one component set: structure and behaviour stay identical while colour, typography and spacing change through configuration. An acquired brand can retain its visual identity while running on components the group maintains centrally.
That is the main argument after a merger or a portfolio consolidation. See multi-brand consolidation for how the estate side of that is handled.
A single corporate site with one publishing team gets its coherence from a properly structured build. Adding a documented, versioned, separately governed system introduces process to a problem that does not have it.
It also fits badly where properties differ in substance rather than in styling: a marketing site, an authenticated portal and an ecommerce platform may share tokens usefully and share very few components. Take the tokens and leave the rest.
Systems fail through neglect rather than through design. Name a small group spanning brand, digital and engineering with authority to approve new components and retire old ones, agree how a market requests something the system lacks, and version the releases so a subsidiary knows what it is consuming.
Without that, teams build outside the system for speed and the library gradually becomes a record of an earlier state.
We work from the properties that exist rather than from a blank page: audit the interfaces in use, identify the repeated patterns, define the tokens against the brand guidelines, then build the components in code and in the design tool from that same token source.
Our design systems page sets out that process, and our UX and UI design page covers the interface work it supports.
A shared library of design tokens — colour, typography, spacing, breakpoints — and the interface components built on them, documented so several teams, markets or agencies produce work that holds together. It earns its keep once more than one team builds interfaces independently. A single website gets the same coherence from a well-structured component library inside its own build.
It implements them rather than replacing them. Brand guidelines are usually written for print and applied materials, and say little about focus states, breakpoints, error handling or how a specification table behaves on a phone. A design system turns those rules into working components, so each new page inherits the decisions instead of reopening them.
That is what the token layer exists for. Components stay structurally and behaviourally identical while colour, typography and spacing shift per brand through configuration. It is the usual argument after an acquisition, where a brand keeps its identity while running on components the group maintains centrally. See multi-brand consolidation for the estate side.
Usually not as a formal, versioned system. A properly structured build already yields a coherent component library for that site, and the governance a standalone system requires adds process without a second team to serve. The case changes once a second property, a portal or a country subsidiary site enters the picture.
The specification table with unit handling, the product card with its certification and availability markers, the datasheet and CAD download block, the faceted filter panel, the distributor locator result, the comparison view, and the RFQ form with its part-number picker. Those are the elements buyers meet repeatedly, and where inconsistency costs the most.
A small named group spanning brand, digital and engineering, with authority to approve new components and retire old ones, plus an agreed route for a market to request something the system lacks. Version the releases so subsidiaries know what they are consuming. Left unowned, teams build around the system for speed and it becomes a record of an earlier state.
Tell us how many teams and properties build independently and we will set out what a system would cover and what it would cost to run.