Think of the last time someone said, "Hi, I'm Dana," and you replied, "Great to meet you," with total warmth. Ninety seconds later, you couldn't have told anyone her name under oath.

Now think about what came next. You steered the conversation carefully, avoided any sentence that needed a name, and hoped she wouldn't notice. Maybe she did. Maybe she was doing the same thing about yours.

We treat forgetting a name as a small moral failure, proof that we didn't really care. It almost never is. It's a predictable quirk of how memory works, and once you see the mechanism, the fix is surprisingly mechanical.

A name is the hardest kind of information to hold

In 1990, the psychologist Gillian Cohen published work on why putting names to faces is so hard. One of the findings has become known as the Baker/baker paradox. Tell people that a stranger's occupation is baker, and later they're more likely to remember it than if you tell them the stranger's surname is Baker. Same word, same face, very different staying power.

The reason is that a job comes with meaning. "Baker" connects to flour, early mornings, warm bread, a hundred things you already know. Those connections are hooks, and memory hangs on hooks. A name like Dana is mostly an arbitrary label. It points to nothing. It has to be stored almost bare, with little to anchor it.

This also explains why names are the classic tip-of-the-tongue casualty. You can recall where someone works, what they said about the budget, even the color of their jacket, and still come up empty on the one word that identifies them. The rest of the memory was richly connected. The name was not.

You probably never stored it in the first place

Here's the less comfortable part. Often the name wasn't forgotten. It was never encoded.

Think about what's happening in your head during an introduction. You're managing your own face, working out what to say about yourself, noticing the room, maybe rehearsing your own line. The name arrives in the one moment when your attention is pointed at yourself. It passes through your ears and out the other side.

Memory research has long distinguished between hearing something and processing it deeply enough to retain it. Shallow exposure leaves little trace. That's why "I'm terrible with names" is usually the wrong diagnosis. The problem is rarely storage capacity. It's that, in the critical two seconds, nothing was being stored.

The cost of this is not trivial, because of what a name signals. Being called by your name is one of the quieter ways people feel recognized. Getting it wrong, or visibly avoiding it, tells the other person they were a blur to you. In meetings, where status and belonging are already being negotiated, that small message lands harder than we'd like.

Why rehearsal works, and which kind

The common advice is to repeat the name back: "Nice to meet you, Dana." That's helpful, but mostly because it forces you to attend. Its memory benefit alone is thin, because repeating something immediately, while it's still sitting in your short-term buffer, is easy and teaches your brain very little.

A better-supported idea comes from the research on spaced and expanded retrieval. In a 1978 study, Landauer and Bjork tested people on learning first and last name pairs and compared different schedules for practicing recall. Retrieving the name after gradually widening gaps, a short wait, then a longer one, then longer still, produced better retention than either cramming it repeatedly in a row or waiting too long between attempts.

The key ingredient is effortful retrieval. Each time you pull the name out of memory without looking at it, you strengthen the path to it. The gap matters because the retrieval has to be a little bit hard. If it's trivially easy, nothing is built. If it's impossible, you've just practiced failing.

That's the whole mechanism, and it's usable in the middle of a normal workday.

Give the name a hook

Since the trouble with names is that they're bare, the other half of the solution is to attach something. This doesn't need to be a clever mnemonic. It just needs to be a connection.

The most reliable hooks are real ones. Dana mentions she just moved from Denver, so she's "Dana from Denver," and the alliteration helps too. Marcus is the one who asked about the vendor contract. Priya has the same surname as your college roommate. None of these are profound. They convert an arbitrary label into something with a second route to it, the way "baker" had meaning built in.

Asking one small question works well for this, because it makes you listen for a hook: "How do you spell that?" or "Is there a story behind that name?" or simply "What do you work on?" Each gives the name something to attach to.

When you've already blanked

Sometimes it's too late, and you're standing there with a face and a gap. A few honest moves beat the avoidance routine.

Say it plainly, early, and with warmth: "I'm so sorry, your name has slipped away from me. Remind me?" People overwhelmingly respond with relief, often because they've been in your seat. The sting of asking is brief. The sting of getting through an entire meeting by pointing and saying "hey you" is much longer.

The longer you wait, the more expensive the question becomes. A name forgotten at minute two costs a shrug. A name forgotten after six months of working together costs an awkward silence. So ask while it's cheap.

Your next moves

  • Make the name the one thing you do when someone introduces themselves. Look at them, stop planning your own line for two seconds, and say the name back in a full sentence: "Good to meet you, Dana." The goal is to force real attention, not to rehearse.
  • Attach one fact before the conversation ends. Find a single detail, a city, a project, a joke, an odd coincidence, and link it to the name in your head: "Dana, Denver, the migration."
  • Test yourself on a schedule. Right after the meeting, write the name from memory, with no looking. Do it again an hour later, and again the next morning. That's expanded retrieval in miniature, and it takes under a minute total.
  • Look at the invite or attendee list before you walk in. Read the names while picturing what you know about each person. You'll hear the names differently when they're said aloud.
  • Ask early, not late. If you blank, say "Sorry, remind me your name?" within the first few minutes, while the cost is still a single shrug.

Where this leaves us

If you're someone who finishes a meeting knowing the decisions but not who made them, it can be hard to see the pattern. That's the idea behind MeetingMortem: a place to look back on how your meetings actually went, who was in the room, what was said, and how it felt, so the details that slip away have somewhere to land. A name logged the same day, with a note about what made that person memorable, is the same retrieval-and-hook habit, just written down. If that sounds useful, you can take a look at https://meetingmortem.lumenlabs.works whenever you like.