How to remember details about people (without pretending you have a perfect memory)

You know the person who, eight months later, asks how your sister’s surgery went — and you also know the hot flush of being asked “how’s the new job?” by someone whose name you’ve lost twice. The gap between those two people is not memory talent. It’s that one of them runs a system, and would probably admit it if asked.

Forgetting is the default — ‘great memory’ is usually a great system

Start with the uncomfortable baseline: conversational details are close to the worst-case input for human memory. They arrive once, unrepeated, in a noisy environment, while you’re busy formulating your next sentence. Ebbinghaus (1885) mapped how steeply unreinforced material drops away — most loss in the first hours and days — and a century of replication has kept the shape intact. Whatever someone told you at Thursday’s dinner is, by Sunday, a paraphrase; by next month, a vibe.

So how do the people who “never forget” do it? Mostly, they don’t — they out-process and out-capture you. Watch them closely: they repeat your news back to you, they ask the second question, and they spend a suspicious fifteen seconds on their phone right after you part. The performance of effortless memory is built on deliberate encoding and a note. That’s good news. A system can be copied; a gift can’t.

It also reframes what you’re optimizing. The goal isn’t storing everything — it’s reliably resurfacing the few details that make someone feel known: the names of the people they love, the thing they’re building, the thing they’re worried about, the loop you left open. Twenty well-chosen words per person cover all four.

Encode deeply while they’re still talking

Memory research has a precise name for why some heard things stick and others evaporate: depth of processing. Craik and Lockhart (1972) argued — and Craik and Tulving (1975) showed experimentally — that recall tracks how you process material, not how long you’re exposed to it. Words judged for meaning were recalled dramatically better than words judged for font or sound. Shallow in, shallow out.

Applied to conversation, deep processing is mostly a listening posture with three mechanical habits attached:

Connect it. When she says she’s training for her first triathlon, hook the fact to something you already own: your own abandoned couch-to-5k, the lake she mentioned, the fact that her race month is her startup’s launch month. Each connection is a retrieval path later — this is elaborative encoding doing its quiet work.

Say it back. “Wait — first triathlon, while shipping a product?” Repeating a detail in your own words forces semantic processing and, as a bonus, is exactly what good listening looks like from the outside.

Ask the second question. The first question anyone asks is social reflex; the second is where both encoding and intimacy happen. “Which discipline scares you?” embeds the triathlon fact in a story, and stories outlast facts.

Names deserve their own line, because they’re the detail people fail at most publicly. A name is arbitrary — there’s no meaning to process — so it has to be given meaning on the spot: say it back inside the first sentence, hook it to an anchor (a friend who shares it, the alliteration with their company, the city), and use it once more when you part. If it’s already gone, ask again early; “sorry, I lost your name in the noise” costs nothing in minute two and compounds awkwardness every minute after. When the name lands in your note later, write the anchor next to it.

None of this is note-taking yet. That’s deliberate: encoding is what you do in the conversation, with full attention. The phone stays away until afterwards — which brings us to the part most people skip.

The 30-second note

1. Capture within five minutes, not five hours

   The walk to the car, the elevator down, the queue for coffee — that’s the window. The curve is steepest right at the start, and the specifics (names, numbers, exact phrasings) fall first. Thirty seconds now beats ten minutes of reconstruction tomorrow, and a three-word voice memo beats both if your hands are full.

2. Write four things, telegram style

   Context: where, when, who introduced you. Topics: what actually animated them, not the polite preamble. Open loops: promised in either direction. Personal details: one or two, in their words. GDC afterparty via Tomás — building climbing gym in Leipzig — I owe him the permit contact — daughter Ada, born March. Twenty words; done.

3. File it where it will resurface

   A note that can’t find you again is a diary, not a system. Attach it to the contact record, the row in your networking tracker, or wherever your follow-ups live — the point is that the note and the person stay joined. Over time these entries become an interaction log: a running history that turns ‘I think we discussed this?’ into a fact you can check.

4. Review it right before you meet again

   This is the spacing effect earning its keep. Cepeda et al. (2006), meta-analyzing 254 studies, confirmed that reviews distributed over time massively outperform massed study. The relationship version is almost free: ninety seconds with your notes before the call or the dinner. Try to recall first, then check — retrieval practice strengthens the memory more than re-reading does. After a few spaced refreshes, you’ll find you no longer need the note for that person at all.

Where do the notes live? Anywhere that pairs them with a resurfacing mechanism. A text file works at ten relationships. At fifty-plus, the bottleneck becomes retrieval at the right moment — which is the job personal CRMs exist for, and the reason we built Endearist with the note pinned to the reminder: when someone resurfaces, their context comes with them. Whether you need that category of tool at all is a fair question with an honest answer in personal CRM vs. your contacts app — and if your notes mostly feed post-event follow-ups, the follow-up guide shows what those twenty words buy you in practice.

The ethics of writing things down about people

Noting details about people sits in a strange cultural spot: universally practiced — by doctors, managers, diplomats, and anyone who’s ever written “Lena, Jakob’s sister, vet” into their phone — and rarely discussed. So discuss it. The practice is legitimate; it also has real lines.

Record what was offered, not what was extracted. The triathlon, the daughter’s name, the job worry — these were handed to you in conversation. A detail someone shared with you is yours to remember; a detail you assembled about them from observation and inference starts to smell like surveillance.

Write observations, not verdicts. “Seemed stretched thin, project at risk” will age fine. “Whiny, probably failing” is a verdict that poisons every future interaction — you’ll meet your note instead of the person. Speculation about health, relationships, or motives doesn’t belong in writing at all.

Apply the read-aloud test. Would you be comfortable if the person read the note? This single check enforces nearly everything else — tone, content, intent. It’s not hypothetical hygiene either: notes written this way genuinely change how you show up, because what you rehearse about a person is what you bring to them.

Know the legal frame, loosely. Private relationship notes fall under the GDPR’s household exemption — purely personal use sits outside its scope. Use the notes commercially and the rules change. And independent of law: when a relationship ends or a note stops serving care, delete it. Forgetting, done on purpose, is also a form of respect.