Designing for alignment at scale
The design system was conceived as a shared language rather than a prescriptive rulebook. Instead of enforcing uniformity, it focused on defining stable foundations and clear boundaries between what needed to be consistent and what could remain flexible. By making decisions explicit, teams could reason about interfaces using the same principles, even when working on different products and timelines. The emphasis was on enabling collaboration, reducing friction, and supporting long-term coherence across the ecosystem.
What changed
The design system enabled teams to work from a shared foundation, reducing duplication and inconsistencies across products and services.
The digital experience became more consistent and readable, while teams could iterate faster without having to renegotiate fundamental decisions for each new project. The ecosystem's complexity remained, but became manageable.
Reflection
In omnichannel contexts, a design system doesn't standardize the experience, it makes it recognizable, even when the context changes. When decisions are shared, consistency becomes a consequence, not a goal to chase.
This project demonstrates my approach to design systems in complex, service-oriented ecosystems, where design value emerges in the ability to connect products, teams, and touchpoints into a unified, continuous experience.