3 min read

Turning disconnected grant tools into one trusted platform

Client
Gretchen Swanson Center for Nutrition, for the USDA-backed Nutrition Incentive Hub
My role
Lead product designer
Timeline
8 months
What changed
One portal and reporting platform replacing spreadsheets and legacy tools
Nutrition Incentive Hub Platform

Overview

Nutrition Incentive Hub

A USDA-backed coalition supporting nutrition incentive and produce prescription projects. It connects practitioners, researchers, and program administrators to build stronger, more effective programs that put healthy food on the tables of families who need it most.

The problem

The network ran on old software, spreadsheets, and workarounds, and no two of them agreed. Grantees spent more time chasing paperwork than running their programs. The administrators helping them spent their days on that same paperwork, with no way to tell which programs were actually working.

The solution

I led the design of one portal and Power BI platform to replace all of it, with accessibility (WCAG 2.1 AA) and a documented design system built in from the start. Instead of hunting for the current version of something, grantees and administrators could open one place and trust what they found there.

My approach

Research-led product design for a federal coalition

The path from talking to people and mapping their days to a working portal, accessibility standards, and a documented design system.

User Experience Design Process

Size of circle = Amount of effort

1

Research

Before designing anything, we needed to understand where the friction actually lived. We paired a system audit with stakeholder interviews and journey mapping to capture how grantees, administrators, and researchers experienced the network day to day. The data told us what was slow. The interviews told us what was stressful, and the two rarely pointed at the same thing.

System audit & analysis

System audit & analysis
What we discovered
  • Found where the spreadsheets slowed everyone down
  • Matched federal reporting rules to what the system could do
  • Documented every tool in use, to replace the paper trail

Stakeholder inquiry

Stakeholder inquiry
The human truth
  • Interviewed users to find what wore them down
  • Made the case for one live portal
  • Found where people got lost while applying

Persona development

Persona development
Building empathy
  • Built personas for every kind of user
  • Named the groups having the hardest time
  • Gave developers real people to build for

Journey mapping

Journey mapping
Mapping pain points
  • Mapped the trip from applying to getting funded
  • Marked the moments people got confused
  • Added help where people needed it most
2

Information architecture

A coalition this size accumulates content faster than anyone can organize it. We restructured the information around how people actually look for things, not how the organization happened to be filed. The goal was simple: anyone, from a first-time grantee to a seasoned administrator, should be able to find what they need without already knowing where it lives.

Strategic content org

Strategic content org
Making complexity simple
  • Renamed things the way people actually say them
  • Put every resource within two clicks
  • Built room for the network to keep growing

Workflow optimization

Workflow optimization
Removing friction
  • Reduced processing time from 45-55 hours to just over 10
  • Mapped the decision paths so no one hit a dead end
  • Connected what grantees submit to what reviewers see
3

Visual design

Public-sector tools often feel cold, and that coldness quietly tells people the system wasn’t built for them. We developed a visual language that balanced the authority a federal program requires with the warmth its community deserves. Consistency here wasn’t about looking polished. It was about making the platform feel trustworthy and calm under the weight of real work.

Conceptual exploration

Conceptual exploration
Finding the right balance
  • Balanced federal authority with a human feel
  • Tried directions that met the rules and still felt usable

Prototyping & validation

Prototyping & validation
De-risking the design
  • Tested assumptions on rough screens first
  • Applied WCAG standards from the first draft
  • Filled out the forms ourselves to find the errors
4

User interface

The last layer was making the system durable. We built a component library and design system so the platform could grow without fragmenting again. Every pattern was documented, checked against WCAG 2.1 AA, and handed to the development team ready to use, so the clarity we designed would outlast the launch.

Digital design system

Digital design system
The foundation
  • Built one grid that works on any device
  • Defined what the screen says back, so no one is left guessing
  • Built accessibility into the foundation

Scalable component library

Scalable component library
Built to last
  • One place designers and developers both work from
  • Handed over specs ready to build
  • Designed small components that combine into new screens

The impact

Dimension
Outcome
Operational velocity
Reduced data analysis request processing from 45-55 hours to just over 10, freeing analysts for higher-value work.
Data integrity
Cut data checking and validation time roughly in half while meaningfully reducing submission errors.
Rapid scale
Nearly doubled the number of grantees served by the platform without adding analysts.
Network growth
Platform carries 135+ grantees and 200+ grants across the U.S., sustaining 200,000+ page requests a week and 450,000+ metrics captured a year.

One platform carrying 135+ grantees and 200+ grants, at 200,000+ page requests a week. Administrators got their time back. Grantees could trust what they were reading. And the network finally had room to grow.

Next case studyGiving dispatchers one real-time view of a 450+ truck fleet →