Designing AI Search and Trust Signals for Millions of Data Assets

Designing AI Search and Trust Signals for Millions of Data Assets

Designing AI Search and Trust Signals for Millions of Data Assets

Role

Role

Lead Designer

Lead Designer

Team

Team

Sole designer · PM · Engineer

Sole designer · PM · Engineer

Duration

Duration

2 months

2 months

All data shown is for illustration purposes only.

Summary

Walmart Data Catalog holds millions of internal data assets, and analysts couldn’t tell which ones to trust. I designed natural-language search and AI-generated asset descriptions, so people can ask for data in plain words and judge a result without opening it. I also designed Spotlight, a curated tier of trusted assets, with a readiness checklist that shows owners how to qualify. In UAT, task time dropped from 15–30 minutes to 3–5, and description coverage went from 40% to 100%.

What I owned

  • Led research: 4 workshops with 12 users.

  • Designed the search and Spotlight-tab directions.

  • Defined with business and engineering what the AI descriptions should include.

Problem

Illustration of a user trying to net the right dataset among scattered assets with missing metadata, duplicate tables and similar names

Walmart Data Catalog is Walmart’s internal platform where analysts and data users find and use company datasets. When users searched, all results appeared equal, and reliable tables were mixed with duplicates, deprecated versions, and poorly documented assets. Users had no signal for which result to trust, so many bypassed the catalog entirely and asked colleagues on Slack instead.

How did I know it was a problem?

We ran research sessions where participants shared their daily tasks.

Workshops

Workshops

4

4

Users

Users

12

12

Domains

Domains

4

User roles

User roles

3

3

Time per task

Time per task

~25 mins

~25 mins

Research workshop over video call, with a participant searching the data catalog

One of the workshops

Spreadsheet of user statements tagged by feeling and problem type

User statement analysis

Here I observed that…

A typical search performed in the session looked like this.

Journey map of a typical search, from scanning results to asking colleagues, totaling about 25 minutes

…users weren’t struggling to search, they didn’t trust what the search returned.

Understanding the opportunities

Sketch mapping each problem to its cause and the design opportunity it led to

These opportunities directly shaped the four solutions I designed.

Search bar with a natural-language query: Show me Q2 sales data

Improving the search

Grid of data assets with a small set highlighted as trusted assets

Building trust and transparency in search results

Search results loading AI-generated summaries for each asset

Generating asset information

Checklist to promote an asset, showing enrich data complete and lineage review and data quality incomplete

Clear path to make an asset discoverable

Search bar with a natural-language query: Show me Q2 sales data

Improving the search

Search results loading AI-generated summaries for each asset

Generating asset information

Grid of data assets with a small set highlighted as trusted assets

Building trust and transparency in search results

Checklist to promote an asset, showing enrich data complete and lineage review and data quality incomplete

Clear path to make an asset discoverable

Key decisions

With a trusted set established, the question became how to show it in results.

With a trusted set established, the question became how to show it in results.

I explored two directions: a single list where Spotlight assets carry a tag, and a two-tab layout separating Spotlight results from everything else.

Two search layouts compared: a single list with Spotlight tags and a two-tab design that 8 of 12 users preferred
Search result expanded to show an AI-generated description of the dataset

Descriptions emerged from research as the single most useful attribute for identifying an asset. I collaborated with business and engineering to define which details the AI-generated descriptions should surface, so the output was consistently useful rather than generic.

Final designs

  1. NLP Search — users could describe what they needed in plain language instead of knowing the exact table name, making the catalog usable for people new to the data.

Data catalog home page with natural-language search and the user's workbench
  1. Spotlight Tab — trusted assets get their own tab, with automatic fallback to all results when no Spotlight assets match…

Automatically falls back to other assets when no Spotlight assets match.

  1. AI Descriptions — every asset gets a readable, accurate summary, reducing the need to open an asset just to evaluate it.

  1. Readiness Checklist — Owners follow a step-by-step checklist that makes the qualification criteria explicit and the path to nomination clear.

Overview of the final designs: search results, readiness checklist and Spotlight coverage dashboard
Overview of the final designs: search results, readiness checklist and Spotlight coverage dashboard

Early Results

Task time

15–30 min → 3–5 min

UAT results, assets with data quality enabled.

UAT results, assets with data quality enabled.

Description coverage

40% → 100%

Preferred the tab layout

8 of 10 users

Launch metrics

To follow

Most of the time saved came from the finding phase, not the task itself. Users also requested bulk nomination during testing, which is the next gap to close.

Learnings

  1. We started this project trying to fix search. Watching users showed us the real problem was trust. That distinction shaped every decision that followed.

  2. The readiness checklist works well for nominating individual assets, but bulk nomination remains unsolved. Users flagged this in testing, and it’s the most immediate gap to address post-launch.

  3. Two areas worth exploring next:

    1. Using AI to review data lineage.

    2. Simplify data quality setup, reducing manual effort for asset owners.

Other projects

Other projects

Other projects

Nikhil Dasari

Nikhil Dasari

Designed in Arkansas, mentally relocated to Big Sur. Photo by George Cox on Unsplash

Designed in Arkansas, mentally relocated to Big Sur. Photo by George Cox on Unsplash