Bed Threads Build Your Own Bundle hero composition.
Product · 2022 · Bed Threads platform

Build Your Own Bundle.

Designing Bed Threads' Build Your Own Bundle from MVP to production. Lateral thinking turned a dropdown into an experience that lifted average order value by $128. Direct competitors used it as 'inspiration' for their own.

Role Senior UX/UI Designer
Client Bed Threads
Year 2022
Disciplines Product · Research · E-commerce

Brief

Take Bed Threads' Build Your Own Bundle from a working MVP to production. New colours were the focus of the 2021 range, so the configurator needed to scale with the catalogue without breaking the mobile flow that drove most of the bundle traffic.

Problem

The original picker was a single dropdown. As the palette grew it would keep lengthening, force more scroll, and bury the size step behind the colour decision. Mobile users were dropping off at exactly the moment the configurator should have felt like the most engaging part of the site.

My role

As Senior UX/UI Designer I owned the experience end-to-end:

  • Audit of the original picker and the live MVP against Hotjar behaviour
  • Blind usability sessions via userbrain.com plus moderated user interviews
  • Competitive read of two direct competitors that had adopted the BYOB pattern
  • Lateral-thinking ideation that broke the linear progress bar
  • Mobile and desktop final design including progressive disclosure and the live 3D render
  • Annotated developer hand-off and QA
Outcome

A configurator the catalogue could grow into — and competitors copied.

$128
average order value lift, MVP to production
2+
direct competitors observed adopting the pattern
MVP→prod
three rounds of testing across mobile and desktop
1
progressive-disclosure flow, mobile and desktop unified

Original, MVP, Final

  • The original design required users to select one colour from a dropdown menu. With new colours launching as a 2021 focus, that dropdown would keep lengthening and require further scrolling.
  • Expanding colours into swatches in the MVP introduced gamification and creativity, and increased the usability of the experience.
  • The final replaced the swatch row alone with progressive disclosure and a live 3D render, so the bundle built itself in front of the customer as each step resolved.
Original BYOB: single dropdown colour picker
Original
MVP BYOB: swatch row replaces dropdown
MVP
Final design: progressive disclosure and live 3D render
Final design

Testing

Goals: assess the usability of the BYOB experience on mobile. Gather initial insights, build assumptions, and validate them in follow-up tests. The output: insights to make design and functionality improvements.

Method: blind user sessions via userbrain.com and user interviews.

Insight: users got "excited" at the colour step and missed sheet-size selection further into the flow. That single behaviour became the trigger for the progressive-disclosure pattern in the final design.

Market-leading MVP

After launching, direct competitors used the Bed Threads BYOB as 'inspiration' for their experiences. Some executed features better than our MVP. That let me conduct blind usability testing against the copies, and use those findings to push the experience further.

Market-leading MVP composition.
Competitor A bundle configurator captured in June 2022, showing the same swatch row and step-by-step flow.
Competitor A · June 2022: the same swatch row and step-by-step flow as the BYOB MVP, shipped roughly six months after Bed Threads launched the pattern.
Competitor B colour-selection step captured in June 2022, showing the live-render bundle preview reproduced from BYOB.
Competitor B · June 2022: the live-render bundle preview, reproduced from the Bed Threads pattern alongside the colour-selection step.

MVP review

I conducted a detailed review of the design to surface areas of opportunity. Inconsistencies between the mobile and desktop progress bar stood out, alongside other usability problems uncovered through Hotjar and follow-up testing.

Progress bar

The progress bar imagery below shows the inconsistencies across the mobile and desktop experience. The sheets and pillowcases steps in particular were a focus of the redesign.

Original mobile progress bar.
Mobile: original progress bar.
Original desktop progress bar.
Desktop: original progress bar. Inconsistent with mobile.

Progress-bar ideations

Designing a progress bar that moved linearly on desktop wouldn't solve the inconsistency. In some ideations the font was too small for a sub-heading, or steps sat too close together to read.

