Performance Metrics

How suppliers view the performance of their business

Project Overview

My Role

I worked as the lead UX designer overseeing all projects, making sure the experiences were consistent. I built learning materials based on discovery work and gave presentations evangelizing our work and it’s importance to Walmart. I was point person for connecting with other product teams outside of Supplier and brought up opportunities to cross collaborate.

The Project

I was focused on the end to end Supplier One experience. Suppliers had to jump from platform to platform constantly to get their daily tasks completed. Supplier One consolidates those platforms into one place. It was a completely new platform that we built from the ground up.

The Challenges

Had to learn quickly about the supplier space, while being mindful of deadlines
Starting from scratch, no existing Supplier One mock ups or page layouts
Small team of designers (3-5), and limited access to researchers and content designers
Working alongside other enterprise teams creating B2B focused patterns, since our existing pattern library is in progress and geared towards customer facing applications.

The Process

User testing

What is a supplier?
Personas
Supplier ID mapping

End to End Journey Map

Generative User Interviews

Storyboarding

Sample journey and how it affects the end customer
The business opportunities and Walmart’s goals
The core customer emotion driving us towards those goals from a supplier lens

Supplier One Projects

Where We Are Today

User testing

1P (first party) suppliers refer to manufacturers or vendors that sell their products directly to retailers like Walmart. These suppliers typically have an established relationship with the retailer and offer a wide range of products that are sold under the retailer’s brand.

Take a minute to write an introduction that is short, sweet, and to the point.

Started with the information architecture hierarchy

Aligned the hierarchy across all the performance pages and combined the two returns pages

Context of the page

The tabs help set the context of what I’m looking at and for what reason. They function as a cause vs. result comparison.

Consistent header

Every performance page includes the same header structure to help set expectations and ease of use.

Widget charting

There was a common theme of “payments/cost” information on each of the performance pages.

This finding was key in introducing the context switching tabs.

Additionally, I used this chart to align similar widgets with each other starting with the two returns pages combining into one page.

Navigation

I visualized the current structure of the nav with the contextual “payments/cost” info.

But I could also see different ways of structuring info. For example, did they want to see all of that information together or in reference to what was causing it? Maybe both?

As we build out more of the Payments pages, I plan to see how this information scales and fits into the bigger picture.

Widget Patterns

After aligning all the widget designs to use the same design per its function, I categorized them and set a specific hierarchy for the order in which they would lay on the page for consistency.

Designing for the short term and long term concurrently

Immediate deliverables

Mock-ups delivered translating current functionality and general groupings
Translated to Living Design
Delivered a consistent navigation
Delivered reusable widget components
Future thinking

How will this fold into future Payments work?
How might we set up the navigation to scale?
What should we research?