Client
B2B platform development across multiple internal teams
Context & Challenge
Over time, B2B platform evolved into a fragmented ecosystem of semi-similar applications — each built by different teams, with only loosely aligned UI patterns and design decisions. A full redesign or top-down design system rollout wasn’t possible due to technical constraints and the varying maturity of legacy systems.
Yet, consistency and clarity were urgently needed — both for usability and to streamline design/development workflows.
My Role
I co-led this initiative alongside another designer. Together, we aimed to establish a shared design language that could align existing systems without requiring full redesigns.
Process
1. Auditing the Platform
We began by auditing all platform applications — mapping them out in physical workshops to find similarities, divergences, and repeating patterns.
2. Defining the Language
From our insights, we created a rulebook grounded in shared UI logic, not aesthetics. We validated these rules in mockups to ensure the language solved real problems before documenting it in:
- A basic Figma component library
- Shared design tokens and UI patterns
- Guidelines for reuse across scenarios
The focus wasn’t visual reinvention — it was clear hierarchy, minimal disruption, and compatibility with the current ecosystem.
3. Developer Enablement
We introduced the language to all development teams — explaining the „why” behind each decision. By aligning on rules that used existing elements, developers could implement updates faster, with confidence that their work was scalable and future-ready.
Impact & Ongoing Work
While still being progressively adopted, the design language has already delivered clear benefits:
- Faster solution design — fewer inconsistencies, less file chaos
- Lower dev cost — reusing known components across systems
- Solid foundation — enabling future improvements in accessibility and alignment with a company-wide code design system
This project stood out by emphasizing alignment over reinvention — a pragmatic approach that respected the complexity of enterprise systems while still driving long-term design maturity.