Talk with restaurant teams
Bar Tabs includes interviews with 15 waitstaff and managers, customer sessions, competitive research, Smart Serve training, and work behind a bar.
See the field research →For product design hiring teams
Restaurant problems.
Evidence to release.
I design restaurant software with the people who use it, then stay close through testing, implementation, and release.
Best place to start
Bar Tabs
The clearest end-to-end story of field research, prototypes, testing, and shipped work.
Open Bar Tabs →Role evidence
The work matches the full product cycle.
Each point below links to the case study with the strongest proof.
Make ideas testable early
Kiosk quantity controls moved through five concepts, eight refinements, paper tests, hardware trials, two voting rounds, and one shipped rule set.
See the Kiosk test →Stay through implementation
POS and Backoffice work records responsive rules, component behavior, engineering handoff, staged releases, and build review.
See shipped platform patterns →Learn the operating system
The work connects POS, Kiosk, Bar Tabs, and Backoffice. Each decision accounts for permissions, hardware, service states, and connected workflows.
Compare the four products →Use AI inside the work
I use connected sources to synthesize research, compare concepts, check current product rules, build prototypes, and preserve decisions.
Read the AI practice →Return patterns to the system
The shared POS keyboard, responsive guidance, Menu Management components, and navigation rules reduce repeated design and engineering decisions.
See the component decisions →Show what changed
Bar Tabs shows how expert feedback changed bill splitting. Kiosk shows five concepts, hardware testing, team voting, and the chosen rule.
See a decision change →Separate scale from impact
The case studies name released work and open measures. Kiosk and POS report dated product scale without claiming that one design caused it.
See the result boundary →Suggested reading path
Four pages. Four kinds of proof.
01 · Research and service pressure
Bar Tabs
Start here for interviews, field learning, prototypes, usability sessions, and shipped Phase 1 work.
Open case study → 02 · Testing on real hardwareKiosk
Read this for accessibility, printed prototype testing, physical input, recovery, and production review.
Open case study → 03 · Systems and critiqueBackoffice
Read this for dense records, permissions, reusable components, rejected directions, and staged delivery.
Open case study → 04 · Platform and releasePOS
Read this for responsive rules, shared inputs, hardware states, engineering use, and released patterns.
Open case study →This guide follows the role focus in the 7shifts Product Designer posting, reviewed September 29, 2026.
Open my resume →