How to actually get dinner on the table in 15 minutes

Most fifteen-minute recipes are lying, usually by not counting the chopping, or by starting from cooked rice they do not mention.

Genuinely fast cooking is a structural problem rather than a recipe problem. Meals that are fast are fast for reasons, and the reasons repeat.

Rule one: nothing that needs to soften

Root vegetables, dry pulses and tough cuts of meat all need time and no technique will change that. Fifteen-minute food is built from things that are already soft or that cook in minutes: eggs, prawns, mince, tomatoes, spinach, mushrooms, anything pre-cooked.

This is why almost every fast dish in the world is built on eggs or noodles.

Rule two: one pan, and get it hot first

Heat the pan while you chop. Most home cooking is done on a pan that is too cool, which is why food steams and greys instead of browning. Browning is flavour, and it is also speed: a properly hot pan cooks the outside of something in ninety seconds.

One pan also means one thing to wash, which matters more at 9pm than any of this.

Rule three: cook the leftovers you already have

Cold rice becomes fried rice in ten minutes. Leftover dal becomes a paratha filling. Boiled potatoes become jeera aloo, aloo chaat or a sandwich. Roast a tray of vegetables on Sunday and they are in your bowls, wraps and pasta all week.

Deliberately over-cooking rice and potatoes is the single highest-return habit in a weeknight kitchen.

Rule four: acid and fat at the end, not more spice

When a fast dish tastes thin, the instinct is to add spice. The answer is almost always lemon, vinegar or a knob of butter added off the heat.

Long-cooked food builds depth through time. Fast food has to borrow it, and it borrows from fat and acid.

Rule five: stop counting the rice

Put the rice on first and it cooks while you make everything else. It is not part of the fifteen minutes because it does not need you.

The same is true of a kettle of water for pasta or noodles. Start the slow, unattended thing before you start the fast, attended thing. This sounds obvious and is the step people most often get backwards.

The twenty minutes you spend on Sunday

Fast weeknight cooking is mostly decided at the weekend, and by a very small amount of work.

Boil a batch of potatoes. Cook extra rice deliberately and refrigerate it. Make a jar of ginger-garlic paste. Chop onions and keep them in a sealed box; they will be fine for three days and the smell does not transfer if the box is genuinely airtight.

That is twenty minutes and it removes the slowest step from four or five weeknight dinners. It is not meal prep in the sense of cooking whole meals ahead, which most people abandon after a fortnight. It is prepping the components you were going to make anyway.

What fifteen minutes cannot buy you

Being honest about the limits matters as much as the techniques. Fifteen minutes will not give you a biryani, a slow-cooked mutton, a properly browned onion base, or bread.

Browning onions alone takes twelve minutes and cannot be shortened, which means any dish whose flavour rests on a brown onion masala is off the table on a weeknight. That is not a failure of technique, it is chemistry.

Cook those on a Sunday, or accept a different kind of dinner on a Tuesday. The mistake is trying to rush them and producing a pale, thin version of a dish you like, then concluding you cannot cook it.

The dishes that follow all five

Every one of these is genuinely fifteen minutes or less, including preparation, from a normal kitchen.

  • Masala omelette with buttered toast, 10 minutes
  • Tomato egg stir fry, 12 minutes
  • Garlic fried rice with a fried egg, 15 minutes
  • Pasta aglio e olio, 15 minutes
  • Besan chilla, 15 minutes
  • Egg bhurji, 15 minutes
  • Bread upma, 15 minutes
  • Batata bhaji, 15 minutes

Recipes that use this

Still don't know what to cook? Let it decide →