Options
Make customization visible and finite.
Clyde Dogs should give guests useful choices without making every order a unique production experiment. Lobos's proposed approach is to define the modifications the line can execute reliably, then make those choices obvious.
Choice without chaos
The menu should describe the paths the line actually supports.
A guest should be able to order a straightforward dog, remove a topping, add an approved topping, or choose a more heavily dressed signature build without forcing the crew to invent a new process at the service window.
“The truck does not have a secret menu. Secrets imply we were uncertain the first time.”
— Lobos
Plain is a real option.
A plain dog is operationally simple and should remain simple: correct dog, correct bun, correct packaging, and an accurate ticket.
Approved add-ons should have portions.
Extra onions, peppers, chili, cheese, or sauce should use defined portion tools or counts.
Put sauces on the side when that makes the order easier.
Side portions can be a useful option when the guest wants control or when adding the sauce in advance would compromise the bun.
“Ketchup, mustard, relish. A committee was proposed. The committee was fried.”
— Lobos
Special orders should not bypass food-safety controls.
Customization does not change storage, heating, holding, allergen communication, cross-contact controls, or other required procedures.
The final check should read the ticket literally.
Before handoff, the checker should compare the finished order with the requested build: dog, bun, toppings, removals, additions, sides, beverages, and packaging.