Why Deciding What's for Dinner Is Harder Than Cooking It

By about five o'clock most days, the cooking isn't the hard part. Chopping an onion, boiling some pasta, putting something in the oven: you can do all of that on autopilot. What wears you down is the question that comes before it. What are we actually having?

I'm not the only one who feels this. In a recent r/cookingtonight thread, people describe being more tired of deciding what to cook than of cooking itself. Parents in r/workingmoms and r/daddit ask the same thing from different angles: how do you take the daily dinner decision off your plate when you're already running on empty?

That question is the reason I built Foodedo. I've written before about the habit of asking "what's for dinner?" every night. This post is about something narrower: why the decision itself is so draining, and three practical ways to make it less often, whether or not you ever use an app.

Why the decision is the hard bit

Deciding what's for dinner looks like one small choice, but it's really a stack of them. What's in the fridge? What needs using up? Who won't eat what this week? Is there time to shop? Did we have this two days ago? How tired am I, honestly? Each one is minor. Together, at the end of a working day, they add up.

Cooking, by contrast, is mostly following steps. Once you know you're making a stir-fry, your hands know what to do. The decision has no steps. It's open-ended, it lands at the worst time of day, and it usually lands on the same person every time.

That last part matters. A lot of the frustration people describe isn't about food at all. It's about being the one who always has to come up with the answer. Even when someone else offers to cook, "just tell me what to make" still leaves the hardest part with you.

So the fix isn't a better recipe. It's changing when, how often and by whom the decision gets made.

1. Front-load the decision once a week

The simplest change is to stop deciding dinner every evening and decide it once, at a time when you've got a bit of headroom. For lots of people that's a weekend morning; for others it's a quiet ten minutes on a Sunday night.

The point isn't to produce a perfect plan. It's to move the decision away from 5pm, when you're hungry, tired and short on options, to a moment when you can think for a few minutes and then stop thinking about it for the rest of the week.

A few things make this easier:

• Decide dinners, not every meal. Breakfasts and lunches tend to sort themselves out. Dinner is where the fatigue lives.
• Plan fewer nights than you think. Five planned dinners leaves room for leftovers, a takeaway or plans changing.
• Make the shopping list at the same time. If the plan and the list are separate jobs, the list often doesn't get done, and you're back to improvising midweek.
• Don't treat it as a contract. If Wednesday's dinner becomes Thursday's, that's fine. The plan is there to remove the question, not to add guilt.

Once the week is decided, the evening question becomes "what does the plan say?", which takes about two seconds to answer.

2. Keep a fallback list for the nights the plan falls over

Even a good plan breaks. Someone's late, the chicken is past its date, or you simply can't face the thing you planned. Those are the nights when the decision fatigue comes roaring back, because now you're deciding under even more pressure.

A fallback list deals with that. It's a short list, maybe five to eight dinners, that meet three rules:

• You can make them from things you usually have in.
• They take very little thought, ideally no recipe at all.
• Everyone in the house will eat them without a debate.

Think beans on toast with something on the side, an omelette, a freezer meal you batch-cooked, pasta with whatever sauce is in the cupboard. They don't need to be impressive. Their job is to be the answer when you have no answer.

Write the list down somewhere you'll see it: on the fridge, in your notes app, or alongside your saved recipes. The trick is that on a bad night you're not choosing from everything you could possibly cook. You're choosing from a handful, and any of them will do.

It also helps to keep the ingredients for one or two of these topped up as a habit, so the fallback is always actually possible.

3. Hand off the choice, not just the cooking

Sharing the cooking is good. Sharing the deciding is what actually lightens the load. There are a few ways to do that.

Give someone else the planning job. If you live with a partner or older kids, let them own the weekly plan on alternate weeks, start to finish, including the list. The rule is that whoever plans gets to choose, and nobody re-litigates it on Tuesday.

Let people pick from a shortlist. Younger kids, or anyone who finds a blank page hard, can choose one dinner each from a list of options you're happy to cook. They feel involved, and you haven't had to invent anything.

Use rules to take choices out of it. Some households use loose themes, like pasta on Monday or something from the freezer on Friday. You're not deciding from scratch; you're filling in a slot.

Hand it to a tool. This is the bit I built Foodedo for. When you generate a plan, Foodedo picks the dinners for you, based on meals you've saved, liked, used before or turned down. You can still choose meals yourself if you want to, but you don't have to. The shopping list is linked to the plan, so changing a dinner changes what you need to buy.

The aim is the same whichever route you take: the person who's most tired shouldn't be the one who has to come up with the answer every night.

Make your own meals the starting point

One thing that makes all three of these easier is having your meals in one place. If the dinners your household actually eats are scattered across bookmarks, screenshots and memory, every planning session starts with hunting for them.

In Foodedo you can import a recipe from a link or by pasting in the text, so the meals you already rely on become the pool the plan is drawn from. To be upfront: some recipe sites won't import cleanly, and in those cases pasting the text is the way round it. Foodedo also doesn't track what's in your cupboards, so checking the list against what you've already got is still down to you.

Whatever you use, the principle holds. The plan should be built from food your household already likes, not from an endless list of new things to try. Variety is nice, but it's the opposite of what you need when you're trying to make fewer decisions.

A simple week to try

If you want to test this without changing everything, try it for one week:

• Pick one ten-minute slot at the weekend to plan five dinners and write the shopping list.
• Write a fallback list of five easy dinners and stick it somewhere visible.
• Hand one night's decision to someone else in the house, or let a tool pick it.

Then notice how the evenings feel. You'll still be cooking, but you won't be facing the same open-ended question every night at the point when you've got the least left to give.

That's really all I wanted Foodedo to do: take the deciding off your plate, so cooking dinner is just cooking dinner.