Writing Recipe Notes Your Family Can Actually Follow

My sister in law texted me a photo of a pot roast that looked nothing like the one I make, next to the recipe card I had written out for her by hand, and asked what she did wrong. She had followed every line. The problem was not her cooking, it was my card, which told her to cook the onions until soft and season the broth to taste, two instructions that meant something specific in my head and almost nothing on paper.

Why Season to Taste Fails More Often Than It Helps

Season to taste assumes the reader already knows roughly what the dish should taste like when it is right, which is only true for someone who has eaten it before. For a new cook or a new recipe, that instruction is not guidance, it is a gap where guidance should be. A better version names a starting amount and a specific check, something like half a teaspoon of salt, then taste and adjust in small increments, because a range with a floor gives someone an actual place to start instead of a blank space to guess at.

Writing for Yourself Versus Writing for Someone Else

A recipe card scrawled for your own use during a busy week is allowed to be short, because you already carry the missing context in your head. The moment that card is meant for someone else, every shortcut you took becomes a decision they have to make without the information you had. Cook until done works fine as a personal reminder and fails completely as an instruction to a person who does not know what done looks like, smells like, or feels like on a fork.

A Structure That Removes the Guesswork

The fix I use now is a simple three part structure for anything that is not purely measurement. State the ingredient in the state it should be in before the step starts, chopped fine or fully thawed rather than just named. State the action with a specific verb, simmer rather than cook, since simmer tells someone what the surface of the pot should look like. Then give a doneness cue that does not depend on a clock alone, since ovens and stovetops vary enough that a time range without a visual or textural check will fail for someone whose equipment runs differently than mine.

Where I Actually Understood This as a Communication Problem

The clearest explanation I ever found for why instructions like mine kept failing did not come from a cooking source at all. It came from reading through Cuesta Comunicacion Total, a site focused on plain communication between people who assume they are being clear, which turned out to describe my recipe cards almost exactly. The gap between what a person writing instructions knows and what a person reading them knows is the same gap whether the topic is a pot roast or a work memo, and treating it as a kitchen specific problem kept me from noticing the actual fix for years.

Why More Detail Is Not Always Clearer

The common advice once you notice a vague recipe is to write down every single step in exhaustive detail, and I tried that for a while with poor results. A card with forty short, granular lines buries the two or three steps that actually determine whether the dish turns out right, because a reader skimming a long list gives every line roughly equal weight. The fix was not more detail everywhere, it was more precision exactly at the two or three moments where a wrong guess ruins the dish, and less fuss around the steps that are genuinely forgiving.

The Words That Quietly Cause the Most Damage

A few words do more damage than the rest, and I now watch for them specifically when I edit a card. Some, a handful, a splash, and to taste all assume a shared sense of scale that a new cook simply has not built yet. Soft, tender, and golden are useful only if the reader has seen what those words mean on this exact dish before, otherwise they are describing a result rather than helping someone reach it. Replacing even three or four of these words with a number, a time, or a visible sign, like the edges pulling away from the pan, fixes more confusion than rewriting the whole card from scratch.

Why Family Recipes Get Vaguer, Not Clearer, Over Time

It seems backwards that a recipe made hundreds of times in one family often becomes harder to follow rather than easier, but the pattern makes sense once you notice it. Each time someone who already knows the dish writes it down, they trim a little more of what feels obvious to them, and what feels obvious keeps shrinking as their own familiarity grows. Three generations later the card says simmer until right, a phrase that meant something specific to the person who wrote it and almost nothing to anyone else, including their own grandchildren trying to recreate a holiday dish from memory and a scrap of handwriting.

Testing a Card on Someone Who Never Watched You Cook

The real test of a written recipe is not whether you can follow it, since you already know the dish. Hand it to someone who has never seen you make it and watch where they hesitate. My sister in law's confused pot roast turned out to be useful in the end, because it showed me exactly which two lines needed rewriting rather than leaving me to guess. I now do this deliberately before I consider a family recipe finished, the same way I test any new dish before serving it to guests, which I wrote about in betting on a new recipe without testing it first.

What This Changed About How I Write Recipes Now

Every card I write for someone else now gets one more pass specifically for vague verbs and missing states, the same care I put into building a plan in how to build a weeknight meal plan in 15 minutes, where the whole point is removing decisions at the moment someone is tired and rushed. The habit of reading a recipe fully before cooking it, which I covered in reading a recipe before you start cooking it, only works if the recipe rewards that close reading with real information. More on getting weeknight cooking to actually work lives in Weeknight Meals.