Building Consistency Across Applications
Worked with a team to design a scalable design system for a financial services firm, unifying siloed internal tools, accelerating product launches, and empowering non-designers to mock up ideas quickly.
Client: Financial Services Firm (NDA)
Role: UX/UI Designer
Tools: Figma, FigJam, Powerpoint, Storybook
Team: UX/UI Designer (Me), another UX/UI Designer, Developer, Engagement Lead, Stakeholders
DEFINING APPLICATION PATTERNS
The Problem
Siloed workflows: Internal apps were built independently with little cross-team communication, which led to disjointed experiences across the firm’s applications.
Inconsistent experiences: As a result, users encountered mismatched patterns and branding, leading to confusion and inefficiency.
Slow Rollouts: New apps were often rebuilt from scratch, delaying launches and increasing costs.
The Opportunity
Move from isolated design efforts to a single source of truth.
Empower teams to build confidently and consistently while bridging the gap between business, design, and development.
My Role
I co-led the project with another designer, participating in stakeholder alignment workshops and consulting on the system’s structure.
I built the component library in Figma, collaborated closely with development for alignment, QA-ed components in Storybook, and created documentation for users of all experience levels.
Approach
Built on trust from earlier work by auditing tools and interviewing teams.
Participated in workshops run by the engagement lead to align business, design, and development on shared goals.
Designed components 1 to 2 sprints ahead of development, refining based on feedback.
Delivered a scalable Figma design system and am actively collaborating with my team to integrate it into live projects.
Continuing work to align cross-LOB applications into a unified platform using our patterns and design system.
THE APPLICATION SHELL
Challenge
Some end users were business stakeholders, not just the product team, and needed to understand and use the design system. During stakeholder workshops, we discovered most of these clients weren’t comfortable using Figma. Forcing a full Figma takeover risked slowing adoption.
Meeting People Where They Are
So I pivoted. Instead of forcing Figma on users, I leaned into what the client already knew and trusted: Microsoft. I created a living “how-to” manual in PowerPoint, a tool they felt confident using, sharing, and updating.
It included visual examples, usage guidelines, and access instructions, making the system approachable, not overwhelming.
A MODULAR DESIGN SYSTEM
Delivered Solution
We designed a scalable component library that mapped 1:1 to the development kit, allowing designers and developers to work in sync.
The system established foundational dashboard patterns to support future growth.
Measuring Success
Faster Iteration: Redesigned an in-flight product in 3 weeks, without delaying development.
Design System Adoption: 6 internal apps wrapped in the new UI layer, speeding delivery and ensuring consistency.
Strategic Impact: Sparked leadership’s initiative to create a unified engagement dashboard across all lines of business.
What I Learned
Component Flexibility Matters
I learned how to build smarter, more flexible components. Building adaptable components required testing multiple approaches.
Insight
The best solution isn’t always flashy. Sometimes, it’s about meeting people where they are.