The setting
's is cloud software that manages a restaurant's website, online ordering, customer records, point of sale, fulfillment and kitchen work. It serves restaurant owners and their guests.
A loyalty balance becomes a promise when the conversion reaches a guest.
A uniform launch protects the announced transition, while withholding uncertain conversions protects earned entitlements.
Who you’d be doing this for
“A regular showed me the preview and asked if dinner was free. I had to pull up her old rewards while the line grew.”
Kariuki Kirui · Restaurant owner · a character in this brief
Operates two restaurants with regulars who have accumulated loyalty points over several years.
What is at stake
Nine of 20 guests misread a loyalty conversion before 48,000 balances change. You weigh a uniform launch against verified promises that guests can spend.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- uniform transition vs verified entitlements
- simple balances vs conditional redemption
- release certainty vs irreversible promises
- broad preview coverage vs narrow audit coverage
Why Owner
Branded apps and lifecycle engagement carry the same loyalty promise across thousands of restaurant identities.
Written with these in mind
Not your kind of problem? 20 more at Owner, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Owner. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Head of Design, Consumer (opens in a new tab)
- Owner powers the digital guest experience for thousands of restaurants, from online ordering and branded apps to loyalty and lifecycle engagement.
- Set the design vision across online ordering, native mobile apps, loyalty, and lifecycle engagement.
- Staff Product Designer (opens in a new tab)
- Senior Product Designer (opens in a new tab)
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on easing someone in at the cost of understanding.
Forty-six percent of cardholders who reach the payment summary leave without converting.
You have to weigh faster completion against a clear view of what the plan will cost.
First-time approved shoppers complete at 61% when several plan choices appear, even as returning shoppers finish more often.
You must weigh a faster path to confirmation against proof that shoppers understand their repayment schedule.
Repayment-related reversals reach 14% within a day of an on-demand pay request.
You must weigh faster access to cash against a confirmation moment employees can trust.
The same setting, from another role
Each is set around Owner’s Owner AI-native restaurant platform, written for a different role. They’re separate briefs, not the same scenario.
Owners cannot tell whether a payout difference is pending, refunded, or missing after service.
You have to weigh a fast daily read against financial detail people can trust.
Multi-location operators cannot see which locations are losing repeat direct guests or why.
You must weigh a useful first retention view against definitions operators and Finance can both trust.
Several owners changed promotions or hours after recommendations missed local operating context.
You have to weigh immediate protection for live restaurants against the evidence needed to improve the recommendation loop.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make a hard-to-reverse product decision feel clear and defensible before customers are bound by its consequences.
Deleted records now eat 31% of retention cost, and recovery is slowing in large bases before a fixed storage migration.
You have to cut the cost without removing data that customers expect to get back.
Routing differs by region, so time to the right owner varies threefold, and the slowest paths enter the next filing peak unchanged.
You decide what must be true before launch, since the new path is hard to undo.
A migration review found 14,600 old invoices the new service calculates differently, 430 with conflicting exemption evidence.
You decide what counts as correct before a switch you cannot undo.
