Her grandchildren know almost nothing about her

Today's Tip: Turn One Small Memory Into A Story Worth Keeping

Your grandchildren know your name and your address… and almost none of the stories that made you.

Let me explain…

Grandparents Day was Sunday. Sioux Falls, South Dakota, had good weather for it. My friend Bev Osterberg spent the afternoon on her front porch with a mug of coffee and a plate of her mother's spritz cookies, waiting for her son to bring the kids over.

They came. They stayed twenty minutes. Then they were back in the van, off to the next thing.

Bev is sixty-seven. She keeps the books two mornings a week for the Presbyterian church on 26th Street… and she knits tiny wool caps for the NICU on Wednesdays. She is not a writer. She was never going to sit down and pen a memoir.

But she has stories. And her grandchildren do not know them.

She does not know that her grandmother came through Ellis Island alone at seventeen. She does not know about the summer Bev spent as a nineteen-year-old counting fish for the Department of Game and Parks up near the Missouri. She does not know why Bev still cannot look at a jar of pickled herring without laughing.

So on Sunday night, after everyone had gone home, Bev tried something. She opened Claude on her laptop and typed one sentence about the summer with the fish.

Twelve minutes later she had two full pages. In her own voice.

Here is how she did it.

She did not try to write the story herself. That would have taken her three weeks and produced half a paragraph.

Instead, she gave Claude a starting point — one memory, one sentence — and asked it to interview her the way a good reporter would. Ask me questions. Get the story out of me. Then write it up.

The prompt below is the one she used. Copy it, paste it, replace the seed memory with your own.

Bev started with two sentences: "The summer I was nineteen I worked for the Nebraska Game and Parks counting paddlefish on the Missouri River. My cousin Larry drove up from Omaha every Friday with a case of beer and made me laugh so hard I nearly fell in twice."

Claude asked her about the boat. About the smell of the mud. About the color of the sky at five in the morning. About what her mother had said when she told her she was taking the job. About whether she was scared. About what Larry looked like then, and what he looks like now.

She typed short answers. Four words here… a sentence there. It took her about ten minutes.

Then Claude wrote the story. Four hundred and eighty words. Her voice. The paddlefish, the mud, the sunrise, her mother's face, Larry's laugh. It was not fancy. It was hers.

She printed two copies. One for the drawer. One folded into a birthday card for her granddaughter, who turns twelve next month.

I know what you are thinking… "This feels like cheating. If Claude wrote it, is it really mine?"

Fair question. Here is the honest answer.

Every fact in Bev's story came from Bev. Every feeling, every name, every detail of the mud and the light and her mother's voice on the porch — all of it, hers. Claude asked questions. Bev answered them. Claude arranged her answers into paragraphs.

Nothing was added. Nothing was invented. If you dictated a letter to your granddaughter and she typed it up cleanly for you, you would still call it your letter. This is the same thing.

The other worry I hear is the one about tone. That AI writing sounds stiff or sappy or fake. It can. That is why the prompt says "plain and warm," "short sentences," and "no fancy words."

If the first draft still sounds off, tell Claude what is wrong. "Too flowery." "You made me sound sad. I was not sad, I was tired." It will fix it. That is what it does.

Start with the smallest thing. Not your whole life. Not the big trip.

One afternoon. One argument. One time you were scared and someone was kind. One kitchen. One car. One song on the radio.

Give Claude the seed. Let it ask. Answer as short as you like.

In twelve minutes you will have a page your grandchildren can hold in their hands forty years from now.

★ Quick Wins

Skill Builder: The Follow-Up Prompt

There is a small habit that separates people who get good answers out of AI from people who get generic ones. It is not typing longer prompts. It is not learning fancy tricks. It is one question… added to the end of anything you ask.

The question is: "What else do you need to know from me before you answer?"

Most people type a request and hit send. Claude does its best with what it has. But you almost always know things it does not… things that would change the answer if you had thought to include them. The follow-up question turns Claude from a guesser into an interviewer. It stops guessing and starts asking.

Here is how it plays out. Ask Claude, cold, "Help me write a note to my sister apologizing for the argument at Thanksgiving." You will get a generic apology. But add "What else do you need to know from me before you write it?" and Claude will ask what the argument was about, how old the disagreement is, what your sister tends to react well to, and whether you want to open a conversation or close one.

Answer three of those and the note you get back is unrecognizable from the first one. It is yours.

It works for almost anything. Doctor questions. Contractor bids. Vacation plans. Drafting a difficult email. Comparing two health plans.

The bigger the decision, the more you want Claude asking, not guessing. Save the prompt below and paste it after any request from now on. It is thirteen words. It will change everything you get back.

The rule of thumb is this: if the answer matters, ask Claude what it needs first. If you are just curious about the population of Bolivia, hit send. If you are writing to your sister, or comparing two plans, or drafting a note to your doctor… let it interview you.

Ten seconds of typing thirteen more words is the difference between a generic answer and one that sounds like it came from someone who actually knows you.