When I have a full afternoon of work ahead, I want to eat enough without feeling heavy, so I do not lose the first hour to drowsiness.
Khi tôi còn cả buổi chiều phải làm việc, tôi muốn ăn đủ no mà không bị nặng bụng, để không mất một tiếng đầu giờ chiều vì buồn ngủ.
Job context
- Who
- Someone doing focused work all afternoon
- When
- At the moment of ordering
- Trigger
- An afternoon already lost to a heavy meal
- Situation
- No way to know in advance how a dish will land
- Constraints
- The menu offers nothing but a name and a price
5 Pains
No idea how large a portion is
HighThe photograph does not say.
Root cause: Menus describe dishes, not portions
Sleepiness afterwards costs the afternoon
HighAnd you learn it only once it is too late.
Root cause: The consequence appears an hour after the decision
Eating light means hunger by three
MediumThen snacking makes it worse.
Root cause: Lunch is the only meal inside an eight-hour stretch
No information beyond the name
MediumOily or not, salty or not, nothing is stated.
Root cause: Small kitchens have no channel to publish that
The same dish differs hugely between places
MediumOne name, two entirely different plates.
Root cause: A dish name is a shared convention, not a standard
5 Desired Outcomes
Know the portion size before ordering
FunctionalStay alert through the afternoon
FunctionalNot be hungry again by mid-afternoon
FunctionalKnow how the dish is made
FunctionalStop guessing at every order
Emotional
5 Existing Solutions
A solution is not the same thing as a product, a customer can hire a behaviour or a workaround too.
Order a known dish at a known place
BehaviourThe only way to know what is coming, and it locks you into a few options.
Look at photographs and reviews
ProductThe only source available, shot from the most flattering angle.
Deliberately order less than usual
WorkaroundAvoids the heaviness by moving the problem to three o'clock.
Ask the seller about the portion
BehaviourThe most accurate route, and nearly impossible when ordering through an app.
Split the meal into two sittings
WorkaroundSolves both ends at once, needing somewhere to keep it and a little planning.
2 Opportunity Gaps
No unit exists for describing a portion, not grams, not a fullness level, nothing, so a buyer cannot compare two dishes at all.
Why existing solutions fail: Publishing portions exposes a kitchen to direct comparison on quantity, so no seller has a reason to go first, and the platform earns per order, not per satisfied meal.
Potential opportunity: A portion signal reported by the people who ate, accumulating per dish rather than waiting for sellers to declare.
The decision happens at ordering and the consequence appears an hour later, in a different place and state, with nothing connecting the two ends.
Why existing solutions fail: The eater never joins the two events into a lesson, because an hour and several other things sit between them, so the same mistake repeats hundreds of times and teaches nothing.
Potential opportunity: Reconnecting the two ends for the eater: recording the dish and recording the afternoon, so the pattern surfaces itself.