All projects
May – August 2026

Volunteer Respite Event Portal

Client
Tennessee Caregiver Coalition
My role
Product Manager
Project tools
FigmaClaude + Figma MCPNotion
Team
10-member UX team

01Project Overview

Tennessee Caregiver Coalition (TCC) connects caregivers with volunteers to provide respite care through bi-monthly community support events.

Problem

The existing platform created unnecessary friction for caregivers, volunteers, and staff.

Solution

A unified registration and event management platform tailored to three user groups.

My role

As Product Manager, I led a 10-member UX team through a 16-week project, translating research and stakeholder needs into MVP priorities and coordinating design, testing, and handoff while utilizing AI-assisted workflows.

02Research

Challenging our assumptions

Our initial audit suggested registration and navigation needed the most attention.

User research revealed a different set of priorities across caregivers and volunteers.

FigJam · Platform audit affinity map

What users told us

Across 10 interviews and usability testing sessions, we found that some workflows worked better for the people actually using them than our audit-based assumptions.

Registration wasn't universally difficult.

“I think the current registration process is pretty straightforward and easy to navigate.”
— 2-year program volunteer

The real problems lay in places we weren't even looking, like in the repeated, detailed intake forms caregivers had to deal with.

Repeated intake was exhausting for caregivers.

“No parent likes to fill these forms out... We just get tired of it.”
— Parent of child with autism

What the numbers revealed

Auditing the platform showed that volunteer training materials were buried behind several clicks, making a mandatory task harder to achieve. In fact, of 93 currently registered volunteers, 46 weren't marked as trained.

TCC staff explained that volunteers arriving unprepared create difficulties, particularly at Parents' Night Out events where volunteers work directly with children.

46/93registered volunteers weren't marked as trained

03Design

Making AI drafts usable

We used Claude with Figma MCP to explore concepts quickly, but the drafts still needed human judgment. One AI-suggested staff table seemed organized on the surface, but buried key actions like opening participant profiles.

75%
of user testers struggled to find key information or actions in the AI prototype
11 columns with important actions buried.
4 columns, clickable rows, and clearer status information.

Clarifying volunteer training

We made training progress visible in 3 ways: top-level reminder, progress bar, and organized status sections.

Training buried in existing site
Volunteer training progress

04Outcome

One platform, three experiences

Our final prototype separated workflows clearly so we could focus on what each user needed most, bringing relief to caregivers, clarity to volunteers, and control to staff.

Caregiver · Reusable profile
Staff · Reporting dashboard
Volunteer · Training progress

Handoff

We carefully annotated the high-fidelity Figma prototype and documented important UX decisions, client context, and product specifications to support TCC's development phase.

Next steps
  • Post-launch metrics. To measure real-world impact, I'd want to track registration & training completion and staff time spent on coordination tasks.
  • More testing. Outside the numbers, hearing feedback from real users across all 3 groups would provide new insights.
  • Automated communication. Setting up reminders and notifications would reduce manual follow-up. This could be an interesting place to integrate AI into the site!

05Reflections

i.

AI isn't a shortcut

This was my first larger project using AI-assisted prototyping, and it was pretty cool to see how fast we could churn out and test our ideas. However, I quickly realized AI didn't give us a “skip iteration” button, just a new way to get into the work!

ii.

The energy you bring matters

I was responsible for both delivering something great to our client and being a pillar for my team. By communicating openly, setting clear expectations, and leading with the same willingness to contribute that I hoped to see from others, I built a team culture where people felt comfortable asking for help and supporting each other.

iii.

Know what to leave alone

Our audit gave us plenty of things to redesign, but talking to actual users challenged some of those assumptions. I learned that knowing when to leave a good thing alone is just as important as knowing what to change.

Check out my other work!