EBS Design System
Laying the foundations for a new system
My Role
Company
Walmart
Industry
Year
Company Overview
The Experience design team sits within Enterprise Business Services (EBS) EBS whose mission is to create and define user experience excellence for products and services across Walmart Global Tech.
Problem
The EBS design team grew rapidly to help support internal business partners on new software initiatives within the enterprise. These projects ran into difficulties during the development process due to inconsistent styles, patterns, and components across our product portfolio due to a lack of officially shared components in design or in code. This lack of design standardization would result in product delays due to numerous instances of refactoring from both design and engineering teams.
Solution
To create a design system across EBS to help decrease inefficiencies in the product lifecycle by improving consistency in design standards across both design and engineering team. The goal was to provide a platform to support a wide range of products across internal product teams.
Role
As the design lead for this effort, my responsibilities included outlining the vision, roadmap, planning for the deployment of a new system across EBS. The goal was to establish a robust system that included design principles, documentation, and a design library kit with components to match in code.
Strategy
The scope and responsibility of building a design system is a very large undertaking. Before any work could begin, we needed buy-in from Senior Leadership to move this initiative forward.
A presentation was prepared for Senior Design Managers, Directors and the Vice President of the department to get the project approved. The deck contained information describing what a design system was, how it aligned with the department goals, a budget proposal, and a high level roadmap of the resources necessary to create, manage and deploy a system.
Research
To gain a deeper understanding of the existing issues described by stakeholders we first needed to conduct user research. I partnered with a researcher to conduct user interviews to understand the needs of both designers and developers. These two user segments were selected as the central focus for the research effort because they were involved in key stages of the development process; from initial intake, project kickoff, design to hand-off, implementation in code then finally product delivery.
Design Principles
Another aspect of the system we took took time to define were design principles. Design principles are important because they help define the standards of design for a team. In essence they represent the values the team wants to measure against when designing products. And up until this point, the team had not defined any set of values for the team to follow.
Design Principles:
Collaborative
Simplicity
Research & Empathy
Universal and Accessible
Systematic
Foundational Audit
Before any system work could be explored we needed to take time to conduct an audit of our products. An audit would help us better understand what products exist in our product portfolio and inform us how to proceed with our design standardization effort. The audit we focused on first revolved around foundational elements to help us better understand the landscape of styles needed for the new system.
Component Audit
After the foundational audit was complete we made preparations for a second audit focused on larger parts of a system using the same project as in the foundational audit. In this case the audit’s goal was to gain better insight on existing discrepancies but for components and patterns. For this effort, I collaborated each design lead for each project selected for the audit to identify existing components and categorize them into different groupings based on similar functionality.
Change of Direction
As we continued to set up the foundations for a new systems we also began to define other areas such as governance for a new system (using Jira), design toolsets for future design libraries (Figma), building advocacy across the teams, team trainings, and researching how design tokens could be integrated in future front-end code. As we reached out to other teams for future collaboration we learned that other teams had also begun working on similar system initiatives.
One team, Ecommerce in particular, had recently updated their own foundations after some internal brand changes were released by the company. After learning more about the work and the direction they were headed I began meeting with their Head of Design to discuss our similar initiatives.
Conclusion
In the end, the initiative to create a design system specifically for EBS never continued. Senior Leaders decided it would be best to try to adopt the other design system as part of a new standardization effort to streamline ways of working. With that said I’m very proud of the initial effort made to establish a new system. Given more time and resources I’m certain we could have made a system capable of improving the lives of my fellow associates across the Enterprise.
