Case study / 03

lululemon · 2025

Helping guests understand the whole outfit

I redesigned an AI-assisted outfit component so guests could understand a complete look at a glance and confidently shop more than one item.

Headline outcomeEngagement increased from ~2% to 5%
Outfit Inspiration final interface
03

What I owned and why it mattered.

Role
Product Designer
Team
PM · Research · Machine learning · Engineering
Platform
Web · iOS native app
Timeline
Q4 2024 – Q1 2025

My responsibilities

  • Workshop facilitation
  • Experience architecture
  • Component design
  • Accessibility behavior

Methods

  • Co-creation workshop
  • Concept sorting
  • Interaction design
  • Accessibility mapping

The problem behind the interface

The existing outfit module was visible but underused: engagement was 2.35% on web and 1.6% in app. Products appeared as recommendations, but the interface did not help guests visualize a coherent head-to-toe look.

What the direction was based on

  • 01

    Baseline engagement was 2.35% on web and 1.6% in app

  • 02

    Guest needs clustered around versatility, styling education, and confidence for an activity or occasion

  • 03

    Concepts were generated in a workshop, grouped into five experience types, and sorted toward a preferred direction

Turning uncertainty into a focused design direction

I led a concept workshop, organized ideas into five experience types, and evaluated them against three guest needs: versatility, styling education, and confidence for a specific activity or occasion. Exploration covered outfitting rules, hierarchy, accessibility, and future scalability.

The grid creates hierarchy between the seed item and supporting pieces
02The grid creates hierarchy between the seed item and supporting pieces
Guests wanted an outfit idea—not a row of related products. The relationship between the seed item and every recommendation had to be immediately visible.
01

Show a complete look

A structured flat lay communicated the relationship between the seed item and supporting products more clearly than a generic row.

02

Preserve a clear hierarchy

The seed product remains visually primary while recommendations read as one coordinated outfit.

03

Future-proof the component

Modular slots allow recommendation strategies to change over the next 12–24 months without replacing the interface.

A system people can understand at a glance

A structured flat-lay grid establishes the seed item first, then organizes complementary products into a complete look. Accessible carousel behavior and modular content slots allow future recommendation strategies to plug in without redesigning the interface.

A complete outfit reads as one idea on mobile
03A complete outfit reads as one idea on mobile
Exploration compared density, hierarchy, and product relationships
04Exploration compared density, hierarchy, and product relationships
Component anatomy documented content, controls, and responsive behavior
05Component anatomy documented content, controls, and responsive behavior
A modular roadmap connects the current experience to future strategies
06A modular roadmap connects the current experience to future strategies

Designing inside the real system

  • Machine-generated imagery and product combinations could vary in quality
  • Carousel behavior needed explicit keyboard and screen-reader focus rules
  • The pattern had to support future recommendation strategies

I led concept generation and sorting, partnered with research on guest needs, worked with machine-learning and engineering partners on content variability, and documented accessible focus behavior for carousel arrows, pagination, and skip links.

What changed

Engagement increased from ~2% to 5%

  1. 01Engagement increased to 5%
  2. 02More multi-item purchases started in the component
  3. 03The modular pattern was designed to evolve over 12–24 months
Measurement note

The source reports engagement increasing from roughly 2% to 5%, alongside more multi-item purchases through the component. The source does not specify the evaluation window, so the case study avoids implying a precise causal attribution beyond the reported change.

What I’d carry forward

Designing for machine-generated content meant planning for inconsistency. Clear rules, resilient layouts, and useful empty states mattered as much as the ideal-state composition.

Next case study · lululemon

Building a system for complete looks—not isolated items

View case study ↗