I led the end-to-end creation of a mobile Design System from scratch for a large banking ecosystem. The system was built to support multiple products, teams, and platforms while ensuring consistency, accessibility, and scalability. Beyond design execution, I approached the Design System as a product driving adoption across teams, collaborating closely with developers, and continuously improving it based on real-world usage.

The primary goal was to reduce time-to-market for mobile products by standardizing design and development processes. The system was intended to speed up design and development, support rapid prototyping and hypothesis testing, and ensure a consistent experience across all mobile banking products. It also helped strengthen brand recognition and user trust.

A secondary goal was to build a scalable and flexible system that could support multiple teams while maintaining a unified user experience.

I worked as the end-to-end owner of the Design System, covering strategy, design, research, implementation support, and adoption.

I defined core product patterns based on existing banking products, designed the system architecture—including tokens, components, and theming—and built cross-platform libraries for iOS and Android. I also led accessibility efforts, including WCAG compliance and user research with visually impaired participants.

Beyond design, I created documentation and usage guidelines, established collaboration workflows with developers, validated the system with real product teams, and drove internal adoption among stakeholders.

I treated the Design System not simply as a component library, but as a product for designers and developers. I identified pain points in real workflows, iterated on the system based on feedback from product teams, and drove adoption across the organization by clearly communicating its value to stakeholders and project managers.

I developed a flexible token-based architecture that supported multiple products and themes from a single foundation. The system used a clear token structure across Text, Elements, and Background, enabling light and dark themes while maintaining consistency across products.

This approach reduced dark theme implementation time by approximately 90% and allowed teams to create product-specific themes without compromising system consistency.

I built a modular and scalable cross-platform component system for iOS and Android, with separate libraries supporting platform-specific behaviors and native UX patterns. An atomic structure of atoms, molecules, and patterns made the system easier to scale, maintain, and evolve, while fully variant-driven components provided greater flexibility and speed.
This enabled product teams to work faster without recreating components, maintain platform-native experiences, and reduce inconsistencies between design and implementation.

Before defining the system, I conducted a benchmark analysis of 10+ existing banking apps and design systems to understand recurring UX patterns, platform differences, and product constraints.

This research helped me identify shared patterns across products, reduce unnecessary inconsistencies, and design a system that could support migration without creating additional complexity for existing teams. It also ensured that the Design System was grounded in real product needs rather than abstract standards.

I treated accessibility as a core pillar of the Design System, not an afterthought. I applied WCAG contrast standards, developed color-safe palettes for users with color vision deficiencies, defined rules to prevent incorrect color usage, and built support for dynamic typography and screen readers.

I also collaborated with UX researchers and participated in interviews with visually impaired users, translating real accessibility needs directly into design decisions and system guidelines.

A key part of the project was ensuring that the Design System was not only built, but successfully adopted across the organization.

I worked cross-functionally with designers, developers, and product stakeholders to align design and implementation. I defined a development-compatible token structure, reduced ambiguity in handoff, and helped ensure consistent behavior between design and code. This made delivery faster, more predictable, and easier to scale across teams.

At the same time, I actively drove internal adoption of the Design System as a product by presenting its value to product teams and stakeholders, collaborating closely with project managers, and supporting teams during onboarding and migration. I also demonstrated its impact through time and cost savings.

This helped establish the Design System as a core internal product used across teams rather than an isolated design initiative.

I established a scalable governance model for maintaining and evolving the Design System, including clear processes for component requests, validation, updates, and collaboration between the Design System and product teams.

This helped keep the system relevant, lightweight, and scalable as new product needs emerged.