Progress-bar ideation: linear desktop bar with sub-step labels.
Linear bar with sub-steps: sub-heading type ran too small to read.
Progress-bar ideation: linear bar with grouped pillowcase steps.
Grouped pillowcase steps: sheets and pillowcases sat too close together.
Progress-bar ideation: numbered linear bar with full step labels.
Numbered bar with full labels: legible, but the row stretched past the viewport.
Progress-bar ideation: condensed linear bar with icon-only steps.
Condensed icon-only steps: fit on screen, but step meaning was unclear.

Problem solving

I needed lateral thinking to crack this. I found inspiration in how Gmail, Wix, Minecraft, and the settings menu on my monitor lay out their options. They stack and move left-to-right. Why does the progress bar need to move linearly? It doesn't. It can progress vertically, with options stacked.

Inspiration: Gmail settings layout.
Inspiration: Wix-style stacked options.
Inspiration: monitor settings menu.
Inspiration: Minecraft-style stacked options.

Desktop progress-bar ideations

Exploring placement of the signifier and the overall UI for the desktop progress bar.

Desktop progress-bar exploration: four placement variants for the step indicator.
Four desktop variants exploring where the step indicator sits relative to the workspace.

Progress bar · desktop

The lateral-thinking insight resolved into a vertically-stacked indicator on the left, with the live render holding the right-hand workspace. Steps progress top-to-bottom on desktop and the same logic carries over to mobile, so the two patterns finally read as one experience.

Final desktop progress bar: vertical indicator on the left, live render on the right.
Final desktop: vertical step indicator on the left, live render holds the workspace.

Ideations · mobile features

Sketching how the mobile build step would carry colour selection, the live render, and the primary CTA without crowding the viewport.

Mobile feature ideations: render placement, swatch density, and CTA hierarchy.
Mobile features: testing render placement, swatch density, and where the primary CTA sits.

Select-size ideations

The size step was where mobile users were most likely to skip ahead. These frames explored how to make the choice visible without breaking the rhythm of the colour-led flow.

Select-size ideations: pill, segmented, and stepper variants.
Size-selection variants: pill, segmented, and stepper patterns tested against tap accuracy.

Concept refinement

Ideation and refinement of the concept across mobile and desktop.

Concept refinement: mobile and desktop side-by-side with shared component logic.
Mobile and desktop side-by-side: aligning component logic so the two read as one system.

Developer notes

Annotated specs covered the progress-bar interaction states, swatch-tap behaviour across breakpoints, and the conditional logic between step completion and the live 3D render. The hand-off doc became the squad's source of truth across engineering and QA.

Developer notes: progress-bar state annotations across breakpoints.
Progress-bar states: annotated transitions between completed, active, and pending steps.
Developer notes: swatch interaction and 3D-render trigger specs.
Swatch interactions and render triggers: tap targets, hover states, and the data flow into the 3D preview.

Final design

Progressive disclosure

Through testing I noticed that users were getting "excited" about the colour options and missing steps further into the flow. I used progressive disclosure to break larger steps into manageable tasks.

Final design: progressive disclosure.

Mobile

  • Signifier showing completion or incompletion of each step.
  • Live 3D render lets the user visualise their combination.
  • Primary CTA, plus "start over" and "save for later".
  • Colour swatches at every selection step.
Mobile: build step with colour swatches.
Build: colour swatches and live render.
Mobile: summary step with smaller render.
Summary: render scales down; items become editable.

Desktop

The right-hand 'workspace' allows the user a more efficient workflow. The inspiration pop-up lets them compare the live render to inspiration imagery side-by-side, reducing amended orders post-purchase and saving the business money.

Desktop final design: workspace layout.
Workspace layout: efficient desktop workflow.
Inspiration pop-up: render vs lifestyle reference.
Inspiration pop-up: render vs. lifestyle reference, side by side.

Methods

Responsive web Progressive disclosure Usability testing Hotjar analysis End-to-end 3D render integration Lateral problem-solving Developer handover