Does choosing a recipe by ingredient count make things easier?

Whether you can finish a recipe on a weeknight is decided not by the number of ingredients but by the number of preparation steps. If a long ingredient list all goes into a single pot, the evening's work is short; if a short list puts every ingredient through a separate process, the work stretches out. What you count while choosing a recipe is steps, not ingredients.

Why is the ingredient count a misleading criterion?

An ingredient list is a shopping criterion; it says nothing about the time spent in the kitchen. In a vegetable dish with more than ten ingredients, most of them are chopped on the same board and go into the same pot. In a recipe with four ingredients, one is marinated, one is seared in a separate pan, one is boiled in separate water, and in the end they all come together.

The second has fewer ingredients and more work. Choosing by looking at the list does not show that difference; looking at the body of the recipe does. So dropping a recipe because its ingredient list is crowded most often means dropping the wrong recipe.

How do you count the steps?

While reading the recipe through once from start to finish, mark three things: how many times the heat source changes, how many separate containers get dirty, and in how many places you have to wait. Preheating the oven, resting a dough or leaving meat in the refrigerator do not need you to stand in the kitchen, but they lengthen the evening.

These three numbers give a far better estimate than how many ingredients the recipe has. Pick the low one for weeknights and set the high one aside for the weekend. If you note the numbers next to the recipe, the decision is already made the second time you look at it.

The chopping work itself is not measured by a single number either. The same number of ingredients spreads over different times when one is cut coarsely and another is finely minced; ingredients that need fine work are the invisible length of a recipe.

The real cost: processing the same ingredient twice

The pattern that eats the most time is one ingredient going through two different processes. Potatoes boiled first and then fried, part of the onion sautéed and part added raw, meat seared and then cooked in a separate sauce are all like this.

These do not make a recipe bad; most of the time they genuinely change the result. They are simply not the work of a tired evening. If a recipe has more than one of this pattern, saving it for an easier day is a realistic choice.

How many containers will be washed at the end of a recipe is part of the evening too, and it usually goes uncounted. The number of containers standing on the counter when the meal is over decides whether you will cook that recipe again more than the cooking time does.

How do you choose a weeknight recipe?

One-pot recipes with a single heat source and no waiting are the natural candidates for weeknights. The ingredient count is free here; if they are all prepared on the same board and go into the same container, the length of the list is not a problem.

Not trying a new recipe for the first time on a weeknight helps as well. On a first attempt you pause while reading, look for measures, take a step back; the same recipe gets noticeably shorter the second time. In other words, the real time a recipe takes only appears the second time you cook it.

How many people a recipe is written for changes the step count too. While scaling a recipe for four down to one, ingredients that are hard to divide come up and the recipe gets more complicated instead of shorter; that has to be taken into account in a weeknight choice as well.

What can you do today?

Open the recipe you are thinking of cooking this week and count its steps: changes of heat, number of containers, waiting. Write the result next to the recipe. If you have a few recipes that work well for you, gather them in one place; choosing on a weeknight is always shorter than looking for a recipe from scratch.