← All work
USDA Market News — aerial view of farmland with tractor and USDA logo

USDA Market News

Redesigning how American farmers find market data

Role
Principal Designer — UX/UI
Team
Solo designer with client PM & engineering
Timeline
12 weeks
Platform
iOS & Android
Outcome
V2 shipped to the App Store & Play Store in July 2022, expanding coverage from ~800 to ~1,500 market reports across 4 commodity areas. Crossed 10,000+ downloads within two months of launch.

The problem

The USDA Market News app gives farmers and producers free, unbiased price and sales data — the information they use to decide when to sell, what to charge, and where to ship. Six months after MVP1 launched, the feedback was clear: the data was valuable, but finding it wasn't. Users were confused by the "Reports near me" flow, couldn't filter a growing catalog of reports, and had no way to reach archived data.

At the same time, USDA wanted to expand the app from 800 Livestock, Poultry and Grain reports to nearly 1,500 — adding Cotton & Tobacco, Dairy, and Specialty Crops. A navigation model that was already straining would have collapsed under double the content.

The brief: redesign Market News V2 to absorb 2× the content while making the most-used flows — finding, filtering, and saving reports — dramatically easier, within USDA branding and accessibility standards.

Understanding the users

Market News serves working farmers, many in their 50s and older, who are experts in their business but not in mobile apps. Two things from research shaped everything that followed:

Usability testing of MVP1 (4 participants; sessions run by the client's team, synthesis by me) confirmed the pattern: 2 of 4 got lost in "Reports near me" and couldn't find the filter, and participants struggled with the calendar/archive entry point, which sat too close to the "more options" button to tap reliably.

Auditing MVP1

Five screens from the original MVP1 app showing dense lists, report details and calendar
MVP1: dense unscannable lists, a buried calendar, and no way to narrow 800 reports.

I ran a heuristic evaluation of MVP1 and a competitive analysis of Cattle Market Mobile (the client's benchmark). Out of ten heuristic categories, three issues drove the redesign:

Cattle Market Mobile app screens used for competitive analysis
Cattle Market Mobile set the bar for categorized navigation and favorites — but lacked filtering and archives, the exact gaps V2 could own.

Key design decisions

1 · Filters as the backbone, not a feature

Every major complaint — lost in "near me," 50 unfindable favorites, unreachable archives — was the same problem: no way to narrow a large set. Instead of bolting a filter button onto each screen, I made commodity preferences a first-class concept: users select their Commodity Areas and Market Types once, and that selection persistently scopes Home, Favorites, Subscriptions, and Archive search. A farmer who only cares about Cotton Forward Contracts never wades through Poultry auctions again.

2 · Archive search by year → month → day, not an endless calendar

Twenty years of reports were technically accessible but practically unreachable. I sketched multiple archive models — timeline scrub, calendar grid, faceted list — and landed on a stepped Year → Month → Report-date drill-down: it matches how farmers referenced archives in interviews ("Livestock in June 2018") and stays tappable for older users. The calendar-grid option failed exactly the tap-precision problem testing had flagged.

Hand-drawn low fidelity sketches exploring archive search, favorites and report detail patterns
Low-fi explorations of the archive and favorites models — the stepped drill-down (top right) won on tap size and mental-model fit.
Information architecture diagram showing onboarding flow into four report search paths
The revised IA: onboarding ends in commodity personalization, which feeds four ways to reach a report — location, commodity, state, or archive date.

3 · Green over blue: brand fit beat aesthetic preference

I designed two complete visual directions. The blue direction was minimal, modern — and initially the favorite. I recommended against it: blue has no anchor in USDA's brand or in agriculture, and it's the default of every generic data-viz app, so it made a government agricultural tool look like a fintech dashboard. The green direction kept USDA's identity, and I built the design system around it with AAA/AA contrast ratios to address the color-blindness feedback directly.

Alternative blue visual direction across calendar, preferences and favorites screens
The road not taken: the blue direction — cleaner at first glance, but off-brand for USDA and indistinct from generic data apps.

The shipped product

Final shipped V2 screens: calendar onboarding, commodity preferences, searchable favorites and report details
Shipped V2: commodity preferences set during onboarding scope every list in the app; Favorites are searchable by name or SLUG ID; archives are two taps away.

V2 launched on iOS and Android in July 2022. The app crossed 10,000 downloads within its first two months — while absorbing nearly double the content of MVP1 — and the filter-first navigation shipped as designed, surviving engineering QA without simplification.

What I'd push for next

Self-initiated exploration concepts: map-based area selector, date-range chips and tabbed subscriptions
Post-handoff explorations: a map selector with radius slider, quick date-range chips, and tabbed Subscriptions — my proposed MVP3 starting points.

After handoff, I kept exploring on my own time: a map-based area selector with a radius slider (replacing the confusing ZIP + radius input), quick date-range chips ("Last 15 days"), and tabbed Calendar / New Reports / Commodity views inside Subscriptions. These were cut from MVP2 by tech constraints, team bandwidth, and timelines — the right call then — but they're where I'd take MVP3, starting with the map selector, since location entry was the single most confusing interaction in testing.

What I'd do differently: push for testing with more than four participants earlier, and instrument the app at launch so V2's impact could be measured in task success rather than downloads.