All projects

Product Tiles: the Shop's component system

One product tile system, born in NerdWallet's Shop redesign and refined with A/B tests on visual details in Lyssna.

Role
Senior Product Designer
Timeline
Platform
Mobile (iOS + Android)
Team
Senior Product Designer, Product Manager, Engineering, Design System team
Product Tiles: the Shop's component system

Overview

During NerdWallet's Shop redesign, the product tile got too complex to solve inside the main project. It had to handle several product types, advertiser disclosure compliance states and lots of content variations, all with one visual language. This case covers how the tile became its own component system: from a brainstorming session, through A/B tests on color, font, spacing and hierarchy in Lyssna, to a full hi-fi flow and engineering handoff.

Product DesignDesign SystemMobileComponent Design

1. Problem identified

This project came out of the brainstorming and ideation phase of the Shop redesign. When we mapped the Shop's problems as a whole, it was obvious the product tile carried a big share of the complexity on its own. It had to work for several product types (credit card, banking and a generic format for future expansion), follow advertiser disclosure compliance states and absorb many content variations, always with the same visual language. So we pulled the tile out of the main redesign and gave it its own workstream, with dedicated time and testing.

2. Brainstorming session

To understand the tile's pain points and form hypotheses, I ran a brainstorming session with the team. We mapped where the current component broke down: different layouts for credit card, banking and loan tiles, disclosure treated as an overlay instead of part of the structure, and no shared spacing and typography tokens. We also listed possible directions before anyone started designing.

3. Lo-fi improvements and A/B testing in Lyssna

With hypotheses in hand, I moved to lo-fis that tested color, font, size, spacing and hierarchy inside the tile. Each variation went through A/B tests in Lyssna, with two or more versions side by side, so decisions came from user data rather than internal taste. The tests answered very concrete questions. Which type weight made the annual fee and rewards rate easier to read without fighting the product name and the NerdWallet Rating? How much space between attribute rows (annual fee, rewards rate, welcome offer, recommended credit score) helped quick scanning, and when did it start to hurt? And how could the advertiser disclosure badge ("AD") stay noticeable without competing with the "Apply now" CTA and the "Add to compare" checkbox?

4. Hi-fi flow and handoff

With lo-fi decisions validated, I designed the full hi-fi flow: three product-type variants (CC, Banking and generic), four states for each (default, pressed, loading, unavailable) and two advertiser disclosure variants built into the component's structure (NE, non-expandable, and RC, reduced/collapsible).

The CC tile ended up with product name, disclosure badge, NerdWallet Rating in stars, annual fee, rewards rate, welcome offer, recommended credit score, a "See full details" link, the "Apply now" CTA and the "Add to compare" checkbox. I validated it with real cards such as the Alaska Airlines Visa Signature® and the World of Hyatt Credit Card. The Banking tile is leaner: product name, badge, rating, APY, minimum balance to earn the APY and monthly fee, tested with products like SoFi Checking and Savings. Both carousels also got a fixed last card, "Explore all," that opens the full list for the category.

At handoff, engineering got the spacing and typography token docs plus behavior notes for every state and variant, so the system could be built the same way across the Shop's L1 and L2.

4. Hi-fi flow and handoff

5. Results

This project has no impact metric of its own, because it was always part of the full Shop redesign. The Shop Redesign is what got measured and shared publicly, including a 176% increase in revenue per session and a 174% jump in weekly Shop tab revenue. The tile is central to that result, but isolating its share wouldn't give a reliable number: it shipped with every other L1 and L2 change in the same release.

6. Learnings

Splitting the tile out was worth it even without its own metric. Testing color, spacing and hierarchy in isolation gave me a precision I wouldn't have reached at the pace of the full redesign. Validating piece by piece in Lyssna, not just whole screens, kept guesswork out of small details that, across hundreds of thousands of impressions, really add up.

I also learned that treating advertiser disclosure as part of the tile's structure, not an overlay, made handoff much simpler and removed ambiguity for engineering.

The bigger lesson was about metric expectations. Not every design project can have a number of its own. Sometimes a component's value shows up in the result of the whole system, and that's a fair way to look at it when that's how the work actually functions.

Next project

Home Equity & Home Refinance