Essay

On Not Apologizing for What Is Not on the Plate

Every dinner party host explains the plant-based meal before the first bite. Stop. The food is the food. The apology is what makes the meal small.

Alexandre Teulade · · 8 min read

There is a moment at the start of almost every dinner party where the host serves the plant-based meal and then immediately apologizes for it.

I have watched it happen in maybe a hundred kitchens. The host puts the dish down on the table — a cassoulet, a wellington, a pasta, a moussaka, a salad — and then before anyone has lifted a fork, the host says some version of: “So, full disclosure, this is plant-based, I wasn’t sure how to do it for everyone, I tried this thing with mushrooms instead of, well, you know, and I hope it works, I’m not promising anything.” And the table goes quiet for a second, and everyone looks at the dish slightly differently than they would have, and the meal has already been made smaller before anyone has tasted it.

Stop.

The food is the food. If it is good, no one cares what is not in it. If it is bad, no apology will fix it. The apology is not a courtesy. The apology is the thing that is breaking the meal.

I want to argue this with conviction because I think the apology is the single most common mistake I see in plant-cooking hosting, and because it is doing damage that goes far beyond any one dinner party. Every time a host apologizes for a plant-based meal in front of guests, the host is teaching those guests — silently, structurally — that plant-cooking is a thing that requires an apology. That it is, by default, a lesser version of dinner. That the host is not confident in the food. That the food is going to be okay but probably not great. That the guests should adjust their expectations downward before the first bite.

The guests then eat the meal with adjusted expectations. They are, even if the food is excellent, comparing it to the version they think they would have gotten if the host had not made the substitution. They are not eating the dish that is on the plate. They are eating a comparison. And the comparison, by the inescapable logic of the framing, is the version that is not quite as good as the absent original.

This is the same trap as the substitute word. It is the same trap as the plant-based qualifier. It is the same trap as the “vegan” label on the menu. The trap is in the framing, not the food. The food is fine. The food is, almost always, better than the host gives it credit for. The trap is in the words the host says before the food gets to defend itself.

The fix is to stop talking.

Serve the meal the way you would serve any meal. Pour the wine. Pass the bread. Say “I made cassoulet” or “I made pasta” or “there is risotto” and then let people eat. Do not explain. Do not contextualize. Do not flag the absence. Do not promise anything. Do not apologize. The dish is the dish. Trust it.

I learned this the hard way, over years, in my own kitchen.

When I first started cooking entirely with plants — around 2018, after the slow drift away from meat that I have written about elsewhere — I apologized for everything. I apologized at brunches. I apologized at family dinners. I apologized at the cassoulet I made for eight people in 2022 in the Languedoc, where I was working a season at an estate kitchen and had the audacity to serve a Tarbais-bean cassoulet, with no duck and no pork sausage, to a table of French guests who had been raised on the real one. I prefaced the meal with three full minutes of explanation. I said the words “plant-based” twice. I said the word “vegan” once. I said “I hope it works” four times. The guests ate politely. They said nice things. They left.

The cassoulet was, I now believe, one of the best things I have ever cooked. The braise had gone for eleven hours. The crust on top — broken and re-formed seven times, the proper Languedoc way — was a deep amber that crackled when you pressed it with the back of a spoon. The Tarbais beans had collapsed into the broth in that particular way they have, which makes the dish feel like a single integrated thing rather than beans in a sauce. The smoked paprika and the slow-roasted onion and the splash of cognac at the very end had built a flavor base that, frankly, did not need the duck.

But the guests didn’t get to taste that. They got to taste a defensive cassoulet, served by an apologetic host, with the words “plant-based” hanging in the air over the table. The food was fine. The meal was small. The apology had done its work.

About a year later, in 2023, I was hosting six people for dinner in my apartment in Washington. I had made a wellington — king oyster mushroom center, sherry duxelles, prosciutto-replacement made from sliced and dehydrated celeriac, all-butter puff pastry. I had spent two days on the thing. As I was carrying it to the table I felt the apology forming in my mouth — the same words, the same defensive crouch, the same flagging of the absence — and I stopped.

I put the wellington down. I said nothing. I sliced it. I served it. I asked someone to pass the wine.

The room ate in silence for about three minutes, which is the silence that happens when good food is hitting people in the right way. Then one of the guests — a man I had met twice, who had grown up in Yorkshire on roast dinners and would by any reasonable definition be classified as a meat-eater — pointed at the wellington with his fork and said: “Where did you get this? Is it from somewhere?” Meaning: which butcher made the tenderloin that’s inside this thing.

I said: “It’s mushroom.”

He said: “Shut up.” Then he asked for seconds.

That was the moment I understood what the apology had been costing me for years. Not just the social ease of the dinner. The food itself. The thing on the plate. The apology had been giving people permission to taste the meal in the wrong register. Without the apology, the meal landed exactly where it was supposed to land. The wellington was a wellington. The guest tasted a wellington. He had no advance framing about a substitute or an absence or a clinical category, and so the experience he had was the experience the food was actually delivering, which was: this is a wellington that was made very carefully, by someone who knew what they were doing.

The man asked for the recipe. I gave him the technique. He has, since then, made it for his own family twice. He told me, the second time, that he had served it without saying what was inside, and his father — who has eaten beef wellington for sixty years — finished his plate and asked for the recipe. He still had not been told it was mushroom. The father came back the next week and asked his son to make it again. Only after the second meal did the son tell him.

This is the data point that broke the apology habit for me, permanently. The food, when it is given the chance to defend itself on its own terms, can convince people who have spent sixty years eating the original version. The food is strong enough. The food has always been strong enough. The thing in the way was never the food.

There is one more piece of this I want to make explicit, because I think it is the deepest mistake the apologetic host makes, and I have made it myself for years.

The apology is, deep down, a way of pre-empting criticism. It is the host saying: I am going to point out the thing you might criticize, so that you have to be polite about it. The apology is preemptive defense. And preemptive defense, in food as in everything else, is the surest way to invite the criticism it is trying to avoid. When you flag the absence, you have made the absence the topic of the meal. The guests are now thinking about what is missing. You have done their work for them. You have handed them, free of charge, the framework that makes the meal smaller.

The fix is to refuse to do that work. Serve the food as if it does not require an explanation. Because it does not.

The cassoulet I made in the Languedoc in 2022 did not require an explanation. The wellington in 2023 did not require an explanation. The milanesas I have made in twenty kitchens in five countries did not require an explanation. The risotto I will make this weekend will not require an explanation. The dishes I have inherited from ten countries and refracted through a French technique stack do not require an explanation. They are dinner. They are the whole dinner. They are made with the technique I learned in France, refracted through every kitchen I have been lucky enough to stand in since, and served on plates that are probably chipped because we use the plates we like.

The dish does not owe the diner an apology. The diner does not need one. The meal is good when it is good and bad when it is bad and the apology cannot fix either of those things. It can only make the good meal smaller.

The next time you serve a plant-cooked meal, try this. Put it on the table. Say the name of the dish. Pour the wine. Let everyone eat. Do not flag the absence. Do not explain the substitution. Do not promise anything. Do not apologize.

The food has been waiting for years to speak for itself. Let it.

— Alexandre Teulade Washington, D.C.