The setting
makes software for restaurants, from single locations to large chains. Its handle ordering, payments, kitchen work, staff and reporting.
Campaign activity is visible, but its value to a restaurant manager is still unclear.
Managers need a fast reason to repeat a promotion while the experience must not overstate what campaign data proves.
Who you’d be doing this for
“I sent the offer last week, and now my owner keeps asking if it brought anyone back.”
Chanwoo Huang · Restaurant Manager · a character in this brief
Runs guest campaigns for a two-location restaurant group and decides which offers to repeat.
What is at stake
Managers cannot tell which campaign influenced repeat visits, so they keep guessing where to spend. You have to weigh a clear recommendation against evidence that does not overclaim.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- simple decisions vs honest attribution
- fast operator review vs meaningful context
- reusable patterns vs restaurant-specific variation
- campaign outcomes vs sparse data
Why Toast
Marketing Tools sit beside restaurant ordering and guest experiences, so unclear campaign outcomes leave operators unable to connect outreach to repeat visits.
Written with these in mind
Not your kind of problem? 38 more at Toast, 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 Toast. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Senior Product Designer, Marketing Tools · no longer posted
- You'll own the design of Toast's Marketing Tools: the surfaces restaurants use to reach guests, run campaigns, and understand what's working.
- We build experiences that help make operating and growing a restaurant and delighting guests easier and scalable.
- Principal Product Designer, Onboarding · no longer posted
- You can prototype interactions, spec components, and push Figma work that sets a high bar.
- You’ll set direction hands-on, in Figma, in prototypes, in critique, and through influence: building the conviction and relationships needed for R&D and cross-functional teams to adopt the patterns you define, not just execute your roadmap.
- Senior Product Designer – Toast Retail (opens in a new tab)
- Prototype with AI: Use AI prototyping tools such as Replit, Magic Patterns, or Claude to build working, interactive prototypes with realistic data, so ideas can be tested with customers and engineers before the team commits to them.
- You will partner closely with the Dublin engineering team that is already building and shipping AI tools that help Toast's onboarding teams set up retail customers.
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 is about figuring out which problem is actually worth solving.
Retailers who placed a first order are not returning despite follow-up ads.
You must decide where the system's proposed test stops and the strategist's choice of audience, message or offer begins.
Opening Soon strategists are drawing different next-test conclusions from the same LinkedIn results.
You must decide what AI recommends, what evidence it cites, and where strategist judgment remains required.
Feedback about ecosystem and partner-specific campaigns is repeating without a shared view of what advertisers actually mean.
You must decide where the clustering of Ads Manager and Carrot Ads feedback stops and where the PMs' own reading of campaign scope and reporting questions begins.
The same setting, from another role
Each is set around Toast’s Restaurant point-of-sale and management platform, written for a different role. They’re separate briefs, not the same scenario.
Public-storage findings are being reopened because engineers cannot see whether a restaurant-facing service is exposed.
You have to decide where the route stops and the engineer starts when a finding arrives with its Terraform and Datadog context.
Cash transactions can round locally and later disagree with the cloud record.
You must weigh resilient offline service against controls that keep each location's cash rules correct.
Card payments are failing to recover at some locations after a restricted access change.
You must weigh fast restoration against the access exposure that the rollback would preserve.
Other problems with a similar purpose
In each of these, as in this one, the aim is to turn fragmented, conflicting operational signals into one clear, actionable call.
Checking customers retry account actions when the mobile app and backend services tell an incomplete story.
You decide where the AI's trace of an incident stops and where the on-call engineer's confirmation of the cause begins.
Conflicting updates are letting carrier-integration risks reach readiness reviews too late.
You must decide which dependency changes the workflow sends straight to a Program Manager as uncertain and which it records as flags for the readiness record.
Regional production can stop while aggregate workspace activity still looks healthy.
You must decide where the ranking stops and the CSM starts: which signals set an account's place in the order, and which the CSM reads for themselves before choosing what to say.
