DEPMatrix
Four products. Four visual languages. The same team shipping all of them.
- Client
- B2B software, four-product suiteWithheld by agreement
- Year
- 2024
- Role
- Design & engineering
- Type
- Systems
- Approach
- Design system · Web app · Documentation
Where it started
A B2B product that had become four products. Each had a different nav, a different table, a different idea of a button. Customers learned one, then got lost in the next. The team shipped faster than they could agree.
What was hard
A redesign of everything at once would have frozen the roadmap. We had to make a system the existing screens could join, not a new product they had to wait for.
What we built
A design system: type, color, components, and the patterns they actually repeat — tables, filters, empty states. Then we moved the four products onto it, one surface at a time. Documentation lives with the components, not in a slide.
What changed
New screens start from the system. The four products look like they belong to the same company. The backlog is features again, not “make this one match the other one.”
Scope
- Component and pattern library
- Type, color, and interaction rules
- Four products moved onto the system
- Documentation with the components
- Handover to their design and engineering teams