Dingbo M. Branding Marketing Specialist & Product Designer ← All work
Case study AI · Hardware · SaaS 2022–2025

Yordando

AI Task Management & Scheduling for Professional Kitchens

Role
Product Designer & Founding Team Member
Where
Yordando · Vilnius / Shanghai
Patent
PCT WO2025126247 · co-inventor
Outcome
100 market-ready prototypes
01

Hook

Yordando is an AI task-management and scheduling system for restaurant kitchens.

Line cooks carry a small handheld e-paper device. Every time a task is finished, they press one physical button. Those presses become the live input for a central AI engine that continuously re-optimises who does what, and when — and delivers the result to head chefs through a web dashboard.

I joined as the founding designer and stayed through to market entry: I co-invented the product (PCT international patent WO2025126247), designed both of its digital interfaces, ran the research with the chefs who would use it, and led the design work that took it to investors, trade fairs and the first 100 production prototypes.

Positioning note

Lead with Product Designer. The executive work is a strength, but it should read as “a designer who could carry the product all the way to market”, not as a second, competing job title. Section 8 handles that.

02

Context

Professional kitchens still run on memory and shouted instructions. Shifts are planned from experience, tasks are distributed verbally, and during peak service the plan and the reality drift apart within minutes: work stacks up on one station while another idles, and new cooks lose track of what comes next.

Scheduling software exists, but it lives on the manager's laptop. It is structurally disconnected from the person standing at the pass with a pan in each hand. It can record a plan; it cannot see a service.

Yordando closes that loop by moving the feedback point down to the line cook — a handheld e-paper device with physical buttons. One press per completed task. The data flows back to a central AI that adjusts distribution and scheduling in real time, and surfaces the reasoning to management through a SaaS dashboard.

01
Cook
finishes a task
02
Device
one button press
03
AI engine
re-optimises the plan
04
Dashboard
head chef reads and adjusts

My responsibility: the two digital interfaces — the constrained on-device UI and the SaaS web application — together with the physical form of the device and the field research with end users.

Needs your input
Team size and the other roles — e.g. “working alongside X engineers and an ML lead”.

Tools: Figma (UX/UI, prototyping, design system), semi-structured interviews and in-kitchen observation.

Needs your input
Industrial design / 3D / rendering software you used.
03

Problem

The design problem was not “make a nicer screen.” It was:

How does a cook working in heat, noise and constant motion — hands gloved, wet or full — report progress with almost zero friction, so that the AI schedules from live reality instead of after-the-fact estimates?

This split into two tensions that shaped every decision:

Physical

No cook is going to unlock a phone and tap an app mid-service. Hands are dirty, screens are unreadable under kitchen lighting and heat, and any interaction longer than about a second simply will not happen. The input had to survive the environment, not ask the environment to accommodate it.

Human

A system that assigns tasks and records who completed them is, from the cook's side of the counter, indistinguishable from surveillance unless it is designed otherwise. If cooks feel monitored, they resist, or they press the button carelessly. And the moment the feedback data stops being honest, the AI schedule collapses. Trust was not an ethical footnote on this project — it was the load-bearing requirement.

04

Research

I ran the user research directly, in the kitchens and with the people who would live with the product.

  • 10 in-depth interviews with top-tier professional chefs, including head chefs and line cooks. I wrote the discussion guides and moderated the sessions myself.
Needs your input
Did you also observe services in-kitchen? How many restaurants, which cities? Add one line — direct observation is worth more than interviews in a portfolio.
Needs your input
Any review of existing scheduling / kitchen display software you benchmarked against?

Insights that changed the design

Select the 2–3 that genuinely did — write each as: what we heard → what it changed.

Insight 1 — needs your input
Example of the shape I'm looking for: “Chefs described switching tasks every few minutes during peak. Anything requiring visual attention was dead on arrival → the confirmation had to be operable without looking at the device.”
Insight 2 — needs your input
Example: “Cooks weren't afraid of being scheduled. They were afraid of being scheduled unfairly — of the system not seeing the work they actually did → we made contribution visible to the cook, not only to the manager.”
Insight 3 — needs your input
One insight from head chefs / management side, since you designed their interface too.
05

