TUMI digital flagship store shown across desktop and mobile.

TUMI / Digital Flagship Store

Luxury · Retail · B2C

Building a flexible system
for a digital flagship.

I designed an adaptable component and GUI system that helped TUMI’s digital flagship flex across products, shopping intents, content types, and screen sizes without losing its identity.

Role
Senior UX Designer
Client
TUMI
Product
E-commerce Web
Date
2022

The brief

Create a flagship experience that could adapt without fragmenting.

TUMI needed a digital experience that could support product discovery, comparison, personalization, service, and storytelling across a complex product ecosystem.

My role was to turn a broad product vision into a flexible system that design and engineering could use to build, adapt, and scale.

01 / Context

A digital flagship needs
more than a visual refresh.

TUMI is a U.S. luxury luggage brand generating approximately $750M in annual revenue. Its digital flagship needed to carry the clarity, confidence, and sense of service of a physical store.

Customers could arrive with very different goals: browsing by category, searching for a specific product, comparing luggage, understanding materials, checking airline restrictions, or learning about the brand.

A single rigid page template could not support all of these experiences well. The system needed a stable foundation and the ability to change with context.

TUMI customer personas, shopping journeys, and product needs.
Fig. 01 Different customers needed different information and paths through the same product ecosystem.
01

Discover.

Help customers understand what TUMI offers and where to begin.

02

Evaluate.

Help customers compare products, materials, features, and fit.

03

Connect.

Make product stories, service, and brand values part of the shopping experience.

02 / Insights

Consistency should create
confidence, not limitation.

I combined competitive research, current interaction data, product requirements, customer scenarios, and stakeholder input to define what the system needed to support.

The key insight was that consistency should live in the system’s structure and behavior. The content, hierarchy, and composition could change when the user’s task changed.

01

Navigation had to guide.

Categories needed to explain where customers could go and why each path mattered.

02

Search had to interpret intent.

Search should help customers explore, correct, preview, and narrow their options.

03

PDPs had to tell the product story.

Product pages needed to combine visual storytelling with clear, transparent decision support.

TUMI navigation, search, and product detail page challenges.
Fig. 02 The experience needed to support wayfinding, search guidance, and product understanding—not just access to pages.

30%

Use site search

Search represented a high-intent shopping opportunity.

5–6x

Higher conversion potential

Search visitors can convert at a much higher rate than average visitors.

98%

Need better PDP information

Product pages must reduce uncertainty before purchase.

These figures were used as directional inputs during planning and framing, not as measured outcomes from this project.

03 / The problem

How might one system
support many shopping moments?

TUMI’s products differed by category, material, size, use case, and customer intent. A luggage shopper needed different guidance from a backpack shopper, and a first-time visitor needed different support from a returning customer.

The challenge was to create enough consistency for the experience to feel like one flagship store, while allowing each product category and page to communicate in its own language.

How might we build a component system that adapts to content, context, and device without losing clarity or luxury?

TUMI information architecture mapped into a responsive navigation system.
Fig. 03 The system needed a shared information architecture that could support category-specific navigation and content.

04 / Design response

Stable foundations.
Flexible compositions.

I designed the system at four connected levels: information architecture, component structure, behavior, and delivery.

The goal was not to make every page look the same. It was to make every variation feel like it belonged to the same system.

01

Build navigation as a flexible framework.

I created a shared navigation structure that could adapt to the logic of each category while keeping the overall interaction pattern consistent.

Luggage could be organized by size, construction, and material. Backpacks could be organized by purpose, laptop size, and material. Bags could use type, laptop size, and material.

TUMI navigation variants adapted for luggage, backpacks, and bags.
Fig. 04 One navigation framework, adapted to the meaning of each product category.

Fixed: structure, hierarchy, behavior, and visual language. Flexible: category logic, labels, icons, descriptions, and filters.

02

Turn search into shopping guidance.

I designed search as a guidance component rather than a simple input field. Users could see popular categories, trending products, query suggestions, spelling corrections, and relevant product previews.

Hovering over a suggestion gave customers a quick preview of relevant products before they committed to a results page.

TUMI search experience with suggestions, product previews, and query guidance.
Fig. 05 Search guided intent through suggestions, previews, corrections, and category context.

Search became a bridge between customer language and TUMI’s product system.

03

Make product pages configurable.

I reframed the PDP as a configurable storytelling system. Its structure could combine product visuals, specifications, reviews, service information, sustainability stories, airline guidance, and related products.

The module order and content could change according to the product and the user’s decision needs.

TUMI storytelling product detail page with product information, reviews, airline guide, and brand content.
Fig. 06 The PDP combined functional decision support with product storytelling and emotional connection.
04

Design for responsive behavior.

Responsive design was treated as behavioral adaptation, not visual resizing. I mapped how navigation, search, product cards, galleries, tabs, and content modules changed across desktop, tablet, and mobile.

TUMI responsive interaction flows across desktop, mobile, and tablet.
Fig. 07 Components adapted their behavior and hierarchy across screen sizes rather than simply shrinking.
05

Document the system for reuse.

I documented grid, typography, color, basic components, complex components, variants, states, responsive behavior, animation, and content rules.

This created a shared language for design and engineering and made the system easier to extend beyond the first release.

TUMI design system documentation showing grid, typography, colors, basic components, and complex components.
Fig. 08 Documented components and variants supported design consistency and engineering efficiency.

A component was defined not only by how it looked, but by how it behaved, changed, and could be reused.

06

Translate design into buildable rules.

I worked closely with development from early planning through QA and launch. Delivery files included interaction annotations, content variation notes, responsive behavior, and animation breakdowns.

Early engineering feedback helped identify technical constraints before they became expensive to change.

Annotated TUMI design handoff showing static, dynamic, responsive, and animation notes.
Fig. 09 Design handoff translated visual intent into implementable interaction and content rules.

05 / Outcomes

A flexible system
that could scale.

The work delivered a responsive digital flagship experience and the system behind it: reusable components, adaptive content structures, documented behaviors, and a clear design-to-development workflow.

20

Features and flows

Across navigation, search, PDP, wishlist, comparison, gifting, and service.

9

Product stories

Designed and delivered across the flagship experience.

3

Responsive surfaces

Desktop, tablet, and mobile behavior documented.

Final delivery included the homepage, collection pages, product listing pages, gift product pages, wishlist, product comparison, global navigation, smart search, and product detail pages.

TUMI final delivery showing nearly 20 features and flows across 9 product stories.
Fig. 10 The system supported the flagship experience across discovery, evaluation, personalization, purchase, and service.

What I would carry forward.

An adaptable design system is not a collection of reusable rectangles. It is a set of decisions about what should stay stable, what can change, and what conditions should trigger that change.

The strongest systems are consistent at the structural level and flexible at the content and interaction level.

I built a flexible component system that allowed TUMI’s digital flagship to adapt without losing its identity.