REACH by Walmart
Empowering Walmart to handle risk with confidence by creating a unified data environment of daily work
About
REACH is one of Walmart’s internal products. It’s a cloud-based GRC (Governance, Risk and Compliance) platform, which allows for visualizing and mapping business operations.
The GRC platform, REACH, empowers Walmart to handle risk with confidence by creating a unified data environment of daily work; connecting the business, security and IT.
Background
Team: The team consisted of myself (the Product Designer), the Product Owner, the Scrum Master and around 15 developers.
My Role: As the Product Designer, I had the opportunity to design REACH’s user interface by fulfilling business requirements and solving use cases. I was responsible for delivering User Interface specs to the development team.
Our Process: We worked in an agile scrum environment, working in two-week sprint cycles.
My toolbox: Figma, Miro, Jira, Zoom
The Users: Since REACH is used by many different departments and facilities, there are many different types of user personas interacting with the platform. A large part of my role was focusing on the builder who was responsible for building workflows within REACH.
Designing for Calculated Fields
I was tasked to design the user interface for the builder to create Calculated Field Properties.
What does this mean, exactly?
The Calculated Field Properties allows the builder to manipulate the form based on certain criteria.
Business Requirements
Design a simplified input for nontechnical users to create a Calculated Field.
Design an advanced input for technical users to have the freedom to create advanced functionality to the form.
Display how error-handling occurs.
Mapping out the user flow
click on image to see larger image
Ideation
Competitive Analysis
-
![]()
Notion
-
![]()
ServiceNow
-
![]()
Excel Spreadsheets
I studied these three platforms and their features in order to stay competitive and align with user expectations.
The design on the left is the interface for the Basic Input.
Rationale
For this use case, we have a nontechnical user. The user wants to use an “If” statement to change the form content.
For example, “If Questions 1 answers yes, skip Question 2”
The design on the right is the interface for Advanced Input.
Rationale
This use case is for the technical user. The user (aka the builder) is able to create formulas similar to how they would in excel to manipulate the contents of the form.
Here, the user has the freedom to create formulas that best fit their needs for creating a robust form.
Where can the user turn on a Calculated Field?
How do we know if the calculated field is turned on?
Testing the design
User Feedback
“Facilities are in a hurry when using Reach and are lost where to go and which workflow to use. The system doesn’t guide the user.”
— Coryn, Walmart Lead
Retrospective
It was an exciting opportunity to work on Walmart’s new product, REACH. I believe the product has a long road of iterations and improvements ahead, but we developed and designed a great MVP that thousands of Walmart employees and affiliates use daily.
During the time I worked with Walmart, I would have liked to meet with the users sooner so I could develop deeper empathy for who I was designing for.
However, I learned a lot while I worked in agile environment. I developed my communication and collaboration skills with developers. I learned to adjust the way I delivered the specs of the design based on each developer’s preference.