Superb
About
Block Online Reservations — giving restaurant managers control without calling support.
Year
2022
timeline
3-4 months
What I did
Led the design process end-to-end
Team
Product Manager, Frontend Engineer, Backend Engineer
The Problem
Superb's platform lets guests book restaurant tables online, or lets restaurant staff create reservations manually. When a restaurant needed to close (a table, a room, or the whole place for a day), managers had two disconnected ways to do it: a blunt option from the main Dashboard, or a more granular but confusing "Rule" builder buried in Settings. Neither was intuitive enough — most managers gave up and called the CX team to do it for them, adding real cost and workload on the support side.
My Role
I led the design process end-to-end — from problem framing through a tested, ready-to-ship solution — working closely with a PM and two engineers (frontend and backend) to scope what was technically feasible and design something restaurant managers could actually use without help.
How I approached it
→ Audited the two existing closure paths (Dashboard vs. Settings/Rules) to understand why managers defaulted to calling CX instead of self-serving → Designed a single, flexible modal that could handle both simple closures (a day, a table) and more complex recurring rules, replacing the fragmented two-path system → Usability-tested the new modal with real restaurant managers
What we validated
Managers who tested the new modal completed closures faster and with noticeably more confidence than with the old flow — several commented directly that they'd no longer need to contact support for something this simple. That signal gave the team strong conviction the redesign would meaningfully reduce CX load and improve manager self-sufficiency. This was ready for rollout when my role at Superb ended.
More works