Define

Two users, two interfaces, one loop.

Line cook
Head chef / manager
Interface
Handheld e-paper device
SaaS web application
Role in the system
Produces the signal
Consumes and adjusts the output
Context of use
Seconds, one-handed, no visual attention available
Minutes, seated or at a station, planning mode
Success looks like
Confirmation costs one physical action and no thought
The AI's schedule is legible at a glance and can be overridden

Design principles I set

1. One action, no reading.
Confirmation must complete in a single physical press.
2. The constraint is the brief.
E-paper's slow refresh and lack of colour are not obstacles to design around — they are the argument for radical reduction.
3. Explainable, or it won't be trusted.
Neither the cook nor the head chef should have to take the AI's word for anything.
06

Design decisions

Each decision paired with its reasoning — this is the substance of the case study. Show the artefact next to the argument.

01

Physical buttons and e-paper instead of a touchscreen app.

In an environment of grease, gloves, steam and heat, a mechanical button is the only reliable zero-attention input. E-paper stays legible under harsh kitchen lighting, doesn't glare, and draws so little power that the device runs a full service and beyond without charging.

02

The device screen shows only current task and next step.

Cooks have no reading time. Information density was pushed to the absolute floor. The refresh characteristics of e-paper enforced this discipline rather than fighting it — the medium made restraint the only workable option.

Verify
Confirm this reflects what you actually built before publishing.
03

Contribution is visible to the cook, not only to the manager.

Needs your input
This is the decision that will make the case study memorable. What did you actually do to make the system feel fair rather than supervisory? Even something small: what the cook can see on their own device, how the day's completed work is reflected back, whether the schedule logic was ever explained to the line, whether cooks could flag a mis-assignment.
04

The SaaS dashboard presents the AI's schedule as a proposal, not a verdict.

I designed the web application so that a head chef can read the generated distribution at a glance and adjust it by hand — authority stays with the person who knows the kitchen.

Needs your input
How did you actually visualise the schedule? Timeline, station view, task cards? What could be overridden, and what did the interface do with the override? One concrete detail here is worth a paragraph of theory.
05

The hardware constrained the software, and I designed both.

Because I was responsible for the device's physical form as well as its interface, refresh rate, contrast, button count and grip position were decided together with screen hierarchy rather than handed over the wall.

Needs your input
One example where changing the hardware solved an interface problem, or vice versa — this single example is your strongest differentiator.
07

Solution

The system: a handheld e-paper device with physical confirmation buttons and a single-task screen, a central AI scheduling engine, and a SaaS web application where head chefs read, adjust and act on the generated plan.

The loop: every button press is a timestamped fact about the kitchen. The engine schedules from those facts. The dashboard explains the result. The head chef corrects it where the model is wrong. The correction becomes data too.

My contribution, stated plainly: I designed a slow, colourless, low-resolution screen into the least intrusive and most trusted feedback point in a high-pressure kitchen — and designed the management interface that made its output legible and overridable on the other end.

08

From prototype to market

Because Yordando was an early-stage company, my role extended past the product itself. I include this not as a separate job, but because it is the reason the design ever met a real kitchen.

Manufacturing

I worked with the design and production team in Shanghai (Between Design) to take the device from design files to 100 market-ready 3D-printed prototypes, resolving form, tolerance and finish questions in production.

Intellectual property

I produced the visual component of the patent application — technical sketches, rendered figures and the illustrated explanation of how the system works — filed as PCT international patent WO2025126247, on which I am named co-inventor.

Investment and funding

I designed the pitch materials and pitched to VC funds in Vilnius and Shanghai, supported the company's EU Next Generation fund application, and arranged founder–investor meetings. I also designed the Y Combinator application deck.

Market presence

