top of page
Search

How I Develop a New KAI Menu

Writer: Issachar Lee
Issachar Lee
Oct 19
7 min read

Updated: Oct 21

The ideas, testing and decisions that happen before a dish reaches the table.


A new menu rarely starts with seven finished dishes. Usually, it begins with something smaller: an ingredient I want to explore, a flavour I remember, or a question about how a familiar dish might be approached differently.


At KAI Private Dining in Singapore, I develop each menu around a central idea before working out how the individual courses will fit together. There is research, testing and plenty of reconsideration along the way. Some ideas work; others turn out quite differently from what I had imagined.


Here's a look at how I work through that process.


traditional dishes and flavours as starting point of menu development for KAI Private Dining.

It begins with an idea, not a recipe


For KAI, Southeast Asian ingredients and food traditions are a natural starting point. Growing up around this food and travelling through the region have given me plenty to draw from, but familiarity doesn't mean there is nothing left to discover. Sometimes I want to understand why a particular combination works so well. At other times, I'm interested in what happens when an ingredient is prepared differently.


My classical French training gives me another set of tools to work with. Curing, clarifying, confiting, reducing and making emulsions can change an ingredient's texture, concentrate its flavour or bring out a quality that might otherwise go unnoticed.


The aim isn't to make Southeast Asian food look French, or to combine two cuisines just to create something novel. I want to find a preparation that suits the ingredient and the dish while keeping its character recognisable.


Take kaffir lime leaves, for example. They have a wonderful citrus aroma, but a whole leaf isn't always the best way to incorporate that flavour into a plated dish. Extracting the aroma into an oil gives me a different way to use it. The flavour remains, but the form and presentation can be more suitable for the dish.

That is the sort of question I enjoy working through: not simply what an ingredient tastes like, but how best to use it.



The challenge is turning ideas into dishes.

An idea can sound compelling when described in a notebook. The challenge begins when I try to make it edible. 😂


One example from KAI's Origin menu is the opening tomato course.

The idea came from eating Thai yam salads. After the ingredients have been eaten, there is often a pool of liquid left at the bottom of the plate, full of the dressing's sour, salty and spicy flavours. I've always thought that liquid was worth paying attention to. In fact, in Thailand, they often order a plate of kanom jiin, to mop up the sauce and that becomes their starch of the meal.


I began wondering whether I could capture that part of the experience and make it the starting point for a course.

That led to the tomato consommé. The aim was to create an opening dish that carried the freshness and tang of yam, rather than simply reproducing the salad in a different form.


Getting from that idea to a finished dish takes more than choosing the ingredients. I have to work out how the flavour should come through, what texture the dish needs, and whether each component contributes something useful. A preparation can taste good on its own but still be wrong for the plate.

I also draw on the cookbooks I've collected while travelling around Southeast Asia. When I visit a place, I enjoy eating at restaurants that represent its food culture and, where possible, attending cooking workshops to learn more about how local dishes are made. Those books and experiences give me references to return to when I want to understand a flavour or technique more deeply.

They don't provide ready-made answers for a tasting menu, but they provide inspirations and help me ask better questions.



Southeast Asian cookbooks collected by chef Issachar along his years of travels in the region


I begin by exploring possibilities, testing combinations and paying attention to what each component contributes. Sometimes the first attempt gets close to what I imagined. More often, it gives me a clearer understanding of what the dish still needs.


A preparation may be technically sound but lack personality. A sauce might taste delicious on its own yet dominate the main ingredient. A garnish may add colour without contributing anything meaningful to the flavour. A dish may have all the right elements but still feel incomplete.


These are not necessarily failures in the conventional sense. They are information.

Each attempt helps me understand the idea a little better—and sometimes tells me that I have been asking the wrong question altogether.


Testing often means taking things away

When a dish isn't quite working, it's tempting to add something. Another herb might make it more fragrant; another seasoning might give it more punch; a garnish might make the plate look more complete.


But sometimes the problem is that there is already too much going on.

A sauce may overwhelm the ingredient it is supposed to support. An extra garnish may add colour without improving the flavour. A dish might have enough acidity but lack the right texture. Adding more ingredients won't necessarily solve any of those problems.


I try to consider what each element is contributing. Does it bring flavour, aroma, texture or contrast? Does it help the main ingredient, or distract from it? If I remove it, does the dish actually become worse?


