Aviera
2024
How can service design assist with the strategization and installation of a new ERP at Kroger’s 30+ manufacturing plants?
Designing approval workflows, budget controls, and review processes to support growing organizations.

Overview
The challenge
I joined Kroger on a small but mighty team with the task to transition all of Kroger's 32 manufacturing plants across the US onto a new ERP (Electronic Resource Planning) system. The goal was to modernize technology and standardize processes.
Where we stand today
While this case study will more or less focus on Release 1 at State Avenue, we have gone live now at 6 different plants, including both Grocery and Bakery plants, to date, with a handful more scheduled before the end of this year.
Problem
Grasping the Scope of the Project
Kroger brand products account for one third of the annual revenue for Kroger, and their products are produced from among 30+ manufacturing plants throughout the United States.
To get them all onto the new system means understanding where they are now and preparing them for the changes, which means educating and training them on how their work will remain the same or be different in the future.

Each plant has a unique challenge
01
Products
Each plant produces a different variety of products
02
Systems
Each plant relies on a different combination of tools and systems.
03
Environment
Each plant as its own unique physical constraints.
04
Practices
Each plant has its own deeply ingrained practices.
Insights
Lessons from Release 1
Plants are unique
Develop tools
People!
Training!
Data! Although this was not an area I spent much time in, it seems to be worth mentioning considering its importance.
Plants are unique
All plants are different, no matter how much we wanted to standardize from the beginning, the uniqueness of each plant needs to be considered and taken seriously.
Develop Tools
All plants are different, no matter how much we wanted to standardize from the beginning, the uniqueness of each plant needs to be considered and taken seriously.
Develop relationships
All plants are different, no matter how much we wanted to standardize from the beginning, the uniqueness of each plant needs to be considered and taken seriously.
Training
All plants are different, no matter how much we wanted to standardize from the beginning, the uniqueness of each plant needs to be considered and taken seriously.
Research
Making sense of it all
While there was plenty of documentation for the new system, it was overwhelmingly detailed and technical. It required we, as a team, to self-organize the processes and system in a simpler way. We developed service blueprints that helped bridge the multi-level system down to the people process layer.

One of several Service Design Blueprints with multiple levels of phases, processes, user actions, use cases, hardware, links to specific user journeys, data, and more imbedded (some information redacted)
Unique Plant Challenges
Each plant has unique physical challenges. State Avenue's challenges were among the most complex of all the plants we've been to so far. But because of these complexities, we learned a lot about how to improve the discovery process on future releases.

Outcomes & Deliverables
Mapping our Findings
State Avenue received the bulk of our attention, but in order to see the whole picture, we had to also investigate other plants, warehouses, and centralized agencies such as RASC and Sourcing.
We conducted deep dives into the systems, users, and processes at these institutions to understand how decisions were being made and where inefficiencies existed.
We were able to surface pain points and decision-making patterns by becoming close with the people that worked at the plant, observing their ways of working, and interviewing them for a deeper look into ….

End-to-end process maps separated by line
We mapped the current "end-to-end" of each product at each plant - from planning to production to shipping, focusing on the human and system touch-points on that journey.
Comparing and contrasting the current and future-state maps, we could anticipate where significant changes to the associate's routines and responsibilities would take place.
Communication
Developing Tools
While the service blueprints are necessary for certain strategies to be seen, they weren't …
Plant leadership had issues with the complexity of the system and needed a better way for associates to understand their new role. We needed to pivot

mini-plant simulation
ux design concerns document to track opportunities for improvement
Centralized approval dashboard for reviewing requests, tracking statuses, and reducing delays.
Reflection
Results from State Ave and learnings from future releases
Our approach to using service design methodologies revealed:
Higher problem clarity - able to be more focused on what matters in discovery
Bespoke configurations are sometimes required to meet unique needs, and that's okay
Regular communications strenghtens relationships

To assist with future releases, I developed a "discovery questionnaire" with another designer. It includes questions that come up frequently during discovery and saves everyone time from having to attend meetings to ask the questions.

