ROLES: LEAD PRODUCT DESIGNER

Designing a Unified Experience for Every Fundraiser Hero 

Booster—the fundraising company known for turning laps into dollars—needed a serious glow-up for its internal Admin Dashboard. With different user types (admins, teachers, client care consultants, KDMs, and campaigners) all logging into the same space, we knew it was time to bring clarity, cohesion, and capability to the forefront.
I lead the experience with our Tech Team to create a unified application that supports every user journey within mybooster.com. The result? A living, breathing Beta product shaped by over a year of design, research, and user feedback from 80+ participants. It’s not “done”—but that’s the point. We're building something that evolves alongside our users.

The Problem

Booster’s Admin Dashboard was...well, not exactly a “dashboard.” More like a series of screens duct-taped together with good intentions and confusing navigation.

The Challenges:

  • Multiple user types, multiple needs, one outdated system
  • No unified flow across campaign setup, management, or reporting

  • Old to non-existent design system

  • Zero responsiveness (mobile? what mobile?)
  • Confusion across the board—especially for Customer Care Clients and KDM's just trying to launch a fundraiser
We weren’t just redesigning a dashboard—we were redesigning how people felt about running a fundraiser.

Journey Mapping the Chaos

Before we could fix anything, we had to see everything. We dug into the current workflows for every user type, mapping out:

  • Entry points (from emails, links, logins)
  • Campaign setup paths
  • Daily tasks (like tracking donations or sending reminders)
  • Support routes and where users got lost
Takeaway: Everyone had their own path… and none of them intersected in a meaningful way.

Sketch. LoFi. Rinse. Repeat.

We started light:
  • Sketching out layout ideas by hand
  • Prioritizing navigation and responsiveness
  • Building rough LoFi wireframes focused on flow over flair

We tested. And white-boarded. Then tested again. Each round with a focus group of real users. Each round brought us a little closer.

Research, Testing & Real Talk

From day one, we embedded users into the design process—because you can’t build the right thing unless you talk to the people who’ll use it.

Here’s how we stayed grounded in reality:

  • Engaged 80+ participants through moderated and unmoderated testing

  • Held weekly reviews with Tech and Support to catch issues early and align across teams

  • Built feedback loops into every design milestone—from wireframes to prototypes to the live Beta

And here’s what all that listening taught us:

  • Mobile-first isn’t optional—it’s essential. Teachers and campaigners needed to take action on-the-go, not just from a desk.

  • Admins crave flexibility. They’re juggling multiple campaigns, users, and goals. The dashboard had to adapt to them, not the other way around.

  • Small UX touches make a big difference. Progress indicators, friendly prompts, and intuitive flows gave users confidence at every step.

The Beta Launch

We soft-launched the new Booster Admin Dashboard as a Beta in Spring, and the response blew us away:

  • 90% of Beta users said they didn’t want to go back to the old dashboard

  • Many asked us to “just throw them in” to the new experience—bugs and all

  • 75% of the Clients noted that even in progress, this new system made them more likely to rebook for another year!

  • “It’s like Booster actually listened to all our feedback—and built a system around it.”

Post-Beta Research: Feedback Is Fuel

Even when feedback was glowing and the Beta was a hit—we didn’t stop there. 🚀 Because good design isn’t about just shipping. It’s about listening, learning, and evolving.

After launch, we selected 10 clients from across the country—different roles, regions, and tech comfort levels—to go deep with us in moderated usability sessions. Why? Because real-world context > assumptions.

Their voices didn’t just shape our roadmap—they redirected it.

  • 100% of participants asked for more granular reporting—specifically the ability to filter by time and date.

  • We discovered every client was taking screenshots of our dashboard to share with parents and teams—so we immediately rethought how we design widgets, export options, and shareable views.

  • Their feedback reframed how we think about context, communication, and clarity across the entire system.

And like we said—we’re not done. This wasn’t the end of a project. It was the beginning of a better way to build: one where our users are at the table every step of the way.

The dashboard will continue to grow—because our users do.