These are practical questions, but they can be harder to answer than they sound. An idea that seemed essential at the beginning may turn out to be unnecessary once the dish comes together.


The point of testing isn't to keep adding layers until a plate looks complicated. It's to understand what the dish needs and stop when the elements make sense together.



A dish can work on its own and still be wrong for the menu

A dish can be satisfying on its own and still not belong in a seven-course tasting menu.


If two courses are both rich and deeply savoury, eating them back to back may make the meal feel heavy. Several dishes built around the same herb or flavour profile can become repetitive, even if each one is good individually. A lighter course might be needed between them, or a dish may need to be simplified.

This is why I don't develop all seven courses in isolation and then put them in order at the end. I have to think about how they will work together: which flavours appear early, where the meal becomes more substantial, and what kind of finish makes sense.


The order matters because guests experience the menu as a whole. A dish has to do more than taste good; it has to make sense at that particular point in the meal.

Sometimes that means changing a course that I was initially happy with. Other times, it means leaving a good idea out because the menu already has something similar.


 There should be contrast, but also connection. Familiarity should have room to develop into surprise, and the more substantial parts of the meal should feel earned rather than abrupt.


In that sense, designing a tasting menu is a little like composing a piece of music. Individual passages matter, but so does the relationship between them.




chef Issachar at the pass of the kitchen, explaining a dish, solo chef's execution of dishes

The practical side of cooking alone

KAI operates from a small home kitchen, and I prepare and serve the menu for one shared table of six to eight guests. That affects how I develop the food.


A dish might taste excellent during testing, but can I prepare it consistently for the whole table? Can the important preparation be done ahead without compromising the result? Will the texture hold until service? Can I plate it properly while keeping the rest of the courses on schedule?


These aren't glamorous questions, but they're part of the work.

A complicated technique is only useful if it produces a result worth the extra effort. If a method creates unnecessary steps without improving the dish, I need to reconsider it. Sometimes I adjust the quantities or timing; sometimes I simplify the preparation itself.


Consistency matters, too. A dish cannot depend on everything going perfectly once. I need to understand the method well enough to reproduce the result when I'm cooking for guests, not just when I'm experimenting at my own pace.

The final version has to work both on the plate and in the kitchen where it will be served.  If it only works under ideal testing conditions, it is not yet ready.



Knowing when an idea is finished

Not every dish makes it onto the menu. Sometimes an idea doesn't develop as I hoped. Sometimes the finished dish is perfectly good, but it doesn't add anything that the menu needs.


It's easy to become attached to an idea after spending time researching it, testing it and working through different versions. But the time invested isn't a reason to serve it. The question is whether the dish belongs.


A seven-course menu has limited space. Each course needs a reason to be there, whether it introduces a flavour, provides contrast or helps the meal move naturally towards what comes next. If a dish doesn't contribute to the experience, I have to be willing to leave it out.





That doesn't mean the work was wasted. Even an idea that doesn't make the final menu can teach me something about an ingredient, a technique or the direction I want to take.



The menu is a journey, not a collection

Eventually, the individual dishes begin to make sense alongside one another. I taste them as a sequence, not just as separate recipes, and look at what happens when one course follows another. Sometimes a transition that seemed fine on paper feels awkward when I eat the dishes together. A course may need to be lighter, or an element that once seemed important may no longer be necessary.

The menu is ready when the dishes work as a whole and I can reproduce them with confidence. That doesn't mean every doubt has disappeared. It means the decisions have a clear purpose, and the meal feels coherent without becoming overworked.


By the time guests sit down at KAI, they see the finished plates rather than the discarded versions, the adjustments and the changes of direction. That's how it should be. The purpose of the development process isn't to show how much work went into a dish; it's to make the finished meal worth eating.

Developing a new menu is part of what keeps cooking interesting for me. An ingredient or a memory can lead somewhere unexpected, but it takes time and testing to work out whether that idea belongs on the table.


And once one menu is settled, there are always more questions to explore.

The next KAI menu cycle is planned for January 2027. Until then, Origin is the menu I'm sharing with guests, and the starting point for whatever comes next.


Look out for the new menu cycle from January 2027. 🍃

If you have not yet tried Kai Origin menu, it's going away soon. Book now.




 
 
 

Comments


bottom of page