Meal planning without recipes

Why recipe apps make the dinner question harder

Open any recipe app and you're handed ten thousand dinners you've never cooked. That's a discovery tool — and discovery is not the problem most households have. The problem is a decision: it's Tuesday, everyone's hungry, and someone has to name a dinner in the next ten minutes. A bigger catalog makes that moment worse, not better. Now the choice isn't between the eight meals you know; it's between the eight meals you know and an infinite scroll of ones you don't, each with an ingredient you'd have to buy and steps you'd have to read at the stove.

Psychologists call it choice overload; you've felt it as the twenty-minute browse that ends in takeout. The dinners that get cooked on a weeknight are almost never last night's saved recipe. They're the ones your hands already know — the taco filling you can brown while helping with homework, the traybake you can assemble without measuring anything.

Check your own evidence: if you've used a recipe app for a while, look at the gap between your saved count and your cooked count. Hundreds bookmarked, a handful ever made, and the ones you repeat are dishes you knew before the app. Saving a recipe scratches the planning itch without producing a plan — it's the cooking equivalent of buying a gym membership in January.

To be fair, sometimes recipes are the answer. If you're in a genuine rut and every meal on your list makes you sigh, a new dish is the fix. If a diagnosis just changed how your household eats — celiac, diabetes, a dairy allergy — you need new meals, and recipes are how you learn them. Recipe apps are good at that job. But that's an occasional job. The nightly job is picking from what you already know, and for that you don't need a catalog. You need a list.

Write down your invisible menu

Every household already has a menu; it's just unwritten. Getting it on paper takes about fifteen minutes, and it's the single highest-leverage step in this whole guide. Sit down — together, if you cook together — and list every dinner your household makes. Not dinners you aspire to. Dinners that have appeared on your table more than once in the last year.

Memory alone will stall around eight, so use prompts:

• Your camera roll. Scroll back through a few months of photos — dinners show up in the background more often than you'd think.
• Your grocery history. If you order groceries online, past orders are a map of what you cook. Tortillas every other week means tacos belong on the list.
• Your takeout orders. The pad thai you order monthly points at a stir-fry-shaped hole in your rotation — or at a meal to plan takeout as, on purpose.
• Each other. "What do I make that you'd be sad to lose?" turns up meals one partner had stopped counting.

Expect the list to run longer than you'd guess — 15 or 20 entries is normal by the end. Write them all down, including the barely-cooking ones — quesadillas, breakfast-for-dinner, the rotisserie chicken you dress up with a bag salad. If your household eats it and someone can produce it, it's a meal. No entry is too humble; the humble ones are the load-bearing ones on a Wednesday.

Once the list exists, give it one light layer of structure: mark each meal fast (under 30 minutes, no thinking), medium (45 minutes or a bit of chopping), or weekend (a roast, a slow braise, anything you enjoy but wouldn't attempt on a school night). That's all the metadata a week needs — busy nights pull from the fast column, Sunday pulls from the weekend column. This list is the raw material for every week you'll ever plan: from now on, "what's for dinner this week?" means picking seven lines from a page, not conjuring dinner from a blank fridge.

Formula dinners: cook in lanes, not from recipes

Look at your list and you'll notice most entries aren't really recipes — they're patterns. A protein, a carb, a vegetable. Naming those patterns makes your menu even more flexible, because a formula dinner isn't tied to exact ingredients. "Chicken thighs + rice + whatever green is in the fridge" is one line on your list, but it's a dozen different dinners depending on what the store had and what's wilting in the crisper.

Cooking in lanes removes the two anxieties recipes create. There's no ingredient anxiety — a formula survives a missing item, because spinach becomes green beans becomes frozen peas without the meal falling apart. And shopping gets simpler: you buy in categories (three proteins, two carbs, four vegetables) instead of hunting down one tablespoon of an exact thing. Here are eight formulas that cover most weeks, each with a real dinner it produced at my house:

None of these need a recipe open on the counter. Season the protein, cook the carb the way you always do, and let the vegetable be whichever one you have. If a formula shows up on your invisible-menu list three times in different costumes, write it down as the formula — that's one entry doing the work of three.

A no-recipe sample week

Here's what a week looks like when every night comes from a known meal or a formula. Seven real dinners, zero recipe consultations, one grocery trip:

Notice what the week does: the fastest meals land on the busiest nights, Friday has a ritual instead of a decision, and Sunday's dinner is designed to sweep the fridge clean before the next shop. Steal it as-is, or rebuild it from your own list — the shape matters more than the specific dishes. In FamilyPlate, a week like this takes a couple of minutes: each dinner already lives in your meal library, so planning is picking, not typing.

The shop for this week is one trip and mostly categories: sausages, ground beef, chicken thighs, burger patties, frozen fish fillets; potatoes, oven fries, rice, penne, tortillas; peppers, spinach, peas, salad, plus eggs, cheese, and a jar of sauce. If the store is out of spinach, Thursday gets green beans and nothing else changes. A recipe-based week snaps when one ingredient is missing; a formula week bends.

Keep the list alive without a binder

The failure mode of every paper system is the same: the list lives on one fridge, in one person's handwriting, and slowly stops matching reality. The meal list only keeps working if it's shared, current, and attached to the actual week — which is the shape of a shared meal library, and it's the exact thing FamilyPlate was built around.

The library is the list you just wrote, kept alive. You save each dinner once, with its usual ingredients — "tacos" knows it needs ground beef, tortillas, cheese, lettuce, salsa. Everyone in your household sees the same library and can add to it, so the meal your partner makes that you can never quite name is in there too, spelled out. Each week, you plan by picking meals from the library and dropping them onto days, and the shopping list assembles itself from the ingredients of whatever you planned — no second transcription step, no recipe app ever opened. When someone swaps Thursday for pizza, everyone else's phone gets a notification instead of a confused text from the grocery store. The core of that — shared library, weekly plan, automatic shopping list, household sharing by 6-character invite code — is free on iPhone.

And when you do want something new, the system has a place for it: cook the new dish once, and if it earns a repeat, save it to the library with its ingredients. Your invisible menu becomes a visible one that grows a few meals a year — which is exactly as fast as real rotations grow.