Two generations cooking together while one writes the recipe down
StoriesRecipes We Share TeamSeptember 8, 20266 min read

Cook It With Them: How to Write Down a Recipe Nobody Ever Measured

The recipes most worth keeping were never written down. Here is how to capture one from a person who cooks entirely by feel.

Best starting point

Use Recipes We Share for the working system, then use this guide to make better decisions.

The strongest archive combines product workflow with family judgment: the app handles structure, search, sharing, and AI assistance while your family adds context no tool can invent.

In Recipes We Share

  • Capture the original recipe and create a clean version.
  • Organize it so relatives can find and use it.
  • Add memories, comments, and versions as the recipe evolves.

What this guide helps you decide

  • What to prioritize first.
  • Where manual judgment matters.
  • How to avoid a system your family will abandon.
Explore app features

Ask for the recipe and you get: "Oh, I don't really have one. I just make it."

That is not evasion. It is true. After four hundred repetitions the recipe stopped being instructions and became a habit — and habits do not decompose into steps just because someone asks.

Which is why these are the recipes that vanish. Not the ones on cards. The ones in hands.

Here is how to get one down.

Do not ask them to write it

If you ask someone to write out a recipe they cook by feel, one of two things happens. They never get round to it, or they produce something that does not work — because when they try to write it, they reconstruct rather than observe, and the reconstruction is missing the parts they do without noticing.

The version they write down is usually wrong in exactly the ways that matter.

Cook it with them instead

You do not cook. You watch and write. This is the whole method.

Arrange to be there while they make it. If they are far away, do it on a video call — it works nearly as well, and it removes the excuse of distance.

Bring: a notebook, measuring cups and spoons, and a kitchen scale if you have one.

Measure what they pour

They pour salt into their palm. You say "hold on" and tip it into a measuring spoon before it goes in. Roughly a teaspoon and a half. Write that.

They will find this mildly annoying. Do it anyway. This is the entire value of being present: you are converting a handful into a number in real time, and nobody can do that afterwards from memory.

You will slow the cooking down. That is fine.

Write what they do not say

Watch for the things that never make it into a spoken recipe:

  • Pan size and material. "A cast iron skillet" changes the outcome.
  • Actual heat. Not "medium" — is it barely bubbling or properly spitting?
  • What it should look like. "Until it looks right" is real information if you pin it down. What does right look like? Ask.
  • The order they do things, which is often not the order they would tell you.
  • What they leave out. Recipes people recite from memory tend to skip a step they do automatically.

Ask the four questions

While it cooks:

  1. "Where did this come from?" You will often get a person and a decade.
  2. "Have you changed it?" Almost always yes, and the change is usually the reason theirs is better.
  3. "What goes wrong when it goes wrong?" This is the most useful answer in the whole conversation. It gives you the failure mode and how to avoid it — the thing no written recipe includes.
  4. "When do you make it?" Christmas, illness, new neighbours. This is the story.

Taste it and write the target

Before you leave, eat it and write down what it tastes like. Saltier than you expected. Sharper. Looser than it looks.

When you make it alone in two years and it comes out wrong, this note is how you work out which way wrong.

Write it up the same day

Not next week. The details fade fast and you will not notice them fading.

Type it while it is fresh, and include:

  • ingredients with the numbers you measured
  • steps in the order they actually happened
  • the pan, the heat, the visual cues
  • what it should taste like
  • who it came from and one thing about them

Then cook it alone, and correct it

The test. Make it from your own written version, without them, and mark up everything that was ambiguous.

"Medium heat" turned out to be too high. "Until thickened" needed eight minutes. The onion should be finer than you wrote.

Second draft after a solo cook is when it becomes a real recipe rather than notes.

Send it back to them

Two reasons. They will correct something — "no, the butter goes in cold" — which is worth the whole exercise. And it means a great deal to people to see their cooking written down and taken seriously.

Which one first

If several people in your family cook by feel, start with whoever is oldest, or whoever is furthest away, or whoever is unwell. That is not morbid, it is arithmetic. The cards in the drawer will still be there next year. This will not necessarily be.

One afternoon. One recipe. It is the highest-value hour in this entire subject, and almost nobody spends it.


Somewhere to put it once you have it: start free. Attach a photo of the original card if there is one, record who it came from, and give other family members access so it does not depend on you alone.

If your box of cards is next, the recipe box audit covers sorting it in a weekend.

Ingredient weights mentioned in this guide

Put the process into practice

Use Recipes We Share to save the recipe and the story around it

The platform is designed for the full workflow these articles describe: capture the original recipe, refine it into a clean version, save the notes and memory behind it, and share it with family in one place.

  • Preserve the original image and the cleaned recipe together
  • Attach memories, notes, and context while the details are still available
  • Share the finished recipe with family instead of passing it around manually

Related posts

More articles in stories to keep the momentum going.

View all posts