Culture / Food & memory / Field guide 037
Save the recipe.
Keep the story.
“A little of this” is not a measurement. “You know when it’s ready” is not a timer. Here’s how to turn someone’s beloved dish into a recipe another person can actually make—without scrubbing away the person behind it.
How much? Ask.
When does it turn? Watch.
Who taught you? Listen.
it again
The most important part of a handwritten recipe may be the thing it leaves out: how the cook knows the onions are ready, why a particular pan matters, or who showed them the trick. Those details are obvious to the person making the dish and invisible to the person reading the card.
A reliable recipe and a family story are related, but they are not the same record. The recipe should let a new cook reproduce a result. The story should let the original cook speak in their own terms. Preserve both, and keep uncertain details visibly uncertain rather than quietly guessing. You can do this for a parent, a friend, a neighbor or your own favorite dish. Ask before recording, photographing or sharing someone else’s words.
Start with the person, not the ingredients.
Ask: “Could I write this down while you make it? Is there any part of the story you’d prefer I keep private?” If the answer is no, put the notebook away. If they agree, write their preferred name or attribution, the date and whether the record is for yourself, a small family circle or wider sharing.
Begin with an open invitation: “Tell me how this dish became yours.” Then let the answer wander. The Library of Congress encourages listening without interruption when preserving family stories; Boston Public Library’s oral-history guidance recommends open-ended prompts, clarifying questions and avoiding leading assumptions. [1, 2]
You do not need an audio recording to capture something meaningful. Pen and paper are enough. If you do record, agree on where the file lives, who gets a copy and whether it may be shared. Permission to interview is not automatically permission to publish.
Follow the hands through one complete cook.
Write what actually happens, in order. Capture ingredient names, brands only where relevant, quantities, equipment, pan size, heat setting, start and stop times, texture and visible cues. Ask about a decision exactly when it happens, rather than trying to reconstruct it from memory later.
“A handful” becomes a measured amount, ideally while the cook makes the usual batch.
“Until done” becomes an observable cue and an approximate time, marked as a range.
“Sometimes I add…” becomes an optional variation, not part of the only method.
Keep the authentic phrase in a margin alongside the tested specification. “Just a good pinch” can remain a wonderful quote while the recipe records the measured amount used in that batch. If the person declines measurement, write “not yet measured” instead of filling in a plausible number.
Separate the cook’s observation from your inference. “Pan looks dry at minute six” is observed. “Medium-high is always best” is an interpretation and might not transfer between stoves. When the dish depends on temperature for safety, use a thermometer and current authoritative safe-temperature guidance; appearance or a family habit is not proof of safe cooking. [3]
A fictional transcription example
Two columns. One complete handoff.
Imagine a cook says, “Let it settle while everyone finds a plate.” The line contains atmosphere and an instruction, but not enough detail to reproduce the step. Keep the quote in a story field. In the method field, record the actual measured resting time from a witnessed batch—if you have one. Never invent a number just because a recipe looks empty.
These sample lines are illustrative editorial examples, not an actual interviewed cook or tested recipe.
What the cook said
“Let it settle while everyone finds a plate.”
What the next cook needs
Observed rest: ______ minutes after heat is turned off.
How it changes: ______ (texture, surface, scent, other observable sign).
Story note: The speaker’s words, with permission to keep/share.
Make each step survive a different kitchen.
Write ingredients in the order used, set a clear yield (“makes six small servings,” only if observed), specify the tool or vessel that affects results, and use numbered verbs. Do not rely on “do the usual thing” or “cook like you always do.” Mark choices clearly: required, optional, and uncertain are different categories.
Put the sensory details beside the relevant action, not in a distant paragraph. “Stir until the mixture coats the spoon, approximately five to eight minutes in this observed batch” is more useful than an unqualified universal instruction. Where safety matters, include safe handling and verified temperature requirements separately; adapting a cherished recipe never overrides basic food-safety standards. Penn State Extension’s recipe-safety guidance provides a useful check for written temperature, chilling and handling instructions. [4]
Keep two versions, not two competing truths.
Working recipe: what was observed or tested, with units, timing, tools and caveats. Story margin: the speaker’s own words, the occasion, a variation they love and the reason the dish matters. If you have only the story, say it is an oral account—not a tested recipe.
Give the instructions to fresh hands.
The best test is another cook following the written recipe without a narrator filling gaps. If someone you already know willingly tries it, ask them to mark exactly where they hesitated: a missing temperature, ambiguous quantity, pan choice, texture cue or sequence. This is an optional personal practice, not a request to recruit strangers or send feedback to Real Manly.
Version the result. Label the first capture observed batch, the next reader-tested revision only if that test actually happened, and the final date and permission status. Never retroactively claim a dish was tested because the method looks complete. If variants differ, keep both with attribution instead of presenting a single “authentic” universal version.
Sometimes the cook’s answer will be “I don’t know; I just feel it.” That is not a failure. Record the uncertainty, make the next observation specific and allow the story to remain larger than the instructions.
The recipe conversation desk
Find the next honest question.
Choose what you are preserving and what is missing. This small original prompt builder works only in your browser. It does not upload, send or save answers. Copy the suggestion into a notebook or use the one-page printable card.
Source and method notes
Where the guidance comes from.
This article’s four-step capture method and fictional examples are original Real Manly editorial synthesis. It is not an interview with an actual cook, a tested food recipe or a safety certification. For real cooking instructions, verify safety and details in the particular dish and context.
- Library of Congress, “Preserving Family Stories” — narrative prompts and listening practices.
- Boston Public Library, “Crafting Questions” — open-ended, non-leading questions, clarification and thoughtful follow-ups.
- FoodSafety.gov, “Safe Minimum Internal Temperatures” — thermometer-based safety information for relevant ingredients.
- Penn State Extension, “Key Food Safety Instructions for Recipes” — food-handling guidance when writing recipes.