Better Is Not Specific Enough — How Criteria Gives Culinary Development Direction

There is a moment in development when the question “Which one is better?” becomes much more difficult than it sounds. We may already have spent several days or weeks working on the preparation. Inside the kitchen, we have tasted different versions, made adjustments, repeated the recipe, and gradually narrowed the possibilities. We probably understand the history of the dish very well by this point. We know why one ingredient was removed, why another was increased, which technique gave us trouble, and how far the current version has moved from the first attempt.

Then somebody else enters the conversation. Perhaps it is the owner, the person who asked us to develop the recipe, the rest of the team, a group of customers, or someone whose opinion we trust. We put the preparation in front of them and ask what they think. This is where things can become complicated very quickly, because the reactions often arrive in the broadest possible language. “I liked the other one better.” “This version is not quite there.” “I don’t know, I think it needs something.” These reactions are completely normal. People are not necessarily trained to describe what they are experiencing, and they have not lived through the development process with us. But if we are going to use their feedback to make decisions, “better” is not specific enough.

The Problem Is Not Subjectivity

Food is subjective. One person loves bitterness, another avoids it. Someone grew up eating very acidic food and another did not. One person may find a sauce perfectly seasoned while another experiences it as aggressive. Culture, memory, habit, expectation, and personal preference all enter the tasting. The mistake is not allowing subjectivity into the process. The mistake is allowing subjectivity to become the only criterion.

If we ask ten people which version they like best, we may simply discover that ten people have different preferences. That can be interesting, but it does not necessarily tell us which preparation is most appropriate for the work we are developing. A more useful conversation begins when we ask what people are actually responding to. Perhaps someone prefers version A because it is brighter and less fatty. Someone else prefers version B because it has more body and feels richer. Now we have information. The disagreement still exists, but it has become legible.

Once we can name the difference, we can begin deciding whether that difference matters. That is where judgment starts to become useful. We are no longer collecting preference for its own sake; we are trying to understand what the response tells us about the preparation and whether it moves the work in the direction we want.

Everyone Needs to Know What We Are Trying to Solve

Before asking people to evaluate a preparation, we need to give them enough context to understand the problem. This can be very simple. We might say, “We are developing a sauce for this particular dish. The current version tastes good, but it is too rich and becomes unstable during service. We are comparing these versions to see whether we can make it lighter without losing the character of the sauce.” Now the person tasting understands the question. That is very different from simply placing three bowls on the table and asking which one they like.

The same applies if we are developing something for a client. Perhaps they asked for a sauce that can be produced at a particular cost, stored for a certain amount of time, and used by several cooks with different levels of experience. If we show them the most delicious version but it costs twice the target price and takes an hour to make, we have not really solved their problem.

Context helps everyone evaluate the same thing, and it also protects the development process from irrelevant opinions. Someone may say, “I would put truffle in this.” Perhaps that would taste wonderful. But if truffle has nothing to do with the concept, budget, or intended use of the preparation, then it is not necessarily useful feedback. Not every interesting suggestion belongs to the work.

Criteria Give Us Something to Judge Against

This is where criteria become useful. Criteria are simply the qualities or conditions that matter for the particular thing we are developing. For one preparation, flavor may be the dominant concern. For another, stability may be critical. A sauce used à la minute in a small restaurant can tolerate a different level of fragility from something that needs to hold for several hours. A recipe intended for publication must consider whether another cook can understand and reproduce it. A product sold from the restaurant may need to survive storage, packaging, handling, and perhaps refrigeration.

The criteria change because the destination changes. That means “better” can take several forms. A version may have better flavor but worse stability. Another may be slightly less exciting but much easier to produce during service. One may have a beautiful texture but use ingredients that make the cost impossible. Another may be inexpensive and practical but move too far from the original intention. This is where culinary development becomes a real decision-making process. We are no longer asking which version wins in the abstract. We are asking which version best satisfies the combination of things that actually matter.

That can be difficult for cooks because flavor is naturally central to the way we think. Imagine we have three versions of a sauce. Version A tastes extraordinary. It is layered, aromatic, and beautifully textured, but it takes forty minutes of active work and uses two ingredients that are expensive and difficult to source. Version B is slightly simpler but can be produced reliably in fifteen minutes with ingredients the restaurant already uses. Version C is inexpensive and easy but has lost too much of the character we were trying to create.

Which one is better? There is no useful answer until we know the context. If we are developing a sauce for a one-night tasting menu, version A may be entirely appropriate. If we are developing it for a busy lunch restaurant with limited labor, version B may be the stronger preparation. Version C may be practical but no longer worth pursuing because it solves the operational problem by sacrificing too much of the food. None of these judgments says flavor does not matter. They simply recognize that flavor does not work alone.

Criteria Help Us Filter Feedback