I designed the company's brand and communication system — website, brochures, business cards, presentation templates — and the full exhibition identity (stands, posters, print) for SIAL Shanghai, the Shanghai World AI Conference, Collision Toronto and the China Hi-Tech Fair, Shenzhen. I also produced and edited the video content explaining the solution for these events and for social media.

Deployment

I led the on-site training of professional chefs using the system — closing the loop from the research that started the project to the people finally holding the device.

09

Impact

WO2025126247
Patent granted — PCT international patent, as co-inventor.
100
Market-ready prototypes manufactured and delivered.
4 / 3
International trade events across three countries — Shanghai (SIAL, World AI Conference), Shenzhen (China Hi-Tech Fair), Toronto (Collision).
10
Professional chefs interviewed to define the product.
Field deployment
Professional chefs trained on the system in the field, led by me.
Needs your input
Add whichever of these you have, even approximate: pilot restaurants using the device; qualified leads or partnerships generated at the fairs; funding raised or fund stage reached; adoption/task-confirmation rate; anything a chef said after using it. A single honest number, or one strong verbatim quote from a chef, is worth more than three vague claims.
10

Reflection

What the project taught me

In extreme environments, constraints are not obstacles to design around — they are the design direction. E-paper's slowness gave me the discipline I needed. And more fundamentally: whether an AI system works is not a technical question. It is a question of whether the people feeding it data trust what it does with them.

What I'd do differently

Needs your input
One specific, honest thing. Strong candidates, if true: testing the confirmation interaction in a live service earlier; involving line cooks rather than only head chefs in early sessions; building the fairness/transparency features into v1 instead of treating them as a later layer.

Where it leads

Yordando is why I now want to design human-centred AI systems for food and hospitality — systems where efficiency and the experience of the people inside them are not in competition. It is the same question I pursued in my master's research on the relationship between people and AI, met in a hot kitchen instead of on a page.

Appendix

Working material

Reference blocks and production notes. Turn the appendix off before publishing.

Quick-reference blocks

Project card blurb — 45 words

A handheld e-paper device and AI scheduling platform for restaurant kitchens. Line cooks confirm each finished task with one button press; the system turns that live signal into optimised staffing and task distribution. Co-invented, designed end-to-end, and taken to market across four countries.

One-line summary — 20 words

A one-button kitchen device that feeds real-time task data to an AI scheduling engine. PCT patent WO2025126247.

Role line

Product Designer & Founding Team Member · 2022–2025 · Yordando (Vilnius / Shanghai)

Scope line

Device interaction & form · SaaS web application (UX/UI, Figma) · Field research with 10 professional chefs · Patent visuals · Brand, pitch and exhibition design · Manufacturing liaison for 100 market-ready prototypes

Visual asset checklist

Section
What to show
Hook
Hero shot of the device in a real kitchen or in hand — one image, full bleed
Context
Simple system diagram: cook → device → AI → dashboard → cook
Research
Photos from interviews / kitchen visits; a page of the discussion guide; insight cards
Define
The two-user table, redrawn as a graphic
Decisions 1–2
Device screens, 2–3 key states, each captioned with its reason
Decision 3
Whatever artefact shows the trust/fairness thinking
Decision 4–5
SaaS dashboard: wireframe → final UI; a flow of the scheduling task
Solution
Exploded or annotated device render; the full loop diagram
Market
Patent figures; exhibition stand photos; pitch deck spreads — as a compact strip, not full pages
Impact
Patent number and metrics as typographic statements, not a paragraph

Still missing — fill these and the case study is complete

  1. Team composition. Who else was on the product, and what did they own? Needed so your scope reads as credible rather than total.
  2. Research detail. How many kitchens did you visit or observe, and where? Which 2–3 insights actually changed a design decision?
  3. The trust decision (Section 6.3). The single most valuable thing you can add — it is what separates this from a hardware case study.
  4. The dashboard specifics (Section 6.4). How the AI schedule was visualised and overridden.
  5. Any real number or chef quote for Section 9.
Dingbo M.
Branding Marketing Specialist & Product Designer · Yordando, 2022–2025