Qualcomm
Qualcomm
Qualcomm

At a glance
ROLE
Senior UX designer
Senior UX designer
COLLABORATORS
Lead, product designers, and engineers
Lead, product designers, and engineers
SCOPE
Four connected libraries
Four connected libraries
Focus
Architecture, scalability & adoption
Architecture, scalability & adoption
SUMMARY
Building a scalable component and pattern ecosystem that brings consistency to marketing workflows without limiting creative flexibility.
At Qualcomm, I helped connect shared design foundations with the marketing team's specific needs. I contributed to foundational and base component libraries, then owned the development of marketing components and reusable page patterns.
The result was a more cohesive design system that made it easier for designers to build landing pages, reuse existing patterns, and gradually move away from fragmented libraries.
Building a scalable component and pattern ecosystem that brings consistency to marketing workflows without limiting creative flexibility.
At Qualcomm, I helped connect shared design foundations with the marketing team's specific needs. I contributed to foundational and base component libraries, then owned the development of marketing components and reusable page patterns.
The result was a more cohesive design system that made it easier for designers to build landing pages, reuse existing patterns, and gradually move away from fragmented libraries.

The challenge
Over time, the marketing team had accumulated several design libraries with duplicated components, inconsistent properties, and patterns built for one-off use cases.
Designers had established workflows and preferred components, making the transition to a new system as much an adoption challenge as a technical one.
Over time, the marketing team had accumulated several design libraries with duplicated components, inconsistent properties, and patterns built for one-off use cases.
Designers had established workflows and preferred components, making the transition to a new system as much an adoption challenge as a technical one.

The System
Rather than creating another standalone library, we organized the system into four interconnected layers.
Each layer builds on the previous one, allowing teams to share consistent foundations while supporting specialized workflows.
Rather than creating another standalone library, we organized the system into four interconnected layers.
Each layer builds on the previous one, allowing teams to share consistent foundations while supporting specialized workflows.

Building for Flexibility


I built the Marketing Component library from the ground up, applying consistent naming conventions, component properties, variants, and responsive behavior.
The goal was to give designers the flexibility to customize content without detaching components or compromising their structure.
I built the Marketing Component library from the ground up, applying consistent naming conventions, component properties, variants, and responsive behavior.
The goal was to give designers the flexibility to customize content without detaching components or compromising their structure.
From Components
to Pages

I extended the system into a Marketing Pattern library, combining components into reusable modules and landing page templates.
Instead of assembling every page section from scratch, designers could start with structured patterns and adapt them to their content.
I extended the system into a Marketing Pattern library, combining components into reusable modules and landing page templates.
Instead of assembling every page section from scratch, designers could start with structured patterns and adapt them to their content.
Driving Adoption
Building the libraries was only part of the challenge. Designers needed a reason to change how they worked.
I used the new components in real landing page projects, shared regular library updates, and created a visual sticker sheet to make the system easier to explore.
Working directly with designers also helped me identify opportunities to simplify properties and improve usability.
Building the libraries was only part of the challenge. Designers needed a reason to change how they worked.
I used the new components in real landing page projects, shared regular library updates, and created a visual sticker sheet to make the system easier to explore.
Working directly with designers also helped me identify opportunities to simplify properties and improve usability.


The Outcome

The team was using the new libraries approximately 70% of the time toward the end of my involvement.
The team was using the new libraries approximately 70% of the time toward the end of my involvement.

Shared components, reusable marketing patterns, and a more consistent way to build landing pages.
Shared components, reusable marketing patterns, and a more consistent way to build landing pages.
The Takeaway
A successful design system isn't measured by how many components it contains, but by how effectively people can use them.
This project reinforced that thoughtful architecture and adoption go hand in hand. Building the system was the technical challenge. Making it useful enough for designers to embrace was the real design challenge.
A successful design system isn't measured by how many components it contains, but by how effectively people can use them.
This project reinforced that thoughtful architecture and adoption go hand in hand. Building the system was the technical challenge. Making it useful enough for designers to embrace was the real design challenge.
