Case studies

The problem

In a volunteer-run group, important events, reminders, sign-ups, resources, and group information can become scattered across messages and difficult for members and volunteer leaders to keep track of. Leaders end up re-answering the same questions, and members miss things that were announced somewhere.

I am in my fourth year as a member of CCC MomCo and am serving as a Table Leader this year, so I knew the problem from both sides: the member who missed a detail and the leader who sent it three times.

What I built

A mobile-first community information and event platform built for one local chapter of approximately 55 members. It centralizes events, reminders, sign-ups, resources, and group information, and it supports different experiences and administrative workflows for members, table leaders and mentor moms, and coordinators.

Because most of the people using it are volunteers with limited time to learn another tool, I created separate interactive onboarding experiences for each user group covering product use, mobile access, leadership workflows, and administration. Adoption was a design requirement, not an afterthought.

Member experience

Saved to the phone home screen like an app. Three tabs: upcoming events with flyers, map links, and add-to-calendar; pinned reminders with links; and the table directory.

Leader experience

Table leaders and mentor moms update events and reminders from their phones through a shared Google Sheet and a Google Form. Changes appear within minutes without touching code.

Coordinator workflows

One shared calendar feeds five table pages, each with its own colors, icon, reminders, and roster, plus a leadership view for the people who run the chapter.

Role-specific onboarding

Interactive walkthroughs for each role, so people can start without a training session.

My role

Workflow design, information architecture, role-based UX, onboarding design, documentation, AI-assisted development, and the volunteer adoption work that follows a launch. I built it as a member of the organization, not as an outside vendor, and I maintain it alongside the leaders who use it.

The problem

During weight-room training, one coach supervises multiple groups of athletes while simultaneously tracking time, rotations, exercises, repetitions, and whistle cues. Every one of those is a small operational task, and together they fill the whole session.

Those repetitive demands compete with the work that actually requires a coach: encouragement, form, technique, and safety. A coach watching a stopwatch is not watching a lift.

Before and after

What I built

A visual and audio coaching assistant built to support a high school coach. It displays the current movement and station information, provides visual cues, manages workout timing, handles work and rest transitions, provides audio cues, and blows the whistle automatically at the appropriate time.

It is now used daily across five classes as well as the football and weightlifting programs.

How it works

1. The coach selects a workout. Each workout is a sequence of stations with set work and rest periods.
2. A large display shows the current movement, the station rotation, and a countdown that athletes can read from across the room.
3. Visual cues change as a segment nears its end, and the app plays audio cues and the whistle at the exact transition.
4. Work and rest transitions, rotations, and repetitions advance automatically, so nobody has to watch a stopwatch.

My role

I observed the coaching workflow, translated it into product requirements, designed the user experience, used AI-assisted development to build it, tested it against real sessions, and refined it based on the coach’s feedback.