% 100% left

Case study · Global food & beverage · Field sales

From stale dashboards to decisions in the field

Shipped · Live across North America · Details under NDA

My first programme at a global food and beverage company: turning a slow Power BI report into a native iPad app that 10,000+ field sales leaders rely on, and the month of research I had to argue for first.

Role
UX Architect & Design Manager
Timeline
2022–2023
Platform
Native iPad (iOS)
Scale
10,000+ field sales users, 315K+ storefronts
Suite
Four field sales apps, 2022–2024

The product, its screens and the client’s name are confidential. The cover is a wireframe redrawn with sample data, not the shipped design. Detailed screens are available on request.

Wireframe of the iPad dashboard: sample sales against plan, sales to plan and units, above the bottom five routes, channels and business units
The rep’s dashboard: today’s performance against plan, at a glance.

Opening

Field leaders were fighting their own tool

Every week, field teams in the company’s snack-food division make around 500,000 store visits across North America. The app serves the people who lead them, from District Sales Leaders (DSLs) and Key Account Managers (KAMs) to territory, zonal and account development managers. All of them have minutes per store to decide what to pitch, what to restock and what to fix. The tool meant to help them was a Power BI report.

It was slow. It needed a live connection in stores with poor signal. It took real training just to find the right number. Field leaders had learned to tolerate it.

When I joined the company in 2022, this was my first programme. The brief was simple: move the report to a native iPad app. It turned out to be the first of four. Through 2024, my team designed a family of four field sales apps that replaced about 40 separate tools, one app for each job.

  • Professional selling

  • Frontline leadership

  • Frontline execution

  • Account management

About 40 apps became four.

The call

I argued for a month of research first

Leadership framed it as a platform change. The more I looked, the more it looked like a user experience problem. A new platform meant new navigation, new terminology, new flows and a new mental model. If we didn’t understand how DSLs and KAMs actually worked, we would rebuild the same frustration on a newer screen.

So I proposed a month of structured research before a single wireframe. The concern was fair: a month meant later delivery and unplanned cost.

I reframed the question: what would it cost to get this wrong? I walked the business through three scenarios: the daily productivity lost by 10,000+ field leaders fighting a confusing interface, the training and support burden across 315,000 storefronts, and the risk of pushing a field workforce onto a tool that didn’t fit their day.

Put that way, an extra month looked cheap. They agreed.

A month of research turned out to be the cheapest insurance we could buy.

Research

Four findings changed the brief

I led the research and took it where the work happens: field visits, shadowing DSLs and KAMs in stores, contextual interviews and usability tests. Surveys and stakeholder interviews filled in the rest.

Four findings reframed the whole project:

  1. 01

    The words were wrong.

    Labels used internal business language that field teams didn’t use or recognise.

  2. 02

    The “standard” flows weren’t.

    Users routinely skipped multi-step sequences; there was no time for them mid-visit.

  3. 03

    Desktop logic failed on a handheld.

    Controls that made sense at a desk caused repeated mis-taps under pressure.

  4. 04

    There was no design system for tablets.

    The existing library was desktop-first and not iOS-native.

We logged every finding in a shared research synthesis, so product, engineering and data teams were designing for the same people.

Design

Every decision traced back to the field

Every design decision had to come with a reason that started with “because we found…”.

The app follows the store visit. I built the information architecture around the visit itself, with one step for each moment, in the order a field leader works.

  1. 01

    Plan

    Accounts on a map, and a route that lands in Outlook

  2. 02

    Prep

    The store’s sales, potential and trends

  3. 03

    Store walk

    Survey the store, log displays and promotions

  4. 04

    Recommend­ations

    What to act on today

  5. 05

    Conduct the sale

    A sell sheet, signed and shared

Action first, analysis one tap deeper. We rebuilt the information architecture from the field up, starting with what field leaders need during a store visit. Account health, visit priorities and sales trends became a scannable dashboard. What needed action came first; what needed analysis sat one tap away.

Offline-first. With engineering, we designed a sync model that keeps the latest accounts, routes and sales figures on the device, so the app works where the signal doesn’t.

Native and one-handed. Swipe, pull to refresh, tap targets sized for someone holding a tablet in one hand, and map-based account views for planning a route. Familiar enough to need no manual.

A design system built to scale. Reusable components, token-based theming and documented interaction standards, so engineering could grow the product without design becoming a bottleneck.

AI

Insights that say what to do next

Field leaders didn’t have time to dig through data for opportunities, so I proposed that the app bring them a weekly list instead. AI-generated cards flag a drop in market share, a service gap, unrealised store potential, unsaleables and products that sell well together.

Each card offers two choices: see the actions, or dismiss it. Actions that are accepted go straight into the sell sheet, so an insight becomes part of the pitch in a couple of taps.

Recommendations screens

Confidential. Available on request, with the client’s permission.

Request access

Data is only useful when it tells you what to do next.

Screens

Seven key screens, shared on request

Accounts, trends, promotions, route, survey, 3D display and sell sheet

Confidential. Available on request, with the client’s permission.

Request access

Delivery

Parallel tracks won the time back

To win back the time we’d spent on research, I ran the work in parallel tracks:

  • A design pod building flows and prototypes, every decision mapped to a finding
  • An iPad-native extension of the design system
  • Engineering and data teams involved from day one, with regular review cadences
  • Research re-engaged at every sprint release, so concepts were tested while they could still change

In Q1 2023 we piloted with 150 District Sales Leaders, using heat maps, click tracking, error logging and stress tests under real field conditions. What we learned went straight into the final refinement before rollout.

I also asked the team to write a 72-page product handbook, so knowledge transfers easily and new users get going with minimal onboarding.

Results

+53% satisfaction and an estimated $500M+ a year

By Q3 2023, the app was live for 10,000+ field sales users, bringing sales insights, streamlined store visits and in-store surveys into one app.

+53%

User satisfaction compared with the Power BI baseline

$500M+

Estimated annual efficiency gains (business analysis)

315K+

Storefronts covered across North America

CIO 100

Won by the business team for this programme (2024)

AspectBeforeAfter
PlatformPower BI (web)Native iPad app
OfflineNoneFull offline access
TrainingExtensiveMinimal: intuitive by design

Field leaders told us they spent less time hunting for data and more time with customers. That was the whole point. The programme was presented to the company’s executive committee, which is rare for a UX-led initiative, and the CTO gave me a certificate of appreciation (2023) for delivering the design vision.

Reflection

Listen first, then build

This programme taught me that a designer’s real leverage in a big company is winning the room before the work starts. Get that right, and you earn the time to get the details right.

Launching before you’ve listened is the most expensive design decision you can make. Making that case before the money is committed is one of the most important things a design leader does.