Thriver — three pillars, one design system.
Senior Product Designer across three concurrent product surfaces — a customer-facing marketplace, a vendor onboarding portal, and an internal CRM — while owning the design system that held them together.
Snapshot
Scope
Problem
Three product surfaces had grown independently with conflicting patterns. Customers needed an explorable marketplace, vendors needed efficient management tools, and ops needed a unified CRM.
What I led
Owned the design system across all three pillars. Designed the customer marketplace from scratch — category exploration, collections/favoriting, programs. Mentored junior designers across the team.
Outcome
Bloom + Super Thriver design systems shipped, supporting the three pillars with shared tokens and components. Marketplace launched with category nav, filters, and a Collections feature for saved bookings.
Customer marketplace — category, filter, find.
The customer portal needed to handle a deep multi-category catalog (wellness, food, virtual, etc.) without burying anything. The design problem: how do you make a 4-level taxonomy feel like a guided tour, not a tax form?
Collections — shared favoriting for teams.
Thriver's customers are typically HR or office leads booking on behalf of their team. A single user saving favorites privately wasn't enough — they needed a way to gather options, share with collaborators, and decide together. Collections turned a personal favoriting pattern into a team workflow.
Saved is a feature; shared is a product.
Most marketplaces treat "favorited" as a personal-bucket feature. For Thriver's audience — group bookers — the value only appears when the bucket can be shared. The collaborator modal sits at the top of the IA inside a collection, not buried in settings, because sharing is the action that converts, not an afterthought.