What are your three default meals when you don’t have a plan? Are they good defaults?
The Short Answer
Defaults shape outcomes. When you’re tired, busy, or unprepared, you fall back on defaults, the meals you make without thinking. If your defaults are healthy (rotisserie chicken and vegetables, eggs and avocado, salad with protein), your unplanned eating is fine. If your defaults are problematic (delivery pizza, cereal, fast food), your unplanned eating undermines your goals. Designing good defaults works at the moment you have least capacity to decide, which is what makes it worth the effort up front.
Something to Sit With
You won’t always have a plan. What happens then determines your real eating pattern.
What do you default to, and is that working?
Learn More
Why defaults matter. People stick with defaults even when alternatives are freely available: changing takes active effort, and not changing takes none.[1] Life doesn’t always cooperate with meal planning:
Evening. By the end of the day you want the option that asks least of you. Make that option a good one.
Unexpected changes. Plans fall through. Ingredients spoil. Meetings run late.
Frequency. Many meals are unplanned. If your defaults are poor, many meals are poor.
Your defaults aren’t exceptions; they’re a major part of your eating.[2]
Auditing your defaults. Think about your last several unplanned meals:
What did you eat? Not what you planned to eat, but what you actually ate when there was no plan.
How did you get it? Cooked quickly? Ordered delivery? Grabbed something on the way?
How did it align with your goals? Was the default good, neutral, or problematic?
Many people discover their defaults are worse than their planned meals.
What good defaults look like. Effective defaults share features:
Quick. They can be assembled in 15 minutes or less.
Simple. Few ingredients, minimal technique.
Satisfying. Protein, vegetables, enough volume and flavor to satisfy.
Always available. The ingredients are always on hand.
Examples:
- Eggs scrambled with vegetables and cheese
- Rotisserie chicken (bought ready-made) with bagged salad
- Canned fish over greens with olive oil
- Leftover protein with microwaved frozen vegetables
- Salad with deli meat and nuts
Building better defaults. Steps to improve:
Identify your current defaults. What do you actually fall back on?
Design three new defaults. Simple, healthy meals you can always make.
Stock the ingredients always. Eggs, canned fish, bagged salad, frozen vegetables: whatever your defaults require.
Practice them. Make your new defaults several times so they become automatic.
Remove old defaults. If your old default was ordering pizza, delete the app or remove the number.
The “no plan” plan. Your defaults ARE a plan: the plan for when there’s no plan. Designing them deliberately means even unplanned eating can be good eating.
This isn’t about perfection. It’s about raising the floor. When you’re at your most tired, most rushed, most unprepared, what happens? Good defaults mean even the floor is acceptable.
Further reading:
- Clear J, Atomic Habits[3] (2018) — Designing systems and defaults
- Thaler RH & Sunstein CR, Nudge[4] (2008) — Default options and choice architecture
- Hartwig D & Hartwig M, It Starts with Food[5] (2012) — Simple whole-food meals
Written by AI, directed and approved by me. How this is made →