How to Cook When You Have No Time

First, a question worth answering honestly, because it changes everything below.

If someone handed you the ingredients and a recipe at seven o’clock, would you cook it? If yes, this is not your page. You have twenty minutes and no decision, which is a different problem, and the six o’clock decision is where it gets solved.

If the answer is genuinely no, because the window between arriving home and needing to eat is fifteen or twenty minutes and no amount of planning creates a twenty-fifth, then read on. That is a real constraint, and it means most recipes are simply unavailable to you. Nothing about that is a failure.

The 20-minute recipe is usually lying

Not maliciously. It is a convention.

The stated time almost always means active cooking time, measured from the point where everything is chopped, measured and within reach. A method that opens with “one onion, finely diced” and “two cloves of garlic, minced” has quietly moved eight minutes of work outside the number.

There is also a hidden assumption that you are not doing anything else, which is rarely true in exactly the households that need fast food most.

So a useful rule: add ten minutes to any stated time, and if the ingredient list has more than about six things in it, add more. Once you apply that correction, most of the internet’s weeknight recipes turn out to be thirty-five minute recipes, and it stops being mysterious that they never fit.

What genuinely fits in fifteen minutes

The limit here is physical, not a matter of skill or effort. Some things cannot be made fast because heat takes time to get into food.

These fit. Eggs, in any form. Pasta, because the sauce can be finished in the time the water takes. Anything with tinned fish or tinned beans, which arrive already cooked. Tortillas and flatbreads, which need warming rather than cooking. Thin cuts of meat, because thin is the whole variable. Anything stir fried, since small pieces and high heat is the fastest cooking method there is. And anything built on something already cooked from a previous night.

These do not fit, ever. A braise or a stew, because the point of it is time. Root vegetables roasted from raw, which need forty minutes whatever you do. Dried beans or lentils from scratch. A whole chicken. Bread. Anything where the recipe says “until tender” about something hard.

Knowing the second list is as useful as knowing the first, because it stops you attempting a thing that was never going to work and concluding you are bad at cooking.

Shorten the shopping, not the cooking

If your evening window is fixed, the way to buy time is to move work out of it.

Buy things that arrive with a step already done. Pre-chopped onions cost more and are not a moral failing. Frozen chopped vegetables are picked and frozen fast and are often better than tired fresh ones. Tinned pulses are cooked. Rotisserie chicken is cooked. Frozen rice reheats in three minutes. Jarred sauce is a legitimate base you can improve with two minutes of effort.

There is a strand of cooking advice that treats all of this as cheating. Ignore it. The comparison is not against someone with a free afternoon, it is against ordering delivery, and every one of these beats delivery on cost, speed and what is actually in it.

Cook once, eat twice

This is the highest leverage thing on the page, and it is not about speed at all.

The slow parts of cooking barely change with volume. Heating a pan, waiting for water to boil, waiting for something to soften, and washing up afterwards cost the same whether you cook two portions or four. Doubling a recipe usually costs three or four extra minutes.

So a thirty minute session that makes two dinners is a fifteen minute average, and the second night requires nothing from you at all. That is the only way to get genuinely fast weeknight food if your window is tight: not by cooking faster, but by cooking less often.

The full version of this idea is batch cooking, including the variety problem it creates and how to avoid it.

Get the shopping to the point of no decisions

The last thing that steals evening time is not cooking, it is standing in the kitchen at seven auditing what is there.

If the four meals for the week are decided and the shopping was done against them, the evening has no discovery phase in it. You look at the list of four, pick one, and start. That is the difference between a fifteen minute meal and a fifteen minute meal plus ten minutes of opening cupboards.

Lower the bar deliberately

The last thing, and the one people resist.

A plain meal you actually make beats an excellent meal you do not. If the realistic choice on a Tuesday is between pasta with butter and pepper or delivery, pasta with butter and pepper is the better outcome by every measure that matters, including the nutritional one.

Cooking does not have to be interesting to count. Most of the meals that keep a household fed are not interesting. Keep three or four unglamorous things you can make without thinking, and stop measuring them against food that was cooked by someone with an hour and a photographer.

If assembling the options is what eats the time, that is what AnyRecipe does: recipes from wherever you found them in one place, filtered to the fast ones, a week picked from them, and the shopping list built from that week with quantities merged across meals. Free to download on iPhone and iPad.

And if the honest problem is not the clock but the end of the day, there is a page for that. It is a different problem and it needs a different answer.