You’ve made too many food decisions today and you’re exhausted. What’s your fallback?
The Short Answer
Have a predetermined fallback for the hours when you don’t want to decide anything. When the moment arrives, the fallback decides for you — a default meal you’ve pre-selected that requires no thought and no willpower. This isn’t about the perfect choice; it’s about the good-enough choice you can execute on autopilot when your decision-making capacity is spent.
Something to Sit With
The worst food decisions happen when you’re too tired to decide.
What if that moment was already decided, in advance?
Learn More
Why the evening decision goes badly. Not because a reserve has run out — whether self-control works that way is genuinely unsettled[1] — but for two plainer reasons:
You are choosing while tired and hungry. Neither state makes anyone a better judge of what they will want to have eaten.
The default wins by construction. Most choices run on fast, automatic thinking; overriding a default takes the slow, effortful kind, and at the end of a day that is what you are least willing to spend.[2]
By evening, whatever is already the easy option is very likely what happens.
Why this matters for eating. Food decisions are constant:
What to eat. Each meal, each snack, each moment of hunger.
Whether to eat. Cravings, offers, availability — each requires a decision.
How much. Portions, seconds, stopping points.
By day’s end you’ve made hundreds of food-adjacent decisions, and the next one arrives when you have the least appetite for deciding anything.
The fallback solution. Instead of deciding in the moment, pre-decide:
Select a fallback meal. One or two meals that are:
- Healthy enough that you’re not compromising goals
- Simple enough that you can execute without thinking
- Satisfying enough that you won’t feel deprived
- Always available (ingredients consistently stocked)
Make the decision in advance. When you’re clear-headed, decide: “When I’m too tired to decide, I eat X.” That if-then shape is an implementation intention, and it is the best-supported thing on this page — such plans help most exactly where getting started is the hard part.[3]
Execute without rethinking. When the moment arrives, don’t reconsider. The decision is made. Just execute.
Good fallback characteristics. Effective fallbacks share features:
Minimal preparation. You are not going to cook an elaborate meal at that hour, so don’t pick one.
Minimal decisions. Ideally, a single dish, not multiple choices.
Ingredients always present. Stock your fallback ingredients consistently.
Reasonably healthy. Not perfect, but within bounds.
Examples:
- Scrambled eggs with whatever vegetables are on hand
- Rotisserie chicken (bought ready) with bagged salad
- Canned fish on greens with olive oil
- Pre-made healthy frozen meal you’ve vetted
What the fallback prevents. Without a fallback:
The “what should I eat?” spiral. Asked cold, at the wrong hour, the question has no good answer. You stare at options, unable to choose.
The default to delivery. The path of least resistance, once you are past deciding, is usually whatever arrives fastest.
The “forget it” response. Skipping meals when tired, then overeating later.
Building the habit. Steps:
- Choose your fallback now, while clear-headed
- Stock the ingredients
- Practice making it a few times
- Name it: “My fallback is X”
- When the moment comes, invoke it without debate
Further reading:
- Atomic Habits by James Clear — Systems and defaults[4]
Written by AI, directed and approved by me. How this is made →