Modernizing Dairy Movement, End to End

Extending an end‑to‑end dairy platform to the road—giving drivers a focused mobile tool that fits how they already work while improving accuracy, quality, and visibility for producers, cooperatives, and processors.

Client:

Milk Moovement

Role:

Lead UX Designer

Year:

2021 - 2022

Header for landing page to boost website traffic

The Challenge

Milk Moovement is a broader web platform used by cooperatives, producers, and processors to manage the dairy supply chain, including quality tracking and compliance. Yet many day‑to‑day moments still relied on paper, phone calls, and disconnected tools—especially for truck drivers on the road. Contracted drivers used their own navigation tools and internal systems, and office teams needed accurate, timely data to flow back into the desktop experience to uphold quality and safety standards without adding friction to anyone’s workflow.


This case study focuses on the mobile app that connects into that larger platform, giving drivers a contextual, on‑the‑go companion that fits into how they already work. The challenge was to design a mobile experience that could integrate with third‑party tools, capture critical quality and load data in real time, and enhance visibility and compliance for everyone across the web and mobile ecosystem.

Laptop mockup with the website home page

Process

We began by mapping the end‑to‑end journey of a load of milk across both the web platform and the field workflows it supports—from scheduling and planning in the office to pickups, quality checks, deliveries, and intake at the plant. Ride‑along style discovery with contracted drivers, along with interviews with producers and plant staff, helped us understand how personal navigation tools, in‑cab routines, and existing internal systems shaped behavior on the road.


These insights informed role‑specific flows that clearly separated what belonged in the mobile app versus what remained better suited to the desktop experience. We used low‑fidelity prototypes to validate key tasks like creating and completing pickups, recording volumes and temperatures, capturing sample identifiers, and syncing with the platform—accounting for intermittent connectivity and the need to keep interactions fast and glanceable. As fidelity increased, we focused on ensuring that mobile actions would reliably update the web app and downstream tools, supporting quality control, traceability, and regulatory requirements without adding configuration overhead for drivers.

Solution

The mobile app now acts as a focused, on‑the‑go extension of the Milk Moovement web platform rather than a stand‑alone product. Drivers can manage pickups and deliveries, capture structured data such as volumes, temperatures, and sample barcodes, and sync that information back into the system in a way that aligns with their existing navigation and dispatch tools. The app is designed to sit alongside their preferred mapping or telematics solutions, not replace them, while still ensuring the platform receives consistent, high‑quality operational and quality‑related data.


On the desktop side, office staff, producers, and processors gain real‑time visibility into what is happening on the road: upcoming loads, status updates, quality metrics, and exceptions are all informed by actions taken in the mobile app. This improves coordination, supports faster responses to potential quality issues, and strengthens adherence to safety and compliance standards across the network. The result is an end‑to‑end experience where mobile and web work together—drivers get a lightweight, contextual tool that respects how they already operate, and the wider organization benefits from a more connected, data‑rich view of the supply chain.

The home page header and footer
The footer of the home page

Key takeaways

This work reinforced a few core principles for designing within a connected, quality‑sensitive platform:


  • Mobile should extend and complement the desktop platform, not duplicate it—especially when users already rely on their own tools in the field.

  • Role‑specific experiences create clarity; drivers, office staff, and processors each need focused workflows that still feed a shared, trustworthy source of quality and operational data.

  • Integrations with existing navigation and internal systems are as critical to adoption as UI polish when working with contracted drivers.

  • The most effective operational tools feel lightweight in use but quietly power richer, real‑time insights into performance, quality, and compliance across the broader web platform.