2024 · UX Researcher & Product Designer
Resy Celebrations
A large-party booking feature for the Resy platform
The Problem
Booking for 8+ people on Resy ends the same way every time: an email. Users wait days for back-and-forth clarification on minimums, floor plans, and menus. Restaurants spend hours on coordination they could automate. The Celebrations feature closes that gap.
Role
Co-lead researcher on a 4-person team. I led the research plan, conducted user and restaurant manager interviews, and co-designed the Celebrations feature concept.
Timeline
8 weeks
Tools & Methods
- Figma
- User interviews
- Competitive analysis
- Journey mapping
- Affinity mapping
Dual-Perspective Research
I interviewed both sides of the transaction — NYC users (students and young professionals) and restaurant managers at three Brooklyn restaurants. This revealed a fundamental mismatch: users wanted instant transparency, restaurants needed structured context before committing. Neither the current email workflow nor the app's hard cap at 6 seats served either side.
What Users Needed
Minimum spend, floor plans, and sample menus visible before reaching out
One-click confirmation comparable to a regular reservation
Budget filters to compare restaurants without hidden-cost surprises
Confidence that their date won't disappear during email delays
What Restaurants Needed
Event type upfront — a birthday and a corporate happy hour require different staffing and layouts
A structured intake form in-app instead of open-ended email threads
Protection from last-minute cancellations that cost thousands in missed turnovers
“If guests saw pricing and policies before emailing us, that would filter out groups who aren’t serious.”
The Solution
Celebrations is a dedicated section within Resy for 8+ reservations. A filterable restaurant grid surfaces spend minimums, event policies, and sample menus upfront. A structured inquiry form — party size, event type, dietary needs, budget range — replaces the email chain. Restaurants respond through Resy's dashboard, keeping the full loop in-platform.
Research Validation