Components

Patterns

Layouts

Segments

Tokens

Design
system

Designing systems that scale

Designing systems that scale

…and actually get used

…and actually get used

Designing and maintaining systems for real-world banking

I design and maintain core components within the enterprise-grade design system at Wells Fargo, ensuring they work reliably across real product scenarios. My work spans component redesigns, testing, and careful documentation, bridging the gap between system guidelines and actual usage. I focus on making components scalable, resilient, and intuitive for both designers and end users.

Redesigning outdated components

Redesigning outdated components

  • The previous design system took up about 10% of the app - not a good sign for any design system.

  • The previous design system took up about 10% of the app - not a good sign for any design system.

  • The recent transactions table is one of top 10% of pages in the app that get 95% footfall - everyone checks their transactions often. My goal was to make checking them as acessible as possible.

  • The recent transactions table is one of top 10% of pages in the app that get 95% footfall - everyone checks their transactions often. My goal was to make checking them as acessible as possible.

  • Through extensive competitor research, I introduced new features that successfully positioned Wells Fargo alongside modern fintechs, rather than just traditional banking competitors.

  • Through extensive competitor research, I introduced new features that successfully positioned Wells Fargo alongside modern fintechs, rather than just traditional banking competitors.

Testing

…and more testing

  • I believe a design system is only as good as its stability. To ensure our components were truly fault-tolerant, I stress-tested every new build by pushing variants to their limits.

  • This process involved analyzing the component build from the perspective of a final user, providing feedback, and requesting necessary changes.

  • Visual Quality Assurance (VQA) was also essential; a single pixel out of place can erode trust, so I took a detail obsessed approach to ensure flawless exectuion.

Documentation

  • Building a design system is easy; explaining it is the hard part. I took charge of documenting the "why" behind our component decisions, ensuring designers and developers had a clear source of truth.

  • I authored 9 out of 27 system guides, utilizing AI-assisted workflows to boost efficiency and keep our documentation library growing alongside our product.

  • I authored 11 out of 32 system guides, utilizing AI-assisted workflows to boost efficiency and keep our documentation library growing alongside our product.

Component trainings

  • Conducted trainings, assisted new component adoptions and answered any questions designers had.

Dark mode

  • I explored multiple design and color directions for a dark mode version of the Wells Fargo app, while staying true to the brand identity.

  • Experimented with color variations for UI elements and backgrounds, paying close attention to how minor adjustments impact the overall brand experience.

Maintenance and SME duties

  • A design system constantly evolves to support new features, developer upgrades, and changing business needs. Keeping the system up to date was a constant priority.

  • As an SME, I kept my "ears to the ground," acting as the go-to person for component queries, troubleshooting, and feature requests. It’s not just about building the system; it’s about supporting the people who use it every day.

Got a project in mind?

Book a meeting with me.

Calend.ly

© 2026 Roma Pandya. All rights reserved.

Linkedin

Behance

Contact

Got a project in mind?

Book a meeting with me.

Calend.ly

© 2026 Roma Pandya. All rights reserved.

Linkedin

Behance

Contact