MealOPS connects employees, company administrators and food operations through one workplace meal experience. Employees can discover and order meals using company benefits, while organizations manage budgets, policies and usage. The product brings those perspectives together so the ordering experience can stay simple while the program behind it remains manageable for employers and food partners.
03 / THE PROBLEM
Ordering food is easy. Running workplace meals isn’t.
Workplace meals involve more than choosing lunch. Company budgets and meal policies affect what an employee can order, while vendors, payments and operations determine whether that order can be fulfilled. If those parts are handled separately, a small decision for the employee creates coordination work for everyone else involved in getting the meal to them.
04 / Defining the product
Understand the ecosystem before the screens.
Employees need a quick way to choose and order. Employers need policy, budget control and visibility. Food operations need predictable demand and fulfilment. I mapped those relationships before shaping the individual experiences, so decisions about benefits, ordering and administration could support the same meal program rather than pull it in different directions.
01Make choice fast
Discovery and conversation help an employee get to a meal without turning lunch into a long search or a form filling task.
02Keep benefits in context
The company wallet and applicable policies appear where they affect a choice or payment. Employees do not need to manage the program’s rules before ordering.
03Give admins useful control
Budget, policy and usage belong in the administrative experience. Those controls should support employee ordering without adding extra steps to every meal.
05 / Designing the system
The meal connects the whole program.
Discovery and choice lead into the company wallet, ordering, fulfilment and feedback. The employee journey runs alongside an administrative layer for policy and usage, and an operational layer for delivery. MealOPS connects these responsibilities around the same order, giving each participant the information needed for their part of the work.
Workplace mealsCONNECTED PRODUCT
Employee
Discover + choose
Company wallet
Order + fulfilment
Food partner
Admin + feedback
Employee ↔ MealOPS ↔ employer ↔ food partner
06 / Key product challenges
The decisions that shaped the product.
Employee simplicity, employer control.
01The thinking
A company meal program needs budget and policy controls, but asking employees to manage those rules would make a routine meal choice harder. Ignoring them would move the coordination burden to administrators and food partners.
02The decision
Keep policy and usage management in the admin experience, and show the applicable benefit where it affects employee choice and payment. Connect both perspectives through the order.
03The result
The product structure gives each participant a focused experience while keeping benefits, demand and fulfilment part of one program.
07 / The solution
A quick meal choice, backed by a managed program.
JOURNEY 01
Find a meal. Use the benefit.
The employee experience brings food discovery and conversational ordering into a short path to lunch. Workplace benefits are part of that path, rather than another process to complete first. Choice, company wallet and order state stay together, so the employee can understand what they are ordering and how the benefit applies.
01Find a meal
02Choose an order
03Use workplace benefits
04Follow delivery
Conversation and company payment support the meal choice
JOURNEY 02
One product. Very different users.
Orders connect the employee’s next meal to the employer’s program and the food partner’s work. The responsibilities are different, so the product needs a clear handoff between participant views rather than a shared interface exposing every control to everyone.
01Employer: policy and usage
Budgets, benefit rules and program usage belong in the administrative view. These controls shape the ordering context without becoming tasks the employee must manage.
02Food partner: demand and fulfilment
Order information connects employee choice to the operational work of preparing and delivering meals. Operational status needs to return to the same order context.
03Employee: benefit and order state
The employee needs to understand how the company wallet applies and whether the meal is still being ordered or is moving toward delivery. An unavailable choice or benefit limitation should lead to a clear next action.
08 / Outcome & impact
A meal program with clear participant responsibilities.
My contribution was the product direction and ecosystem structure joining employee choice, company benefits, administration and food operations. The design puts benefit information at the point of ordering while keeping policy and usage control in the employer’s view. The same order connects the employee experience to fulfilment, so each participant has a focused role in the program.
01A connected program
The company wallet, administrative controls and usage information support the same ordering and fulfilment journey that employees use.
02What I learned
Products with several participants become clearer when the ecosystem is designed before individual screens. A choice that looks simple for an employee can create work for an administrator or food partner. Mapping those effects early helped me see where complexity should be handled within the product.
09 / Success criteria
Success criteria for workplace meals.
Evaluate whether employees can order confidently while company benefits and fulfilment stay connected to the same meal.
Order completion
≥98%
Available meal orders completed successfully from selection through confirmation.
Benefit comprehension
≥95%
Employees correctly identifying their applicable company benefit and the amount they need to pay.
Time to order
≤60 sec
Median time to place a repeat meal order using workplace benefits.