What's for dinner

Hi, it's Nora.

Wednesday was about protecting your best two hours at work. Today is about your worst ten minutes at home, and I suspect they're the same ten minutes for most of you.

It's five fifteen. You're tired. Someone is hungry, possibly everyone. You open the fridge and look at it the way you'd look at a crossword in a language you don't speak. There's half a pepper, some yogurt, a lot of condiments, and a vague sense that there was a plan once.

What's for dinner is the most repeated decision in any household. It arrives every single day, at the moment you have the least energy to make it, and it never gets easier by itself. If you do the arithmetic, that's three hundred and sixty five decisions a year, each one made tired, each one with a fallback of takeout that costs four times as much and doesn't make anyone feel great.

I'm not a food person. I don't meal prep on Sundays with matching glass containers. This isn't a recipe issue. It's a systems issue, because dinner isn't a cooking problem. It's a decision problem, and decision problems have boring, reliable fixes.

There are three things making dinner harder than it needs to be, and none of them are about cooking skill.

Decision fatigue at the worst time. By five p.m. you've made hundreds of decisions. Your capacity for one more, especially one with several people's preferences attached, is at its lowest point of the day. That's why "what do you want?" "I don't know, what do you want?" happens in every house in the country.

Ingredients and plans never match. You shop for ideas, not meals. So you have things that could become dinner but don't add up to one. The pepper, the yogurt, the rice. Technically food. Not a meal.

Infinite options. Every night, dinner could be anything. And a question with infinite answers is exhausting, which is why the answer so often becomes the phone and a delivery app.

The fix is to attack all three. Decide once a week instead of daily. Shop for decisions, not ideas. And shrink the options until the question almost answers itself.

This is the single most effective thing I've found, and it takes about fifteen minutes to set up.

Give each weeknight a theme. Not a recipe. A category. Something like:

That's it. Now, on Monday, the question isn't "what's for dinner." It's "which pasta." That's a much smaller question. It has maybe six answers you already know how to make, and you can pick one in about four seconds.

The themes do three jobs at once. They shrink the decision. They make shopping predictable, because you know you need pasta, tortillas, stock, and eggs every week. And they give the week a rhythm that kids, in particular, love. There's a reason taco Tuesday has survived this long.

People worry theme nights get boring. In practice they don't, because the theme stays fixed but what's inside it changes. Pasta can be forty different dinners. What gets boring isn't the category. It's making the same exact meal every Monday, which is a different system and not the one I'm recommending.

Pick themes that match your household. If nobody eats fish, don't have a fish night. If one kid will only eat plain things, make one night a "build your own" night where everything is separate and everyone assembles their own plate. The themes are yours. They should make life easier for the people at your table, not for a food blogger.

Next, write down every dinner your household actually eats and likes. Not aspirational meals. Real ones. The ones that get eaten without complaint.

Most families have somewhere between twelve and twenty. That's plenty. Put them in a note on your phone, grouped by theme. Pasta: the tomato one, the pesto one, the one with sausage. Tacos: chicken, black bean, fish if you're feeling brave.

This list is your menu. When you plan, you plan from it. When someone asks "what can we have," you show them the list. New recipes get tried occasionally, and if they're a hit, they go on the list. If not, they don't. The list grows slowly and only gets better.

This sounds almost too simple to be worth writing down. But it's the difference between planning from memory, which is tired and blank at five p.m., and planning from a menu, which takes seconds.

Once a week, ideally attached to the weekly review from last Saturday, spend ten minutes on dinner.

Ten minutes. Then the whole week's dinners are decided, on a Sunday, when you're calm and have eaten recently.

The other trick that changes the math is making double on purpose.

If you're making a pot of chili, a tray of roasted vegetables, or a big batch of rice, make twice as much. The second half becomes lunch, or dinner two nights later, or goes in the freezer for a bad week.

This is the lightest possible version of meal prep. You're not spending your Sunday cooking seven meals. You're just not throwing away the effort you already spent. The chopping, the pan, the cleanup: they take roughly the same time for four servings as for eight.

A few things that double especially well: soups, stews, chili, pasta sauces, curries, anything braised, roasted chicken, cooked grains, and taco fillings. A few that don't: anything fried, most salads, and pasta that's already mixed with sauce.

Every household needs three dinners that can be made in fifteen minutes from things that live in the pantry or freezer. This is the list that saves you on the nights the plan falls apart, which is maybe one night a week in a normal house.

Mine are: eggs on toast with whatever vegetables are around, a jar of good pasta sauce with frozen meatballs, and quesadillas.

Figure out yours and keep the ingredients stocked. Always. When you use one up, it goes straight on the shopping list. The emergency list is the difference between a bad night being a quick scrambled egg or a forty dollar delivery order and a late bedtime.

In a lot of households, one person carries the whole dinner system in their head. They know what's in the fridge, what everyone will eat, what's running low. That's the invisible part of the work, and it's often heavier than the cooking itself.

I wrote about assigning the list at home a couple of weeks ago, and dinner is the perfect place to start. The theme nights and the rotation list make it much easier to share, because the thinking is already done. Anyone can look at the fridge whiteboard and cook Tuesday's tacos. Nobody needs the person who holds it all in their head.

Some ways families split it:

However you split it, the rule is ownership, not help. "Helping with dinner" still leaves one person as the manager. "Wednesday is yours" doesn't.

A short note, because I get asked. I'm not going to give you nutrition advice. But a few structural things help with picky eaters, and they're mostly about reducing the fight rather than winning it:

Serve things separately when you can. Kids who won't eat a casserole will often eat every component of it on a plate, not touching.

Always include one safe food. Something you know they'll eat, like bread, rice, or fruit, on the table every night. It lowers the stakes.

Let them serve themselves. Kids eat more of what they chose to put on their own plate. It's annoying and messy and it works.

Fifteen minutes this weekend. Pick your theme nights. Write your rotation list. Choose next week's five dinners and put them on the fridge.

Then notice what happens at five fifteen on Monday. My guess is nothing. Which is the point.

Back Wednesday, when we go back to work and I want to talk about the meeting that should have been a note, and how to get rid of a surprising number of them without anyone getting upset.

Better, not busier.

Nora Bishop

P.S. The theme night is one version of a principle that runs through Better, Not Busier, the free guide: decide once, not daily. Twelve small systems like this one, all built for weeks that don't go to plan. It's free and it takes about fifteen minutes to read.