top of page
Site Logos_Kroger.png

Overview

Research and capture the structure of the Kroger organization and how they intersect with the Retain Merchandising System (RMS). Create tools that improve, and capture data that is used by the fulfillment centers, RMS users, and Delivery drivers around the country.  

My Role

Senior II Product Designer 

Stakeholders

- Kroger Organization
- Leadership  
- Fulfillment Centers
- Delivery Drivers 

Tools

- Mural
- Figma 
- Power BI
- Teams
- Outlook 
- Zoom
- Jira
 

RMS Research Project

Kroger needed to understand their new Retail Merchandising System (RMS), and what Products and Roles intersected with it. I conducted a research study that lasted a few months to speak to the various players, and documented their roles, the products they worked on, as well as evaluate the system and it's data to understand how they all work together. 

The result of the research study was a highly complicated diagram that listed the Systems that exist in RMS, Products that interacted with RMS, the names of the roles that supported those products, and what/where data was input and output in the system. This helped the RMS users, as well as Kroger leadership to identify who to speak to, and where improvements needed to be implemented. 

RMS-System-Diagram.gif

Fulfillment Center RMS Synchronizer Research

Kroger was looking for a solution to the issues fulfillment centers were having with updating their inventory with the RMS. The updates were not happening frequent enough, causing discrepancies in inventory numbers, and their inability to know what needed to be stocked and restocked. I lead my team in researching and interviewing fulfillment center employees to understand the existing user flow by role, understanding when they would need to access this system, what data their needed to see, and how often the updates needed to occur. 

Legend .gif

Sketch + Wireframe 

I held sketching and wiring framing sessions with my team to plan how the tool should work. Because the tool was heavy with data, we needed to breakdown how, and which users would access and view the data. Since none of the users are data experts, it needed to be simple and easily understood. It was also a requirement that users should not have to spend much time using the tool to maximize efficiency. We tested these designs with various fulfillment center employees to gather feedback and make improvements. 

Basic Access.png
No Access.png
Manage Site Access.png
Sku Sync.png
Screenshot 2023-03-06 at 2.51.08 PM.png

Prototype 

During the entire process, I was engaged with the development team to be sure the designs we created could be built in a timely manner. This tool was an urgent need, and fulfillment centers wanted to implement it into their work flow as soon as possible. After our final round of testing, I lead my team in designing the final prototype that would be built by my engineering team. Early on in the process, we identified what features would be part of MVP, and what would be added to our backlog for improvements. We logged more of these improvements as we acquired feedback from the users.  

My Learnings

​- When there is a lot of confusion regarding roles, products, and processes, speak to as many people in the organization as possible. You will find clarity and answers. 
- Getting a product live in a timely manner means being strict about what goes into MVP. Plan, and add stories to the backlog so the improvements are more likely to happen. 

What's next?

- We spent time planning and capturing requirements in Jira for phase 2 of the FC Synchronize launch. 
- The goal is to make it a one stop shop for fulfillment center employees. 
- Following the FC Synchronizer project, another team requested I join on designing a Power BI dashboard for delivery drivers to track the temperatures of their produce during transports. This project was confidential, and results cannot be shared outside the Kroger organization. 

bottom of page