UX CASE STUDY
Completing an e-commerce UX refresh for a luxury handbag brand to boost online conversions and enhance customer satisfaction. Building new desktop and mobile features for Mulberry's accounts, checkout, PLP, and PDP pages.


Overview
Context
Mulberry England cultivates a brand identity steeped in British heritage and timeless luxury. This is evident not only through their website design aesthetic but also in their product offerings and messaging. Their website serve as an extension of the brand's emphasis on quality and craftsmanship, showcasing their expertise in leather goods with product stories.
My role
At UX Connections, I collaborated on a project with Stink Studios for Mulberry. As part of a 4+ person UX design team, we partnered closely with Mulberry's product stakeholders and Stink Studio's creative team. We followed an iterative design process, holding regular meetings with the client to address their UX needs.
Client goals
01
improving usability, accessibility, conversion (CRO) and the overall user experience.
02
Create an expansive component library that can be used by designers to create hi-fidelity wireframes for redesigns and additions to the website.
03
Set visual guidelines such as padding, spacing, colors, and font styles to increase the speed and scalability for future wireframe designs.
Challenges
01
Shifting mindsets can be tough. Balancing user needs and client preferences requires patience and consistent high-quality work. But, by building trust through strong relationships and repeated success, change becomes achievable.
Because of this, justifying design choices is central to my process.
02
Limited budgets and a lack of focus on UX often make user testing a challenge. To address this, we relied heavily on data provided by Mulberry to inform our design decisions.
Result
Over the course of a year, we delivered everything from sitemaps, user journeys, wireframes and prototypes, to UX strategy decks and component libraries.
All work on the website redesign was paused towards the end of 2023 as per the client's request.
A future-proof, extensive design system and component library providing a baseline for design production with 71 styles and over 1100 components.
Process
Establishing a foundation with research
The first part of my research process involved spending time exploring and learning from existing design systems. Although I have worked with design systems in the past, I won’t shy away from admitting that this was my first time leading the creation of one from scratch. I wanted to be certain I didn’t miss any steps.
I used a website called Design Systems for Figma that was shared with me by a coworker (thank you Lauren) to look through different examples in Figma. This heavily informed the way I dissected, organized, and documented the scalable elements of the brand.

Defining base tokens and styles
The other, much bulkier part of the research involved an extensive audit of Spectrum Enterprise’s website and existing design palettes. Establishing a baseline for tokens including color styles, text styles, and layout grids was essential before starting to build any components.
I was finding inconsistencies in color hex codes, spacing and padding, and text styles throughout the mobile and desktop wireframes. I went back and forth with the Senior Director of UX at RAPP to finalize styles for the Design System. After around two weeks, we finally had our base to work with.

Building a "drag and drop component library"
In order to successfully deliver a component library within the time and resource constraints, I implemented "drag and drop” components. This way of designing would allow us to remove the problems we were having with visual inconsistency and increase design speed.
I started by auditing each page to compile a list of modules that needed to be built. After knowing which page types needed to be built, I evaluated their anatomy to understand how to organize the final components. After completing the overall audit, I ended up with organized groups of component groups such as Heros, Banners, Cards, Tilesets, etc.
For each component group, I performed another layer of review to asses which groups needed additional variants. The result is an organized library of modules that can be used to create page templates with dynamic layouts for both desktop and mobile.
The result is an organized library of modules that can be used to create page templates with dynamic layouts for both desktop and mobile.
Documenting and testing the library
It was important that the resulting design system and library could be understood and implemented easily. I took inspiration from Goldman Sachs' component documentation to organize and document the final designs.
I am a strong believer in testing work to identify opportunities and expose vulnerabilities. The first iteration should never be the final one. I found it essential to gather feedback for the design system so I personally asked RAPP designers to provide me with an honest critique of the component library as they began implementing it. This served as an informal “stress-test” that was instrumental in making the design system future proof.

Reflection
The importance of a robust network
This was one of the most intense, yet fulfilling projects I’ve worked on. It reshaped the kind of "perfection" I pursue in my work. The bulk of my work on this project was understanding how a Design System is organized, implemented, and expanded. It doesn't matter how pretty your visuals are if no one can easily use them. This project is the perfect example of design that is living — constantly growing and morphing to accommodate new needs.
I've always placed importance on having a diverse network of designers, and this project really proved how important it is. This being the first design system I've worked on, I actively sought mentorship from my friends and coworkers to keep learning as I went. When I’m feeling lost, I know there will always be someone with a fresh perspective, a unique viewpoint, and fresh ideas to contribute.