Case Study
Fix the Rush
A POS bill-splitting experience designed to help restaurant servers divide complex bills quickly, accurately, and with clear confirmation at every stage.
Problem
Splitting a restaurant bill becomes error-prone when multiple seats, shared items, modified orders, cancellations, and different payment groups need to be handled together. The flow needed to reduce manual work while keeping every assignment visible.
Design Goals
- Let servers assign seats and items with minimal interaction.
- Keep bill ownership and totals visible throughout the flow.
- Make exceptions and modified items visually obvious.
- Provide a clear review-and-confirm step before generating bills.
Process
Design process
- 01
Empathize
Understand server workflows, POS constraints, rush-time pressure and common bill-splitting errors.
- 02
Define
Frame the problem around speed, accuracy, visibility and recovery from mistakes.
- 03
Ideate
Explore seat-to-bill assignment, bill grouping, item movement and confirmation patterns.
- 04
Design & Prototype
Create tablet-first high-fidelity UI with clear bill identities and persistent totals.
- 05
Testing
Validate assignment clarity, error visibility, review flow and confirmation confidence.
Key UX Outputs
Stakeholder insights · Problem framing · Information architecture · User flows · Wireframes · High-fidelity UI · Interactive prototype · Usability feedback
Design Decisions
Style guide
- Primary Green#106040Primary action / confirmation / product identity
- Supporting Green#208050Secondary positive emphasis
- Bill Blue#2563EBBill/category identifier
- Bill Amber#D97706Bill/category identifier
- Bill Plum#A85578Bill/category identifier
- Error Red#B91C1CModified / critical exception
- Neutral#F5F5F4Background / structural surfaces
- White#FFFFFFCards / content surfaces
Approach
Design principles
Hierarchy
Use size, weight, spacing and contrast to make the next action or most important information obvious.
Consistency
Repeat components, states, spacing and interaction patterns so users can build familiarity.
Accessibility
Maintain strong text/background contrast and avoid relying on color alone to communicate status.
Feedback
Make changes, exceptions, success and confirmation visible at the moment they happen.
Content clarity
Prefer concise labels, meaningful status language and progressive disclosure over dense explanation.
See every screen, state and interaction behind the Fix the Rush interface in the full Figma file.
Explore the full design in FigmaMore Work
