What a Tasting Menu Is Actually For?
A menu gets treated, most of the time, as a logistics problem: feed this many people, accommodate these allergies, stay within this budget. All true, all necessary, and all beside the actual point of a menu at a designed event.
A tasting menu is a narrative device. Each course is a sentence in a story the guest is eating their way through, whether anyone's told them that or not. The sequence matters as much as any individual dish: what arrives first sets an expectation the next course either fulfills or deliberately breaks; what closes the meal is the last thing a guest's senses remember about the entire evening, regardless of what happened in between.
The best briefs we get from chefs aren't about ingredients. They're about arc: where does the meal want to feel restrained, and where does it want to surprise? Where should a guest's attention sharpen, and where should it be allowed to relax? A menu built only around seasonal availability and dietary logistics can still be technically excellent and say nothing at all.
A menu built around a deliberate emotional sequence - even using humble, everyday ingredients - says something a five-course tasting menu from a rulebook never will.
A menu doesn't need a client's name attached to carry meaning, it needs a genuine point of view about what that particular room, on that particular night, should feel like course by course. That's a harder brief to write than "make it delicious." It's also the only version of the brief that produces a meal anyone remembers past dessert.
Comments