It's 6:40 on a Wednesday. Someone asks what to eat tonight, and the room goes quiet. You float a place. It gets a shrug. You float another. "Eh, we had that last week." Twenty minutes later you're three apps deep, still hungry, and quietly annoyed at each other โ and the only thing that's been decided is that nobody wants to decide.
If that scene feels familiar, you're not indecisive. You're stuck in the worst possible version of a simple problem: an open-ended question with too many right answers and no good way to choose between them.
Why "what to eat tonight" is so hard to answer
The trouble isn't a lack of options โ it's the opposite. Within a short drive there are hundreds of places that would all be perfectly good. When every choice is defensible, none of them is obvious, and your brain keeps holding out for the one that's slightly better than the rest. So you scroll, comparing menus you'll never order from, hunting for a certainty that doesn't exist.
That holdout has a name. Psychologists call it the paradox of choice: past a certain point, more options don't make us happier, they just make us slower and more anxious. We wrote a whole piece on the paradox of choice and dinner if you want the longer version. The short version is that the perfect meal isn't out there waiting to be found. There's just a pile of good-enough dinners and a clock that's running.
You don't need the best restaurant tonight. You need a decision tonight.
The 10-second method
Here is a method that actually fits in ten seconds, because it doesn't ask you to evaluate anything. It asks you to constrain, pick, and commit.
First, constrain. Don't ask "where should we eat?" โ that opens the whole map. Ask one narrowing question instead: how far are we willing to drive, and is there any cuisine we're definitely not in the mood for? That's it. You've gone from hundreds of options to a manageable handful without agonizing over any of them.
Second, pick one. Not a shortlist โ one. A shortlist just restarts the argument at a smaller scale. Name a single place, out loud, with no hedging.
Third, commit and go. The instant a name is on the table, the job is to stop reconsidering. The discomfort you feel in the next few seconds isn't "this is wrong," it's just the withdrawal from optimizing. It passes the moment you're in the car.
Let something else make the call
The hardest part of that method is the picking, because the person who names the place quietly owns it if it's a dud. That's why "I don't care, you pick" is so common โ nobody wants to be responsible for the choice. The fix is to take the responsibility off of any one person entirely and hand it to something neutral.
That's the whole idea behind Tonight's Table. You set where you are, choose a radius up to 45 miles, and either pick a cuisine or hit Surprise Me. Tap once, and it returns a single real restaurant near you, pulled from Apple Maps and tilted toward the small, independent spots that never surface on their own. Don't love it? Tap again to re-roll. You can hide chain restaurants, and "give me something new" will skip places you've already logged. There's no account and no sign-up โ just a button that breaks the standoff. (It's a free app supported by ads, with a one-time option to remove them if you'd rather.)
The goal was never the perfect meal
It helps to remember what you're actually after on a random Wednesday. Not a once-in-a-lifetime dinner. Just a good dinner, eaten with people you like, without the twenty-minute negotiation that sours everyone's mood before the food even arrives. A decent meal you reached in ten seconds beats a marginally better one you reached after an argument.
Make the decision small, make it fast, and let the night be about the table instead of the search bar. If you keep landing back in the same handful of places, that's worth fixing too โ here's how to break the five-restaurant rut. And when you just want the question answered for you, Tonight's Table is one tap away.