Product design leader with 20+ years shaping digital products and building the systems and teams that help great experiences scale. Five design systems, four from concept to deployment.
The Droplets Design System was started before I joined Informatica. It was past the launch stage, but it needed to be brought to maturity and evolved to serve a platform and a family of products.
I built the team, led the UX design system strategy, and drove multiple UX modernization initiatives that elevated the product family through the design system.
I built the team and led the design system strategy, first as Director of Product Visual Design at Informatica, and since March 2026, after the Salesforce acquisition, as Director of UI/UX for Design Systems.
I advocated for the master token system and master color palette, created opportunities for the creative technologist and lead visual designer to socialize both across UX leadership, and pushed the color palette until it met the standard the system needed.
I led the effort to establish an AI-ready foundation for consistent, reliable product experiences, and to integrate AI-powered tools into design system workflows to accelerate design work, improve outcomes, and scale innovation and customer insight.
We also enabled AI-supported prototyping, so teams can explore and validate product experiences earlier.
I led Everest, Schwab’s omnichannel design system, from competing initiatives to one system that 40+ teams build with.
In December 2019, our VP of Design gave us a UX design directive: create a design system to unify and accelerate the product design lifecycle. At that time, there were competing initiatives to create one.
Our engineering leadership had a vision of reducing tech debt through a shared source of code and modular development. Our Brand team had created its own design system, but it was Marketing-centric and lacked the product design perspective and accompanying research discipline required for contemporary software development.
The problem we set out to solve: how might we create design at scale to unify the branded experience across platforms, reduce technical debt, and accelerate the design and build process of our digital products to better serve our clients?
Design systems often start as a design team initiative, and that is how I had worked on previous ones. In this instance, we wanted a joint mission with our technology partners.
That created tension between design leadership’s goal of forward-looking design patterns and the technology team’s mission to reduce tech debt. After six months, I advocated for adding product leadership. A product leader could focus on cross-business priorities and balance our design and tech goals against the organization’s.
We also learned that for a design system to thrive, it needs to move from a project, something with a completion date, to a product, with an ongoing lifecycle, planned funding, staffing, and maintenance.
My role changed over time, but for the most part the dedicated design team reported to me. I made the creative direction decisions, advocated for a director-level product manager, and met with engineering, product, and design leadership on progress and communication. The design team worked with about 50 engineers, who reported into their own organization.
At the executive level, VP and up, we were aligned on the mission but not entirely on the outcomes or how to get there. It took a while to bring everyone around to a shared definition of success.
I invited peer design system leaders in to share how they had solved similar problems. That helped shift the mindset from rigid consistency to a looser form of cohesion, one that leaves room for experimentation and innovation.
Everest is an omnichannel system. Its foundational elements reflect our Brand team’s identity system as an intake, and provide universal foundations shared across responsive web, iOS, Android, voice, and emerging technology such as watch and auto interfaces. The system powers multiple platforms and connected experiences from one source of code and design.
To support that, we designed it with themes. Themes allow different expressions of the design system and give it a path to evolve: you can develop a future version in live code and refine it before pushing it live to the entire client base.
The Schwab Virtual Assistant team and the Schwab mobile teams both reported to me, and both pulled from the shared visual system and foundational tokens. We wanted to go a step further.
I asked my design manager on the virtual assistant to document conversational guidelines wherever he could identify a pattern in the assistant’s flow. For example, “Clean the screen” became a documented guideline. Eventually the content was written by a team of 22 content strategists, but the design decisions about the assistant’s behavior were documented the same way we documented the visual elements pulled from the design system.
Measuring the success of a design system is not as clear-cut as counting components. Through discussions with other leading companies and subject matter experts, we learned common ways to gauge support. These are the questions we ask when gathering adoption data:
In addition to leading the design system team, I led a parallel initiative, Modern Wealth Management, that created a vision of the future target state for the design system. It is covered in its own case study.
Read the Modern Wealth Management case study →The success of the Schwab mobile app taught me how important it is to build the foundations of the visual language into the token system early, if the goal is to scale. At Informatica, when our creative technologist raised this, I got behind his effort quickly and blocked off time for him to work on it.
Not everyone in UX leadership saw yet how central it would be to our future, so I advocated personally for the master token system and master color palette. I created opportunities for the creative technologist and the lead visual designer to socialize both, and I reviewed and pushed the color palette repeatedly until it met the standard I believed the system needed.
Much of our work is not released yet. More visual examples of publicly released content are available upon request.
A two-track approach to evolving a design system.
If you’re building a design system, how do you create a vision of its future while it is still a work in progress? You can build a contemporary design system and visualize a future idealized state for it at the same time.
In addition to leading the design system team, I led a parallel initiative that created a vision of the system’s future target state.
The system was designed to support themes, which allows different expressions of the design system. A future version can be developed in live code and refined before it is pushed live to the entire client base.
The new visual language and interaction patterns were grounded in the Brand tenets of the organization.
I brought Product, Technology, and Brand into one shared build, and out of it came the design system for Autodesk’s cloud products.
A360 was Autodesk’s flagship cloud-based product and the collaboration hub for the Autodesk 360 product line. It sat at the center of Autodesk’s move to the cloud, letting designers, architects, industrial designers, 3D animators, and anyone else working in 3D view all Autodesk file formats in one place and collaborate across a cross-functional team, with or without CAD software. It was also meant to become the basis of a design system for cloud and mobile products.
There was tension over who should drive that system. The creative directors for A360 (the flagship cloud product), AutoCAD (the big revenue generator), and Brand (the team that felt it owned the cohesive experience) each had a claim.
The problem we set out to solve: how do we create a design system for A360 that unifies our product family, incorporates the Brand language, supports design and development at scale, and accelerates product design across channels?
Instead of winning the argument, I invited the AutoCAD and Brand leaders into the work. We ran shared sessions of product mood boarding, ideation, and co-creation of design principles for the Jupiter Design System. Product and Engineering joined the problem framing and discovery, so the system became something we could all stand behind.
I served on the A360 leadership team alongside our Product partner, the Technology lead, UX (the Product creative director and the UX architect), the Brand creative director, and the AutoCAD product creative director.
I led a full visual redesign of the A360 product and platform. I recruited, managed, and directed the visual design team, and contributed as a principal visual designer until the team was fully staffed. For the Jupiter Design System, I provided creative direction and information architecture, and the UX visual design team produced the visual design.
I also acted as a thought partner with the UX architect and business partners on driving a cohesive product experience, and as a subject matter expert and player-coach designer on design systems.
For the 2014 release, I led the team to see its work as the product of collaboration with the rest of the visual design team and co-creation with our UX team. Letting go of the solo designer mindset, and seeing the work as both UX and UI, was important to using the strength of a cross-functional team.
I outlined and delivered a communication strategy to build awareness and support at every level of the organization, and presented the creative direction for A360 and the design system over multiple releases.
Jupiter grew out of the A360 work and became the system for Autodesk’s cloud products. It had its own documentation website, organized into an overview, the brand identity in product, style elements, a framework, patterns, motion and transitions, and components such as buttons, data tables, dialogs, form fields, menus, and progress indicators.
Metrics. User retention and monthly active users increased significantly. We measured net new users, daily users, and A/B tests through Optimizely.
More visual examples are available upon request.
At a late-stage startup, I set the design strategy for four products and then built the system myself.
Delphix is a DataOps company that lets companies make virtual, compressed copies of their databases in minutes, to accelerate development, testing, and innovation. When I was hired, it was a late-stage, pre-IPO startup growing fast, with only the bare bones of an in-house UX team.
I came over with two other senior UX leaders from Autodesk to establish the founding UX team, its culture, and its processes, and to modernize the product platform. The new Director of UX needed four things from me: a long-range strategy for building the product design team as the company grew, a modern visual design, a design strategy to unify the disparate product UIs, and the ability to do hands-on design work in the present.
The starting point: four separate products with completely different, very dated user interfaces.
The first goal was a roadmap to integrate the four products. As we learned more about our users and the platform’s potential, product strategy migrated to the cloud. That required a pivot in UX strategy, from unifying four on-premises apps to building one new, unified, cloud-based experience.
The pivot was an opportunity. Because we were building the experience fresh, we could make the design system coherent from the start and grow it with the platform, instead of retrofitting four legacy interfaces.
As a full-stack designer and experienced manager, I developed a roadmap for unifying the visual UI, created the design system and a pattern library, and contributed to interaction design and user testing as needed.
At a larger company, as creative director, I would have had a team of visual product designers start discovery from the brand identity system, move to mood boarding, and then explore. At Delphix, I was the only in-house visual designer, so I had to set the vision and the design roadmap and then execute it. The design comps, icon library, data visualization, and UI toolkit in this case study are my work.
To speed up development and free the team to focus on the future state of the Delphix Dynamic Data platform, I designed and documented a pattern library. I started with foundational component elements: form controls, UI controls, and basic components. I then set rules for building compound components, to handle more complex interactions.
I led collaborative design exercises with the UX team and development leads to decide on interaction patterns, which let us standardize behaviors across the platform.
The visual language for the new platform meant aligning with our partners in Brand, so there would be one Delphix experience across Product and Marketing. For any new visual design system, I start by understanding the brand and our Product partners’ business goals, and how the visual design can support and extend our UX principles.
I wireframed a responsive web app proof of concept for mobile: a filtered view of the current experience with limited functionality, working across mobile form factors, so customers could complete useful tasks that don’t need the full product UI.
From 2005 to 2012 at TIBCO, I provided creative direction across 70+ products, and worked on mobile apps including the Golden State Warriors app, a 2013 Webby Honoree.
I’m a product design leader with 20+ years of experience shaping digital products and building the systems and teams that help great experiences scale.
At Salesforce, I lead the Informatica product design system, creating an AI-ready foundation that helps teams deliver consistent, reliable experiences and build AI-supported prototypes. I shape the strategy and evolution of the design system, advancing AI-first design practices and creating the structured foundation teams need to use AI confidently and deliver cohesive product experiences at scale.
Throughout my career, I’ve led teams of product designers, UX leaders, and visual designers across web, mobile, tablet, and emerging experiences. I partner closely with Product, Engineering, Research, Content, and Brand to connect customer insight with product strategy and turn complex problems into thoughtful, cohesive experiences.
I care deeply about developing people, fostering strong cross-functional partnerships, and creating the conditions for teams to do meaningful work. I see design systems not just as libraries of components, but as strategic foundations for collaboration, product quality, and innovation at scale.

