Case study

Making diabetes prevention data easier to manage
without starting over

The National Kidney Foundation of Michigan needed a better way for diabetes prevention coaches to submit participant data and for administrators to manage it. I led the UX strategy and design of a two-sided portal that simplified those workflows while working with the organization’s existing reporting infrastructure.

Connecting coaches, administrators, and program data.

Project at a glance

My role

UX Strategy & Design Lead

Industry & Client

Healthcare technology · Nonprofit

Methods

Stakeholder discovery, requirements analysis, workflow mapping, information architecture, wireframing, prototyping, moderated usability testing

Scope

Two role-specific interfaces · Shared portal database · 6 usability testing participants

Outcome

UX strategy, research, and design led by me through Standard Beagle Studio, with technical architecture and implementation by our development team.

The challenge

Spreadsheets worked. Until they didn’t.

The National Kidney Foundation of Michigan relied on spreadsheets to collect participant data for its diabetes prevention programs. As information changed and revisions accumulated, managing submissions became increasingly difficult.

Administrators needed consistent data for grant reporting, but replacing the organization’s existing database wasn’t feasible within the budget. The challenge was to improve the workflow without overhauling the infrastructure.

Why it was complex

Two distinct workflows

Coaches needed to manage participant information and submit updates. Administrators needed to set up workshops, review submissions, and prepare reporting exports.

Existing infrastructure

NKFM already relied on a Microsoft Access database. Direct integration would have been costly and unnecessary for the initial product.

Real-world flexibility

Workshops didn’t always follow a fixed schedule. Coaches needed to accommodate holidays, weather cancellations, and rescheduled sessions.

Doodle of a puzzled character with a question mark.

Can we improve the workflow
without replacing the
whole database?

Research & discovery

Understanding the work before designing the system

I began with the project’s requirements and stakeholder discussions to understand what each user group needed to accomplish.

Rather than starting with screens, I mapped how information would move through the program—from administrators setting up workshops, to coaches collecting data, to administrators preparing reports.

Staff workflows

I mapped how staff would create and publish workshops, manage participant records, review submitted information, and export data for reporting.

Coach workflows

I defined how coaches would access assigned workshops, update participant information, change session dates, and submit completed data.

Technical collaboration

I worked with our developers to understand what was feasible within the budget, existing infrastructure, and healthcare data security requirements.

Key insight

“Coaches need flexibility, while administrators needed consistency.”

Coaches needed to update participant records and adjust schedules as workshops unfolded. Administrators needed complete, reliable information for grant reporting. Exchanging spreadsheets made it difficult to keep those needs aligned, particularly when information changed or submissions needed review.

Design response

Two connected experiences, designed around different needs

I designed the workflows, wireframes, and interactive prototypes for both interfaces, focusing on the tasks coaches and administrators needed to complete.

Simpler workshop setup

Administrators could import workshop data, review records, and publish workshops without entering everything manually.

Flexible coach workflows

Coaches could manage participant records, adjust session dates, and submit data as workshops changed.

Clear submission states

Submission indicators helped users distinguish between saved, submitted, and pending information.

Outcome

A practical solution that grew with the program

Following six moderated usability tests with diabetes prevention coaches, I refined the submission workflow to address confusion around labels and status indicators. Most participants completed the core interactions, but testing helped pinpoint where the experience needed clearer feedback.

I incorporated those findings into the final designs before Standard Beagle’s development team implemented the portal. The result was a practical way for coaches and administrators to manage program information while continuing to use NKFM’s existing reporting infrastructure.

Validated workflows

Most participants completed the key interactions, with testing informing refinements before development.

HIPAA-compliant application

The team delivered a working portal connecting coach and administrator workflows.

Expanded adoption

Initially supporting a handful of workshops, the portal grew to support dozens as program needs evolved.

What this shows about my work

Knowing what to change matters as much as knowing what to keep.

Pragmatic strategy

Finding workable solutions within existing budgets, systems, and technical constraints.

End-to-end UX

Leading workflows, wireframes, prototypes, and usability testing through development handoff.

Designing across roles

Balancing coaches’ need for flexibility with administrators’ reporting requirements.

Built to evolve

Creating a foundation that supported broader adoption and ongoing improvements.