Food stories & preservation guides

The recipes you haven't written down yet.

This section is about the other side of family cooking. The why behind the what, and the practical work of capturing what your family makes before it gets away from you. Stories and guides, both.

An older pair of hands writing a recipe in a cloth-covered journal on a kitchen table

Why it matters

What disappears when a recipe goes unrecorded

Think for a moment about the dish you most associate with a specific person — a grandparent, a parent, an aunt or uncle who cooked without thinking about it. Now ask yourself: do you have that recipe? Not approximately. Actually.

Most people, when they really think about it, do not. The recipe lives in the hands of the person who makes it. It exists in muscle memory, in the smell of the kitchen, in the color of the onions when they're ready. Ask them to write it down and they say "I just know when it's done." That is not nothing. That is the hardest kind of knowledge to transfer.

When that person is gone, the recipe does not automatically vanish. But it starts to blur. You remember the ingredients but not the order. You remember it was chicken but not which cut. You remember the smell but can't reproduce it. The dish becomes a ghost that haunts every attempt you make in your own kitchen.

I have talked to hundreds of people who have lost a recipe this way. It is a specific kind of grief. The ordinary domestic tragedy of something delicious and unrepeatable just ending. This page is an attempt to help you avoid that.

Practical guide 01

How to interview an older relative for a recipe

The worst way to get a recipe from someone who cooks from instinct is to ask them to "just write it down." They will write you a list of ingredients with no quantities and no method, and you will spend years figuring out the rest.

The better approach is to cook alongside them and talk while you work. Here is how I do it.

  1. Ask to cook it together, not to be taught. "Teach me" puts pressure on them to explain things they don't consciously know. "Let's make it together" is more relaxed. You are helping, not being instructed.
  2. Bring a notebook and write in real time, not from memory later. Write down everything you see. The size of the pot, the color of the onions before they add the next thing, the sound of the sizzle. Those sensory cues are the recipe.
  3. Ask comparative questions, not absolute ones. "About how much salt, like a palmful or more like a pinch?" works better than "How much salt do you use?" They cannot answer the second question. They can usually answer the first.
  4. Film the process on your phone. Ask permission first. Even just propping your phone against the backsplash to capture the hands and the pot gives you something to return to. Watch the footage later and write down what you missed.
  5. Ask about the origin after, not during. While cooking, focus on the technique. After the dish is done and you're eating it, ask about where it came from. "Was this your mother's recipe too?" opens up memory in a different way.
  6. Make it yourself and show them. Cook your version and bring it to them. Their reaction (what they correct, what they approve of) is more useful than anything they could tell you in the abstract.
Two people cooking together at a kitchen stove, with a large pot and wooden spoon in view

Practical guide 02

How to write down a "pinch of this" recipe

A true heritage recipe often has no measurements at all. The cook knows what a "handful" means because their hands are a specific size. They know the pot is ready when the smell changes. These things are not transferable without translation, but they can be translated.

Here is the method I use when I'm converting an intuitive recipe into something a stranger could follow.

Step 1: Measure once, cook normally

The first time you make it after watching the original cook, do everything exactly as you observed it, but measure everything into small bowls first, the way a TV cooking show works. You are not changing the recipe, just getting numbers attached to each step. Weigh the butter before it goes in. Measure the flour after scooping it the way they scooped it. Use a thermometer on the liquid.

Step 2: Describe the visual cues

Instead of writing "cook onions until soft," write "cook onions over medium heat, stirring every couple of minutes, until they are golden at the edges and fully translucent, about 12 minutes." The time and the description together give a reader two different ways to know when to move on. One or the other will be right depending on their stove.

Step 3: Note the pan and the heat

The size and material of the pan changes everything. A recipe that works in a 12-inch cast iron is a different recipe in a 10-inch stainless, even with identical ingredients and timings. Write down the pan. Write down whether the heat was medium or high or a low flame that barely made the butter foam. These details feel obvious to the cook and invisible to the reader, which is why they always need to be written.

Step 4: Write a "what it should look like" note at the end

End every recipe with a brief description of the finished dish. Color, texture, smell, any signs that it did not go right. "The sauce should coat the back of a spoon and leave a clear line when you draw your finger through it. If it's still thin after 15 minutes, turn the heat up slightly and give it another five." This gives the cook a target, not just a process.

A recipe written this way (measurements, visual cues, pan specifics, and a description of the result) can be followed by someone who has never made the dish before and get to something close on the first try. That is the goal.

A handmade family recipe book open on a wooden table with a cup of coffee beside it

Practical guide 03

Building a family cookbook that people will actually use

Most family recipe projects never get finished. Someone starts a binder, gathers a few index cards, runs out of momentum, and the binder sits in a drawer for a decade.

The ones that get finished share a few things in common. They have a clear scope — not "every recipe we know" but "the twenty dishes we make at Christmas" or "the five things Dad cooked." They have someone who is actually in charge of it, not a committee. And they include photographs, even imperfect ones taken on a phone.

Start small. One meal, one occasion, one person. Get those recipes written and tested, add a photo, print and bind them in a simple folder. That first finished section builds momentum. Five recipes done completely is worth more than fifty recipes half-started.

For format: a two-column layout works well for print, with the ingredient list on the left and the method on the right. Keep each recipe to a single page. Add a short paragraph above each recipe about its origin — even two sentences of history is enough to give the recipe a human face.

About this blog

"The recipes we lose are not just instructions. They are the taste of a specific life, in a specific kitchen, in a specific time."

Start with one recipe.

You don't need a plan, a binder, or a system. You just need to pick one dish and write it down this week. Browse the recipe collection for inspiration, or read more about the blog.

Browse the recipes