Inventory
An audit of the patterns in use and a decision on which to keep.
An enterprise product grown by accumulation: twelve modules, three interface generations and no shared language between design and engineering.
Each team had built its own components: tables, filters and forms behaved differently depending on the screen.
The priority was not aesthetics but predictability: lowering the cost of every new feature.
An audit of the patterns in use and a decision on which to keep.
Tokens, grid and documented components, versioned as code.
Module-by-module migration, with hands-on team support.
interfaces covered by the design system
time to build a new screen
shared language across design and engineering