Class Hub

A representative prototype of the shipped pattern: enter a class, switch between content tabs, filter the attributes table, drill into attribute options, inspect an attribute in the drawer, and stage a change for review.

The diagnosis came from watching merchandisers move through the old Manage Classes surface: the work was not conceptually hard, but the interface made every action feel bigger than it was.

• Ops shadowing

  Users repeatedly scanned past fields that did not apply to the task at hand, then used memory or handoff notes to find the controls they needed.

• Affinity mapping

  Themes clustered around relevance, minimalism, speed, visibility, and navigation - especially bulk creation, bulk edits, previewing changes, and easier brand catalog navigation.

• Prototype review

  The team aligned on a structure that separated header navigation, content tabs, filters/actions, primary data, drawer details, and footer/global intranet content.

• Keep the existing data model

  The redesign needed to respect how classes, attributes, attribute groups, definitions, standards, and brand catalogs already worked inside Wayfair systems.

• Progressively disclose detail

  The main table stays focused on ranking, visibility, options, and deletion. Secondary class and attribute data moves into a drawer instead of competing with the primary scan path.

• Preserve staging controls

  Changes to class and attribute data had to support project mode and Save to Stages, because downstream catalog impact required review before release.

• Fit the intranet shell

  The experience lived inside Wayfair's internal navigation and search environment, so the redesign had to improve the working surface without pretending it was a standalone product.

1. 01

   Make relevance obvious

   Use content tabs and filters to help merchandisers get to the right subset of class or attribute data before asking them to act.

2. 02

   Reduce handoff

   Keep actions, staging, and secondary detail near the table so users do not need separate notes or tribal knowledge to complete common changes.

3. 03

   Separate scanning from editing

   The table supports fast comparison across attributes; the drawer supports focused review and change-making for the selected row.

We explored several structures before landing on the shipped composition. Each direction was evaluated against the same practical question: could a merchandiser find the right class data, understand what applied, and take action without losing context?

• Direction 01

  Open prototype

• Direction 02

  Open prototype

• Direction 03

  Open prototype

The redesigned Class Hub experience shipped as the new way to manage class and attribute data.

The tool did not change the underlying complexity of Wayfair's catalog systems; it made that complexity more navigable. Merchandisers could move from class context to attribute data, take bulk actions, inspect secondary detail, and stage changes with less hunting. Exact figures are held back here because this case study is a reconstruction and the original surface is redacted; the product shape and design rationale are drawn from the shipped work.