The Menu Should Not Erase the Dish

Imagine a resort restaurant introducing a Maldivian breakfast dish. The kitchen has tested the recipe, checked its ingredients and shown the finished preparation to the service team. On the guest menu, however, the dish is called simply tuna and coconut salad.

The description is not entirely wrong. But it gives little sense of what the guest is ordering. Is it eaten on its own? Does it come with bread? Is it spicy? Why is it on the breakfast menu?

The preparation may be mas huni, a Maldivian breakfast commonly served with roshi flatbread. Calling it a tuna and coconut salad may make the wording easier to recognize while leaving the dish itself harder to understand.

This example is hypothetical, but it reflects a decision faced by hotel teams serving regional food to international guests. My concern is not whether every guest recognizes the name mas huni. It is whether the hotel has explained enough for someone to order it with confidence. A kitchen may take great care over the recipe, only for the menu to make the dish seem more generic than it is.

The name and the description do different jobs

A local dish does not need to lose its name to become approachable. Its name identifies the preparation and connects it to a place. The description tells a guest what to expect.

A clear menu entry might read: Mas Huni: Maldivian tuna with grated coconut, onion, chili and lime, served with roshi flatbread.

That is enough to begin with. It preserves the name, identifies the principal ingredients and explains the accompaniment. The exact words must, of course, match what the hotel actually prepares. Some recipes and serving arrangements differ, and the printed description should never promise an ingredient that is absent from the plate.

The same difficulty appears in other cuisines. Vietnamese bánh xèo is often described in English as a savory pancake or crepe. The comparison is useful, but incomplete. A guest may imagine something soft, when the preparation is distinguished by its crispness. Depending on the regional version, it may contain shrimp, pork, bean sprouts and other ingredients.

A short explanation of its texture and filling can be more helpful than replacing its name with a generic label.

Making the menu familiar is not the same as making it clear

International hotel restaurants serve people with different expectations. Some guests want to try regional food; others prefer something familiar, particularly after a long journey. An effective menu should make space for both.

Hilton’s 2026 Trends Report, released in October 2025, found that 79% of the travelers surveyed took comfort in familiar menu items. The research covered more than 14,000 respondents across 14 countries. It describes the preferences of that survey sample, not a rule for every traveler.

Comfort and curiosity need not be opposing choices. A guest might order a familiar dinner one night and want to try a regional breakfast the next morning. The hotel’s task is to make that second choice understandable.

Keeping the local name does not require a long history lesson beside every dish. Nor does an unfamiliar preparation need to be disguised as something international. A few accurate words can invite a guest to order without guessing.

Describe the food the guest will receive

Menu descriptions usually begin with ingredients and cooking methods. For an unfamiliar dish, the kitchen and restaurant manager should go a little further and consider what might materially affect the guest’s decision.

Is the dish hot or cold? Is its texture crisp, soft or creamy? Is the chili level important? Does an accompaniment complete the preparation? Is it intended for one person or for sharing?

Not every answer belongs on the printed menu. Too much information makes descriptions difficult to read. The point is to include the details that prevent a reasonable misunderstanding.

A phrase such as traditional spiced fish gives almost no indication of whether the fish is grilled, fried, cured or cooked in a sauce. The words sound appealing, but they leave the actual preparation unexplained.

The same caution applies to words such as authentic, traditional and signature. They can be justified, but none is a substitute for describing what is on the plate.

If the hotel offers a contemporary interpretation of a regional preparation, it should be presented as an interpretation. There is room for creativity without suggesting that an adapted dish is an unchanged version of the local tradition.

Translation has to begin in the kitchen

I see menu translation as a culinary decision as much as a language task. A description may be agreed by the Executive Chef and restaurant manager, then passed to a marketing team, an external translator or software. Responsibility for what the dish actually contains and how it is prepared cannot disappear during that process.

A translation can read smoothly and still be inaccurate. A cooking method may become a broader term, the name of a regional ingredient may be replaced by a different one, or a description of mild heat may become a promise of a spicy dish.

