Prototype

Prototype. Daki is not an official Harvard dining service.

What is real
  • Harvard is the intended setting for an initial pilot, not a confirmed partner.
  • Diner locations, hours and access rules are a dated snapshot of published HUDS pages (retrieved Oct 5, 2026). Menus are either that snapshot or, when connected, Daki’s weekly refresh of public HUDS FoodPro pages. Neither is a live feed. Each record shows its source and dates.
  • Where no official menu was captured, Daki says so; a sample menu appears only if you ask for it and is labelled as illustrative.
  • Dining-team figures are simulated from a separate, fictional sample menu.
  • No operational, health, financial or sustainability outcomes have been demonstrated.
  • Prototype interactions stay in this browser unless you choose to share anonymous beta activity with Daki (see the beta notice). Nothing is sent to any dining team.
  • Nutrient groups use only values printed on HUDS nutrition labels. Vitamins, minerals and antioxidants are shown only when the source supplies them; antioxidants never are.
  • No medical or allergen-safety determination is made. Allergen information must be confirmed through the dining provider’s official source.

Dining-team concept

Which decision could an earlier signal actually support?

Dining teams already have transactions, production records, surveys, comments and waste data. What may arrive too late, or not at all, is what diners considered, what they couldn’t find, which schedules got in the way and what they planned ahead. This concept starts from the decision, then shows the evidence. Every figure is simulated.

Built to be questioned. This concept offers no operational instructions. Daki has not validated that these signals can support ordering or menu decisions.

  1. Current menu information
  2. Diner explores or plans
  3. Voluntary interaction signals
  4. Privacy-conscious aggregation
  5. You are hereDining team interprets patterns
  6. Potential improvements

Detailed analytics

Simulated from a fictional sample menu with a fixed seed. Use the filters to explore; groups under 10 are hidden.

Preparing simulated data…

Customer discovery

Tell us what would actually help

Your answers stay in this browser until you choose to copy or email them. Nothing is collected automatically.

Email my answers

Pilot scorecard

What a pilot would need to measure

Nothing here has been measured. There are no active users and no signed pilot.

MeasureFor whomStatus
Decision time (how long from opening Daki to a choice)DinersNot measured
Decision confidenceDinersNot measured
Recommendation relevanceDinersNot measured
Repeat use over 7 and 28 daysDinersNot measured
Share of plans later confirmedDiners and dining teamsNot measured
Reasons plans changeDiners and dining teamsNot measured
How far ahead intentions arriveDining teamsNot measured
Usefulness of the less-than-15-minute thresholdDinersNot measured
How often Fly-By and takeout are recommendedBothNot measured
Whether students carry out advance-pickup plansBothNot measured
Frequency of schedule-related unmet needsDining teamsNot measured
Whether staff consider a signal newDining teamsNot measured
Whether staff can act on itDining teamsNot measured
Cost and effort for dining teamsDining teamsNot measured
Menu-data accuracyBothNot measured
Privacy and trust concernsBothNot measured

Help shape the experiment

Daki is looking for dining professionals who can help determine which signals are useful, which are not, and what a responsible pilot would require.

Or write to maverickyasuda@college.harvard.edu