Creating an Operational Data Strategy for Retail Buyers

The Problem:

When performing category resets and updates, merchandising and desk management teams for a large grocery retailer was making most of their product assortment decisions and strategy with little to no insights into historical event performance. The current operational process allowed for too much flexibility, so each individual team leveraged different workflows and tools, leading to a breakdown in communication and transparency within their corporate office.

Our Process & Solution:

Our team was originally hired to help with process modernization by creating a centralized platform for the front-end lifecycle of on-shelf products. Part way into the engagement, the focus shifted from a workflow optimization effort to a data-driven understanding of on-shelf assortments. I was brought in after this strategy shift to lead out on the creation of this data strategy.

I spend 8 weeks in research around current reporting habits, data availability, and future needs. Through this research we determined there were 3 main lines of questioning needed in the app: exception, post-activity, and opportunity. Since this was an operationally focused tool, the emphasis on reporting was not just on creating stationary dashboards, but also integrating contextual data into the workflow. So the focus of my synthesis understanding the in-app decision making process and data needed to support those workflow decision.

After the synthesis of this research, I worked with business analysts and development team to determine the current state and availability of the necessary data. This allowed us to build a strategy for initial release, along with a foundation for future data needs. At the time of the contract conclusion, phase I of reporting was in development and the internal team had a clear understanding and roadmap for future iterations.

My Roles:

  • User Research

  • UX Design

  • UI Design

Specific Methodologies:

  • User Interviews

  • Stakeholder Interviews

  • Journey/Process Mapping

  • Feedback Reviews

  • Cross-Functional Collaboration with Analysts and Development

 

Screenshot of full research notes in Airtable. This Airtable follows the flow of data-based decision making from question to action to overall business objective.

This screenshot show the initial research Airtable mapped to a scenario based matrix. This matrix was the basis of our workflow integration, because it allowed us to trace lines of questioning to specific decision making moments.

Screenshot of the extended application IA with reporting research notes. This was the first step of identifying key decision-making moments and what bucket of reporting these moments fall into.

Screenshot of the initial lo-fi whimsical design for the Exceptions Report which is housed within the tool.

High-fi design for Exceptions Report.