Ch2 03: What If Restaurants Never Brought You a Bill?#
You’ve just had a great dinner. The food was perfect. The conversation was even better. You’re ready to leave. And then you wait.
You wait for the server to notice you. You wait for the check. You scan the check. You drop your card. You wait for the server to circle back. You wait for the card to process. You sign. You calculate the tip. You sign again.
The last fifteen minutes of a restaurant experience are, almost universally, the worst fifteen minutes. And they’re entirely unnecessary.
The restaurant industry has been polishing the check-paying process for decades. Tablet payments at the table. QR code menus with built-in checkout. Mobile wallets. Split-bill apps. Every one of these innovations makes paying the check faster. None of them asks the more fundamental question: why does the check exist at all?
This is the gap between Level 1 thinking and Level 3 thinking. Level 1 asks: “How do we speed up this step?” Level 3 asks: “What if this step didn’t exist?”
The distance between those two questions is where the most dramatic gains live. Optimizing a step delivers incremental improvement — ten percent faster, twenty percent cheaper. Eliminating a step delivers order-of-magnitude improvement, because you’re not just saving the time the step consumes. You’re erasing every cost, every failure mode, every friction point, and every customer who ever bailed on the experience because of that step.
Zumi, a company in the DVx portfolio, took the Level 3 route to restaurant payments. Their model: you scan a code when you sit down, linking your payment method to the table. You order. You eat. When you’re done, you stand up and walk out. The system charges your card automatically. No check. No signing. No waiting.
The step didn’t get faster. It vanished.
The obvious win is speed. Tables flip faster because diners don’t burn fifteen minutes at the end waiting to pay. For a restaurant running at capacity on a Friday night, that’s a straight shot to more revenue — one or two extra seatings per table per evening.
But the less obvious win is the one that matters more. When you kill a friction point, you don’t just make the existing experience faster for the people already completing it. You also recover all the people who were quietly opting out because of that friction.
Think about how many times you’ve skipped a restaurant because you “didn’t want to deal with the whole paying thing.” How many times you’ve rushed through the end of a meal because you dreaded the checkout ritual. How many times a clunky payment experience soured your memory of an otherwise outstanding dinner.
These are invisible losses. No restaurant can count the customers who didn’t come back because the payment process was a drag. No survey captures the slow bleed of goodwill during those awkward fifteen minutes. But the losses are real, and they’re large.
When the friction disappears, some of those lost customers return. The direct efficiency gain — faster table turns — might be worth twenty percent more revenue. But the indirect demand recovery — customers who now visit more often, linger longer, and leave happier — can be worth three to ten times that.
This pattern isn’t unique to restaurants. Every industry has steps that exist because “that’s how it’s always been done,” not because they add value for the customer.
Ask yourself: which steps in your process would the customer pay you to remove? That question flips the usual optimization lens on its head. Normally we ask which steps the customer values. The inverse — which steps would the customer pay to skip — pinpoints the friction that’s silently destroying value.
The hotel checkout. The insurance claims form. The rental car return. The employee onboarding paperwork. In each case, the step exists to serve the organization — accounting, compliance, asset tracking — not the customer. And in each case, technology has made it possible to meet the organization’s needs without imposing the step on the customer.
There’s a mental trap that blocks most people from Level 3 thinking. I call it the existence anchor — the bias that treats the current shape of a process as proof that every step in it is necessary. If a step exists, our brains assume it must be there for good reason. After all, smart people built this process. If the step could be cut, someone would’ve cut it already.
But that reasoning is circular. The step exists because nobody removed it. Nobody removed it because everyone assumed it was necessary. And everyone assumed it was necessary because it exists.
Breaking the loop takes a deliberate act of imagination: pretend the step doesn’t exist, then ask what would actually go wrong. Not theoretically. Practically — based on what you know about your customers and your operations.
In Zumi’s case, the answer was: almost nothing. The restaurant still gets paid. The customer still gets a receipt (via email). Tax and accounting records still generate. Tipping still works. Every legitimate function of the check-paying step is accomplished — just without the step.
Guidance#
Take your core customer journey and list every step, start to finish. For each, run this test:
-
Does the customer value this step? Not “tolerate” — actively want. If not, it’s a candidate for elimination.
-
What happens if it simply vanishes? Picture tomorrow morning: the step no longer exists. What breaks? Be specific. “Compliance issues” isn’t specific enough — name the exact regulation, exact requirement, exact risk.
-
Can the step’s purpose be served invisibly? Many steps do real work — accounting, verification, compliance — but that work can often happen backstage, without the customer lifting a finger.
The highest form of deletion isn’t removing waste from a process. It’s removing a process from the customer’s experience entirely, while still accomplishing everything the process was built to do.
Get this right, and the customer doesn’t notice something got faster. They notice something unpleasant simply stopped happening. That’s a very different — and much more powerful — kind of improvement.