This becomes especially important when more people join the tasting. Once a preparation leaves the development kitchen, opinions multiply quickly. Someone thinks it should be sweeter. Someone wants more chile. Someone dislikes the color. Someone says it feels too heavy. Someone else says it is not rich enough. If we respond equally to every opinion, the preparation begins moving in circles.

Criteria help us filter those responses. Suppose the central priorities are flavor, stability, speed of service, and cost. If someone says the sauce is too heavy, that feedback may be highly relevant because it touches flavor, mouthfeel, and perhaps the amount of fat. If someone says they would personally prefer it much spicier, we can ask whether that preference fits the intended dish and audience. Perhaps it does. Perhaps it does not.

The point is not to dismiss opinions that fall outside the criteria. Unexpected observations can reveal important things. But criteria allow us to distinguish between information that should redirect the work and information that simply opens another possible direction. That distinction protects the preparation from becoming everything to everyone.

It is also why a simple evaluation sheet can be useful when several people are involved. We do not need twenty categories or an elaborate scorecard. We may only need to ask about flavor balance, texture, stability after thirty minutes, cost, and overall fit with the dish. Another project may need yield, production time, ease of execution, or packaging performance. The framework should come from the problem itself.

Creative Work Eventually Requires Choosing

There is another problem that appears at this stage, and it is almost the opposite of where creative work often begins. At first, we may feel stuck because we have no ideas. Then we start researching and experimenting, and suddenly we have too many. Version A has the best aroma. Version B has the strongest texture. Version C is easier to make. Version D uses an ingredient we are fascinated by. Version E may feel more original. Version F has the best food cost. Now we are stuck again, but for a completely different reason. The possibilities have multiplied, and we have not yet decided which possibilities actually belong to the work.

At some point, development requires narrowing. That can feel uncomfortable because choosing one path means abandoning others, at least for now. A version can be interesting and still not belong in the final preparation. An ingredient can be exciting and still pull the dish in the wrong direction. A technique can demonstrate skill and still add unnecessary complexity. This is where creative direction begins to appear. Creative direction is partly the ability to say, “This is the work we are making, and this is what matters most inside it.” Criteria support that decision because they give us something firmer than preference to work with.

The same is true when the criteria themselves compete. Suppose version A receives the highest marks for flavor, version B for stability, and version C for cost. We still have to decide how much weight each criterion carries. Is a small improvement in flavor worth a much higher cost? Is the more stable version worth choosing if the texture is noticeably worse? Can we accept a longer preparation time because the dish is central to the restaurant’s identity?

These are not mathematical questions alone. They are questions of judgment, and judgment depends on intention. What is this preparation supposed to do? What role does it play? Which qualities are essential and which are negotiable? Where can we compromise, and where would compromise remove the reason the preparation exists in the first place?

Sometimes the Answer Is to Go Back

Clear criteria do not always lead to choosing one of the versions already in front of us. Sometimes they reveal that none of them is ready. Perhaps version A has the flavor we want but is too expensive. Version B solves the cost problem but loses the texture. Version C is stable and practical but feels flat. Instead of choosing the least problematic option, we may decide that the useful information is precisely this: we now know what needs to go back to the kitchen.

That makes the next round much more focused. We are no longer saying, “Try something else.” We are saying, “Can we keep the flavor profile of A while reducing the ingredient cost?” Or, “Can we stabilize B without changing its texture?” The evaluation has produced another question, and that is valuable. A tasting does not always need to produce a winner. Sometimes its purpose is to identify the next problem clearly enough that development can continue.

Better Has to Mean Better for Something

This may be the most useful shift at this stage of the culinary creative process: we stop talking about improvement as though it were universal. Better always means better for something. Better for the dish, the guest, the menu, the service, the production system, the intended price, or the original idea. Sometimes those interests align beautifully. Sometimes they do not, and that is where the real work begins.

The purpose of criteria is not to turn creativity into a scorecard. It is to give judgment enough structure that we can make deliberate decisions rather than simply following the loudest opinion in the room. Once we know what we are trying to improve and why, outside feedback becomes easier to interpret. We can listen without being pulled in every direction. We can recognize an interesting suggestion without automatically adopting it. We can identify when a criticism exposes a real weakness and when it simply reflects another person’s preference.

Most importantly, we can begin narrowing possibilities with more confidence. The creative process has given us options, but options alone do not give us direction. At some point, development asks us to decide what belongs, what does not, and what the work actually needs from us now. That is why “better” is not specific enough. Improvement only becomes useful when we know what we are trying to improve, for what purpose, and why it matters.

→Read further about recipe development, culinary experimentation and R&D, in the framework of the culinary creative process:

What is culinary R&D? → How do I design a culinary test? → What is the difference between testing and refining? → How do I evaluate the test? → How do I decide what is better? → Why should I document it?