Those differences matter in a restaurant. A guest who orders from a translated menu should receive the same information as someone reading the English master.

The approved recipe must therefore remain the reference for every language. A useful internal record includes the original dish name, the ingredients that define it, the method, serving components and the approved description. The kitchen should also maintain its allergen and dietary records through the property’s established food safety process.

A competent language reviewer can check meaning and natural phrasing. The restaurant manager can judge whether the result helps a guest order. Neither should be asked to invent details that are missing from the recipe.

When an ingredient, garnish, sauce or preparation changes, the team must review the affected descriptions and dietary information. That review should reach the printed menu, QR menu, in-room dining material and order-taking systems wherever the dish appears.

Allergen information cannot be inferred safely from a dish’s name. It must reflect the actual ingredients and any relevant cross-contact risks, in accordance with applicable requirements and the hotel’s procedures.

The same dish should not become four different promises simply because it appears in four languages.

The restaurant team finishes the explanation

A clear menu reduces unnecessary questions, but guests will still ask what an unfamiliar preparation tastes like, how it is eaten or whether something can be changed.

The service team needs enough knowledge to answer accurately without giving a lecture. That includes seeing the finished dish, understanding its main components and knowing what the kitchen can alter safely.

Where practical, a menu briefing should include tasting. Someone describing a crisp savory preparation should recognize its texture. Someone recommending a regional breakfast should know whether the roshi is included or ordered separately.

Employees in international hotels may come from many countries and may never have eaten the local dish before joining the property. That is a reason to train them, not to replace the dish’s name with a generic English label.

The team also needs permission to check with the kitchen when an answer is uncertain. A brief, accurate response after verification is better than a confident explanation that proves wrong when the plate arrives.

Look at the questions before removing the dish

When a regional item sells poorly, price and guest preferences are obvious explanations to investigate. But the menu wording and the way the dish is introduced may also be part of the problem.

Restaurant teams can identify descriptions that repeatedly cause confusion. Do guests ask whether the dish is sweet or savory? Are they surprised by the portion or the accompaniment? Do they order it expecting a different texture?

These conversations are not a scientific survey, but they can show where a description is failing to explain the plate.

I would hesitate to remove a regional dish before checking whether guests understood it. The Executive Chef and restaurant manager can compare the description with the finished plate, revise unclear wording and brief the team again. Guest comments and ordering patterns can then be reviewed alongside price, availability and the changing guest mix.

More orders alone would not prove that the new wording caused a change. Fewer misunderstandings and more confident service conversations may tell the team more.

This work does not require a complete menu redesign. I explored the broader relationship between restaurant identity, menu structure and daily service in Restaurant Menu Design: Identity, Structure and Execution. Here, the question is more specific: whether the guest can understand the dish without losing sight of what makes it local.

The people who know the dish should have a say

Regional cooking is not represented responsibly through translation alone. People familiar with the cuisine can help a hotel decide whether a name is used correctly, whether a description is misleading and whether one variation is being presented as the only legitimate version.

That knowledge might come from local cooks, producers or colleagues who understand the dish beyond the version developed for the hotel. Their contribution should be taken seriously rather than used simply to give the menu a local appearance.

The final test can be simple. Before approving a menu, ask a colleague outside the kitchen to read a few unfamiliar entries and describe what will arrive at the table. Repeat the exercise in each language the restaurant intends to use.

If those colleagues cannot form a reasonable expectation, the descriptions need more work.

A hotel should not have to choose between preserving the identity of regional food and making it understandable to visitors. The name deserves to remain. The explanation needs to do its work.

Sources

• Visit Maldives, Maldivian cuisine: A myriad of rich tastes and flavors. Description of mas huni and its customary serving with roshi.
• Vietnam Tourism, 21 Must-Try Vietnamese Dishes. Description and typical ingredients of bánh xèo.
• Hilton, Home Comforts Are the New Carry-On, 2026 Trends Report. Survey finding on familiar menu choices (79%).

About the Author