Food Everyone Likes

You ask at four in the afternoon. What does everyone want for dinner?

Nobody answers. One of them says anything, which isn't an answer. One says the thing you made on Tuesday, which you're not making again on Thursday. The youngest names something you don't have the ingredients for. So you decide alone, cook for an hour, and watch one person eat around the edges of the plate.

Then you do it again the next night.

The search for food everyone likes usually turns into a search for recipes — some list of crowd-pleasers, some set of dishes that supposedly work for every family. That's the wrong place to look. Crowd-pleasers are written for crowds. Your family isn't a crowd. It's four or five specific people with specific objections, and one of them changes their mind every six months.

The dish everyone likes is almost never the dish everyone loves. It's the dish nobody objects to. That distinction sounds small. It's the whole thing.

Why asking doesn't work

The question what do you want to eat asks people to search an unbounded space from memory. Adults are bad at this. Children are worse. What comes back isn't preference — it's whatever surfaced first, which is usually the last good thing they ate or the thing they saw on a screen.

It also asks the wrong question. You don't need to know what they want. You need to know what they'll eat without a negotiation, on a Wednesday, when everyone's tired.

Those are different facts and only one of them is stable.

The veto matters more than the vote

Think about how a meal actually fails. It rarely fails because nobody loved it. It fails because one person wouldn't eat it, and that turned dinner into a thirty-minute event about the food instead of a meal.

So the useful signal isn't the average. Score every dish out of five, take the mean, and almost everything lands in the same narrow band — families rate their own cooking generously, and the numbers compress into something that tells you nothing. Two dishes can average identically when one was quietly fine for everybody and the other was loved by three people and refused by the fourth. Those are completely different dishes. One you can make on a weeknight. The other is a fight.

What you're looking for is the floor, not the average. The dish whose lowest score is a three. That's food everyone likes, in the only sense that matters at six o'clock.

You already know some of them

Every household has four or five of these. They're the meals you fall back on when the week has gone wrong. You don't think of them as favorites because they're not exciting — they're the roast chicken, the pasta with the sauce you make without measuring, the soup that gets eaten in silence.

The problem isn't that you don't have them. It's that you can't list them.

Ask anyone to name their family's ten reliable meals and they'll get to four, pause, and then start naming things they cooked once and liked. The rotation runs itself, and it's mostly invisible to the person running it — which is the same reason a family cookbook is so hard to assemble from memory years later. You're inside it while it's happening, and you can recall about a dozen.

How to find the food everyone likes in your house

Write down what you cooked, not what you plan to cook. A plan is a guess about the future. A record is evidence. Most people who try to solve this reach for a meal planner and give up within three weeks, because planning is work you do before you're tired and recording is work you do after. The adjustments count too — the ones you make to a recipe every time, which is the last section of the cooking conversion chart.

Note who ate it. Not a rating out of ten — nobody sustains that. Just enough to reconstruct the table later: who cleaned the plate, who left it, who asked for it again the following week. Asking a child at the table whether they'd want it again is a two-second question and a better signal than any score.

Pay attention to the refusals. A refusal isn't missing data. It's a strong opinion, and it's the one that determines whether a dish belongs in your rotation. The dish that gets one hard no is out, however much the other three enjoyed it. If you'd rather start on paper, the picky eater chart is built for exactly this — one row per meal, one column per person, and the printable food journal carries the same idea across a whole week of dinners.

Give it two months. You need repetition before a pattern is legible. A dish cooked once tells you about one night — the mood, the timing, how tired everyone was. The same dish cooked five times tells you about the dish.

After a couple of months you stop guessing. You have a list of things that work, with names attached, and the four-in-the-afternoon question mostly answers itself.

What changes when you know

The obvious gain is that dinner gets easier. The less obvious one is that the arguments stop being about food.

When you can point at a record and see that a dish has been made four times and refused by the same person every time, that's no longer a matter of opinion. It's not you never eat anything — which is a character judgment and starts a fight — it's you don't eat this one, which is a fact about a dish and ends the conversation.

The reverse works too. Preferences drift, especially in children, and drift is invisible without a record. A child who wouldn't eat peppers at six often will at nine, but nobody notices, because everyone stopped offering. A record shows you the last refusal was two years ago and it might be worth trying again.

Food everyone likes isn't a list you find. It's a list your household already has, and hasn't written down.

Common questions

MealEncore keeps your family's food memory — a record of what you actually cook and what each person thought of it, so the list of meals that work writes itself. Get started →