[PRODUCT DESIGN]

Tested Product Blocks

At Pillar4 Media, I design the product blocks on revenue pages across several brands, then redesign each one from what its live A/B test shows.

Role

Product Designer

Year

2026

Platform

Web, mobile-first

Services

Product Design, Experimentation, Dev Specs

Tested Product Blocks

Add a URL to embed a website.
Illustration of three product cards in V1 next to the same cards in V2 with product tags added

The short version

Problem

Readers compare products on long recommendation pages, and the block that shows each product decides whether they click through to buy.

What I did

Designed product cards, expandable blocks and featured placements, read each test, and changed only what the data pointed at.

Outcome

Every V2 targets one specific signal from its V1. Several are in active testing across brands.

Three product cards in V1 next to the same cards in V2

01 / The problem

On a recommendation page, the block is the product.

Readers land on long product roundups, and the block that shows each product decides whether they click through to buy. I design those blocks for brands in sleep, supplements, health and fitness, then hand them to product to test. The tests decide what ships, not opinions, including mine.

Anatomy of a tiled product card: superlative, brand and name, rating, promo and one CTA, in two columns on mobile and three on desktop

02 / Tiled cards

A shopping grid people already know.

Product lists were long and slow to scan, so I borrowed the grid shoppers already use on big retail sites: two columns on mobile, three on desktop. Each card packs a superlative, brand, product name, image, rating, promo and one CTA.

Three signals from the first test, and the V2 card with product tags above the rating

03 / Reading V1

The format worked. The card didn’t say enough.

The first test split. More readers engaged with the cards, but fewer converted, and clicks through to the full product page jumped. People wanted more detail than the card gave them. V2 put that detail in the card: product tags above the rating, styled apart from the superlative so the card stays scannable.

V1 rows with image placeholders next to V2 rows with images and carousel arrows

04 / A loss, diagnosed

Find out why it lost before you scrap it.

An expandable block lost on a health product page, and desktop did worse than mobile. The easy move was to throw out the pattern. But the layout had removed every product image, in a category where people want to see the thing before they consider it. Desktop, where missing images stand out most, fit that story. V2 brought images back in the carousel the full product page already uses, so any change in results traces to the images, not a new interaction.

Two phones: V1 with a small text link, V2 with a button labeled with the product name

05 / Mobile

Change the two things the data points at.

On another brand the same block did well on desktop and trailed on mobile, where fewer readers opened it. That pointed at discoverability, not the idea. V2 changed two things. The label names the product instead of a generic “details,” and the control reads as a button you can tap. Nothing else moved.

Three ways to feature a top brand: a recolored slot, a border and banner, and a smaller mini block

06 / Featured brands

Add prominence without demoting the rest.

The brief was to feature the top brand in a list. The risk: recolor one slot and every other brand reads worse by contrast. So the goal became adding prominence without taking any away. One version adds a border or banner and follows the rankings automatically. The other inserts a smaller block for the top pick, full width so the page rhythm holds, but shorter, so it stands out by being different, not louder.

Four edge cases: an odd card count, a long product name, empty fields that hide, and a logo instead of a photo

07 / The spec

A dev file is a spec, not a Figma export.

Most of the design time went to edge cases: an odd number of cards, names that wrap to two lines, empty fields that hide instead of leaving gaps, and a toggle between a product photo and a brand logo. One file went to a partner’s outside engineering team with no access to our systems, so I built it closer to a prototype, with hover states and interaction notes. The bar: a team I’ll never meet can build it without asking me anything.

Results

V1→V2

Each redesign driven by its own test

4

Brands I designed these blocks for

8

Edge cases illustrated in one dev file

Next project

Grok Bot Widget

Grok Bot widgets on two iPhone Home Screens