Aviera

2026

Designing a modern dairy receiving app

I researched and designed a tablet app to replace Kroger's existing dairy receiving process at 16 of it's dairy manufacturing plants around the U.S.

Role

Product Designer

Timeline

July 2025

Team

3 Designers

Platform

Web application

Role

Product Designer

Timeline

July 2025

Team

3 Designers

Platform

Web application

Overview

Finding a replacement for Kroger's legacy applications

Kroger’s Project MAKE required that the first of many dairy plants be ready to go-live with the new ERP, Infor’s “M3”, by the end of 2025, but it's legacy application for managing dairy receiving data was not compatible with the new ERP being installed.

The Impact

For a successful go-live to happen, the legacy app would need to be replaced.

+32%

Balance check speed

2.5 min → 1.7 min

+32%

Balance check speed

2.5 min → 1.7 min

+41%

Transaction clarity

34% → 48% confidence

+41%

Transaction clarity

34% → 48% confidence

−25%

Navigation steps

4 steps → 3 steps

−25%

Navigation steps

4 steps → 3 steps

Problem

16 dairy plants, 16 combinations of systems and processes

Developing a new system/interface also demanded a new standard that each plant would need to follow. Even though this release would only see 1 of the 16 dairy plants go live on the new system, we would need to make sure that the remaining plants could accommodate the new system.

Research

Combining everything we know

I partnered with my PM (and with the occasional assistance from another researcher/designer) to arrange numerous discovery sessions with stakeholders to understand how systems and processes differentiated themselves across key plants, to identify common challenges, and to uncover opportunities.

SME Guidance - We received guidance from SMEs (Subject Matter Experts) and eladership, with access to supporting documentation to assist with requirement gathering.

Understanding the user journey

Each dairy plant we investigated had some combination of roles in the receiving process that could be simplified as Receiver, QA, and Accounting. Each of these roles would be impacted by the move to the new system - namely having a new way to interface with their current work patterns. Each role and each interface would need more focused attention to get the desired outcome.

01

Truck Arrives

Friction

Pending, available, and used balances were not clearly distinguished.

Opportunity

Introduce clearer balance separation with distinct visual hierarchy.

Impact

Improve balance scanning and reduce repeated checking behavior.

02

Lab Testing

Friction

Payments and activity lacked enough context before actions.

Opportunity

Surface merchant details and payment status directly within activity flows.

Impact

Reduce uncertainty and help users understand activity faster.

03

Unloading

Friction

Important actions became harder to find within visually dense layouts.

Opportunity

Simplify navigation patterns and prioritize key financial actions.

Impact

Improve task completion and reduce navigation friction across workflows.

04

Filing Records

Friction

Finding and correcting lost and incorrect scale tickets

Opportunity

Create stronger hierarchy between balances, activity, and supporting details.

Impact

Help users scan information faster and focus on what matters most.

Ideation

Exploring interface directions

I explored multiple layout directions focused on balance visibility, transaction context, and workflow clarity. Each concept tested different approaches to grouping financial information, simplifying navigation, and helping users scan important details faster.

Exploring different dashboard concepts focused on hierarchy, transaction visibility, and clearer everyday financial workflows.

Ultimately I designed the interface around the following four pillars:

01

Ease of Use

Designed intuitive workflows that allow users to quickly complete receiving tasks with minimal training and fewer interactions.

02

Automation

Reduced manual entry and repetitive actions by leveraging system-driven processes, validations, and intelligent defaults.

02

Familiarity

Built on patterns, terminology, and workflows that users already know, helping drive adoption and confidence.

03

Standardization

Established consistent processes, layouts, and interactions to support efficiency, reduce errors, and enable scalability across facilities.

Designs

Refining the dashboard experience

The final designs focused on simplicity and ease of use. The final redesign focused on improving clarity across everyday financial tasks through stronger hierarchy, simplified navigation, and more contextual transaction feedback. The updated interface made balances easier to compare, actions easier to locate, and activity flows easier to understand at a glance.

Emphasis here on the ..sd.f askdfj askdlfj askldfj askldfj asdf

01

Clearer balance hierarchy

Balances became easier to distinguish through improved grouping, spacing, and visual separation.

02

More contextual activity flows

Transaction details, merchant information, and payment states were surfaced earlier to reduce uncertainty before actions.

03

Simplified navigation patterns

Important actions became easier to locate through clearer layout structure and more predictable workflow organization.

Experience Designer

The designs for the finance and accounting dashboards were a significant departure from the way they do things today.

Lessons

Designing for clarity, confidence, and everyday financial workflows

This project reinforced how strongly financial confidence is shaped by interface clarity rather than financial complexity itself. Throughout the redesign, I explored how hierarchy, spacing, and contextual feedback could reduce uncertainty during everyday financial tasks. One of the biggest learnings was recognizing how small interface decisions — such as grouping, transaction context, and action placement — significantly influenced how users interpreted information and navigated the product.

Key outcomes

Clearer hierarchy

Improved separation between balances, transactions, and supporting details.

Faster dashboard scanning

Reduced visual competition across key financial workflows and actions.

More contextual activity

Introduced transaction states, merchant context, and clearer activity flows.

Scalable design system

Created reusable dashboard patterns and modular workflow structures.

Create a free website with Framer, the website builder loved by startups, designers and agencies.