The Ask: Improve scannability on a recall notices page

Why It’s Important: Making content easier to use improves its credibility (source)

The Process: First, I took a look at the page.

I saw that many of the items listed seemed to be recalled on the same day. In the HTML, I saw that these items had the same recall notice URL.

Excerpt of recall notifications page before changes (167 items)
Sample items from list of 167

Building the page by SKU had exaggerated the effect of each recall notice because each notice affected several SKUs. I tried rebuilding the list by recall notice, and this dropped the number of items on the page.

Because a SKU is a business-centric piece of data, I removed it. I also divided the content into chunks by adding product category labels.

This content was jointly owned by two different teams, so I called a short meeting with representatives from both groups to talk through my proposed improvements.

The business owners liked the changes. They asked that we organize the categories on the page from highest number of recalls to fewest.

After a check-in with the UX designer, I built the page in Staging for review.

Recall notifications list after changes
Recall notifications list after changes

Then, after UAT with our business stakeholders, I made the page live.