Let the family vote on dinner (and stop cooking meals nobody wants)

Every family cook knows the sting: an hour on a meal, and someone announces they "don't like this one" — information that existed on Sunday, delivered on Wednesday at 6pm. The fix isn't asking everyone what they want (that's seven negotiations); it's showing the plan and collecting cheap, early signal: thumbs up or thumbs down, before you shop.

Why voting beats asking

• Asking is open-ended — you get "I don't know" or three conflicting requests. Voting on a drafted plan is a 10-second yes/no.
• Early signal moves the fix to Sunday. A downvoted meal gets swapped before the shop, not scraped into the bin after.
• Kids engage more when they had a say. A meal they upvoted is a meal they've pre-committed to eating.

Make it effortless or it won't happen

Voting fails if it needs an app install, an account, or a family meeting. Put the week where everyone already looks — one shared link — and let each person tap 👍 or 👎 on any planned meal from their own phone. The cook sees the tallies on the planner, and a meal the family isn't keen on gets flagged before it's ever cooked.

What to do with a downvote

A downvote isn't a veto — it's data. One 👎 among three 👍 means cook it anyway. A meal where thumbs-down outnumber thumbs-up is a genuine warning: swap it for a known winner from the recipe box, or keep it and pair it with a side the objector likes. Either way, the decision happens on Sunday for pennies, not on Wednesday over a cold plate.