This is some text inside of a div block.

Reimagining IKEA's Product Listing Pages with an adaptive content strategy.

This is some text inside of a div block.

Discovery

This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.

I led a 4-month discovery with IKEA's listing team to define a data-driven, adaptive PLP — surfacing the right content at the right moment for every purchase type, across 10 markets.

This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
This is some text inside of a div block.
TEAM

A cross-functional squad spanning design, research, content and engineering.

Two senior product designers (myself as lead), one UX researcher, one content strategist, two front-end engineers, and embedded stakeholders from category management and merchandising. Discovery ran across 14 weeks with a global remit covering 10 markets.

CONTEXT

Product Listing Pages are IKEA's busiest digital storefront, but they all looked the same.

Whether a customer was browsing a sofa, a kitchen system, or a pack of tealights, the PLP served the same density, the same imagery, and the same supporting content. As IKEA's range expanded across categories with very different decision journeys, this one-size-fits-all template started showing real cracks in performance and customer satisfaction.

PROBLEM

A single rigid template was forcing every category through the same shopping journey.

Customers shopping a planned purchase like a kitchen needed deep guidance, comparison and supporting services. Customers replenishing a low-consideration buy like storage boxes needed speed and density. The same PLP was failing both, hurting findability for inspiration-led shoppers and slowing down task-led ones.

EXISTING RESEARCH

We started by mining what IKEA already knew.

Before running new studies, we audited 30+ existing research artefacts across the customer experience, search and discovery, and category teams. The picture was consistent: customers expected the PLP to behave differently depending on what they were shopping for, and they were quietly compensating for it with workarounds, third-party tools, and store visits.

INSIGHT

“The PLP isn't one page. It's many pages pretending to be one. We need a system that adapts to the question the customer is actually asking.”

This is some text inside of a div block.
This is some text inside of a div block.
CONTENT FRAMEWORK

A shared model for what content the PLP should serve, and when.

This is some text inside of a div block.
PURCHASE TYPES

Three modes that account for nearly all of IKEA's PLP traffic.

Inspirational — the customer is browsing, gathering ideas, often early in a room project. Considered — the customer is comparing options for a known need, weighing services and add-ons. Replenishment — the customer knows exactly what they want and is here to find it fast. Each mode pulls a different set of components into focus.

PERFORMANCE

The data showed real cost in the current template.

Across the 10 markets in scope we saw a 22% drop-off after the first viewport on high-consideration categories, an average of 3.4 filter interactions before exit on inspirational journeys, and a long tail of replenishment customers using site search to bypass the PLP entirely. Customer satisfaction scores trailed the rest of the funnel by 11 points.

WORKSHOP

We brought 24 stakeholders into a two-day cross-functional workshop.

Designers, researchers, content strategists, category leads, range managers and engineers worked through the data together. We aligned on the three purchase types, agreed on the components in scope, and committed to a single shared model for what an adaptive PLP could look like — before any pixels were drawn.

HOW MIGHT WE

“How might we let one PLP behave as many — without forcing every category team to redesign it from scratch?”

This is some text inside of a div block.
This is some text inside of a div block.
QUANTITATIVE BENCHMARK

We benchmarked 18 PLPs across home, fashion, electronics and grocery.

Across the benchmark we scored each PLP on 42 criteria covering content density, comparison support, inspirational content, services exposure, and replenishment shortcuts. The pattern was clear: best-in-class retailers were already running multiple PLP behaviours behind a shared visual system, while IKEA was running one behaviour across very different categories.

CARD SORT (152)

152 customers told us how they group IKEA's content blocks themselves.

Across an unmoderated open card sort and a closed validation sort we tested 36 PLP content blocks against the three purchase types. Customers grouped components into recognisable bundles — inspiration first, then comparison, then services — and crucially they wanted those bundles to behave differently depending on what they were shopping for.

COMPETITOR ANALYSIS

Adaptive PLPs are the new normal outside furniture too.

Wayfair, Argos, John Lewis, Marks & Spencer, Zara Home, Made.com, Crate & Barrel, and West Elm — we mapped how each one let the PLP shape-shift across categories. The strongest patterns combined a stable visual system with category-specific content modules and contextual entry points into services or planning tools.

SOLUTION — STEP 1

Tag the catalogue by purchase type.

This is some text inside of a div block.
SOLUTION — STEP 2

Build a shared content module library.

This is some text inside of a div block.
SOLUTION — STEP 3

Define adaptive templates per purchase type.

This is some text inside of a div block.
SOLUTION — STEP 4

Wire in services and planning where they earn their place.

This is some text inside of a div block.
SOLUTION — STEP 5

Govern the system so it stays coherent at scale.

This is some text inside of a div block.
CLOSING

Discovery handed over a shared model and a clear path into design.

We left the organisation with a single content framework, three reference templates, a tagged catalogue ready to pilot, a prioritised module backlog, and a governance proposal. The next phase moved into prototyping and live testing on two pilot categories, with the goal of proving the adaptive model before rolling it across the full range.