When guests stopped carrying cash
Hotel guests stopped carrying cash. Housekeeping staff stopped getting tipped. The result was a retention crisis — and an opportunity to solve it.
Problem
The shift to cashless payments cut off tip income for hotel housekeeping staff, creating retention pressure for hotel operators in an already constrained labor market.
Role
Solo designer — led experience strategy and execution from discovery through launch, including research, feature scope, engineering partnership, and post-launch analytics framework.
Constraints
No app download or account creation. Payment processing rules required taxes and fees to be charged on top of the guest's selected tip amount — not absorbed into it. Individual employee attribution wasn't operationally reliable.
Outcome
Shipped as a native extension of our workforce management platform. Hotels could configure tipped departments, route payments within existing workflows, and offer guests a frictionless mobile tipping experience.
Research showed that hotel guests wanted to leave tips but were unable to do so because they no longer carried cash.
1. Context & problem
As hotel operations rebounded after COVID, operators faced a retention problem that wasn't immediately visible. Guest payment behavior had shifted almost entirely to cashless — but tip-dependent roles like housekeeping hadn't seen a corresponding change in compensation expectations. Guests wanted to tip but had no mechanism to do so.
For our clients, this created staffing pressure. For our platform, it was an opportunity to extend our workforce management product into a capability that directly addressed a client pain point — without requiring hotels to adopt a separate tool.
2. Constraints & scope
-
No app download or account creation — the experience had to work via QR code in a mobile browser
-
Taxes and fees couldn't be absorbed into the tip amount — legal constraints required them to be charged on top
-
Individual employee attribution wasn't operationally reliable — hotels couldn't guarantee which employee serviced a given room
-
Property-level configurability was required — hotels varied in how departments handled tips and pooling
-
The experience had to be short — tipping is an in-the-moment action, not a considered purchase
Our app supported common mobile payment methods, such as Apple Pay and Google Pay.
3. Research & insights
We ran guest surveys and usability testing with a small participant pool to validate demand, payment behavior, and trust concerns.
-
Intent existed — the mechanism didn't. Guests expressed willingness to tip housekeeping but had no convenient way to do so without cash.
-
Mobile-first behavior was universal. All participants reported regular smartphone use, confirming a QR-to-browser flow would meet guests where they already were.
-
Attribution influenced willingness to tip. Guests were more likely to tip when they trusted the money would reach the intended recipient. This shaped how we communicated department routing.
-
Feedback was an untapped opportunity. Guests wanted to recognize good service beyond payment — informing the addition of a lightweight department rating alongside the tip.
4. Leadership & influence
As the sole designer, I owned the experience end-to-end — from research and feature scope through engineering partnership and launch. I defined the feature scope in collaboration with Product, shaped implementation decisions with Engineering, and contributed to the rollout strategy across hotel properties.
I also established an analytics framework post-launch to track adoption, completion rates, and tip distribution — giving the business a way to measure impact over time rather than shipping and hoping.
Hotels appreciated the ability for guests to rate service staff. Service staff saw the app as a differentiator and a chance to let their work speak for itself in front of management.
5. Key decisions & tradeoffs
Department-level attribution over individual Research showed guests were more likely to tip when they trusted the money reached the right person. We explored associating tips with a specific employee's name and photo — but hotel operations couldn't reliably guarantee which individual serviced a given room. Misattribution would have eroded exactly the trust we were trying to build. We shifted to department-level routing with property configurability, which was operationally honest and still gave guests a clear sense of where their tip was going.
Transparent fee disclosure at payment, not upfront Legal constraints required taxes and fees to be charged on top of the guest's selected tip amount — we couldn't absorb them. Surfacing this too early risked discouraging completion before the guest was committed. Hiding it until the summary screen risked a trust-breaking surprise. We disclosed at the payment step — after tip selection but before confirmation — to preserve trust without front-loading friction.
Three preset tip amounts to anchor the middle Rather than an open amount field, we offered three preset options — deliberately chosen to bracket a target amount and make the middle option feel like the natural choice. The full screen was dedicated to tip entry to prevent mis-taps, and a large readout ensured guests could see exactly what they were selecting.
Added a rating layer to extend beyond payment Research surfaced that guests wanted to recognize good service, not just complete a transaction. We added a lightweight department rating at the end of the flow — giving hotels a service-quality signal alongside financial reward, and giving guests a way to express appreciation that felt more personal than a dollar amount.
6. Outcomes & reflection
Launch status: Shipped as a native platform extension. Feature scope, payment model, configurability, and rollout delivered as planned.
Post-launch measurement: Analytics framework implemented to track adoption, completion rates, and tip distribution over time.
The most interesting constraint was the one we couldn't design around — taxes and fees on top of the tip amount. We couldn't change the rule, so the design problem became purely about when and how to communicate it. Getting that timing right was the difference between a trust-building moment and a checkout abandonment.