The group conversation problem: why everyone at the roundtable gets the same follow-up

Article · 5 min read

Why everyone at the roundtable gets the same follow-up email

Follow-up advice assumes a private conversation. Most networking happens at tables of six, where shared context erases the individual detail an email needs.

Five emails, one dinner

The dinner ran three hours. Six of you at a corner table: a founder who knew the host, two people from the same bank, a product lead who'd flown in that morning, and someone whose company you never quite caught. The conversation was good. Somebody had a sharp take on the keynote, the table argued about it through the main course, and a story about a failed integration got the biggest laugh of the night.

Monday morning you sit down to follow up. Every draft opens the same way: great to meet you at dinner, loved the conversation about the keynote.

Five emails. Same opening line, same callback, a different name after "Hi." Each recipient gets the message the other four got, and on some level they know it, because they were sitting right there too.

The roundtable blur: shared context crowds out the person

Group conversations hand you a lot of memory, and almost all of it is shared. You remember the topic, the argument, the punchline. What slips away is the one thing a follow-up actually needs: what made this particular person distinct from everyone else at the table.

Call it the roundtable blur. In a one-on-one, everything you remember belongs to the other person by default, since there's nobody else it could belong to. In a group, the memorable material belongs to the table. The individual signal (the specific problem the product lead mentioned, the hire the founder is trying to make) was said once, quietly, between bigger moments. And it gets folded into a single memory called "that dinner."

So the follow-up inherits the blur. The problem surfaces at the keyboard, days later, when there's nothing personal left to write.

Why follow-up advice assumes a conversation for two

Almost every follow-up guide gives the same instructions. Reference something specific from your conversation. Mention a detail only the two of you would know. Personalize the subject line.

Good advice, written for a bilateral meeting. It quietly assumes there was a "your conversation" in the first place: a private exchange with its own details. At a roundtable, the specific thing you remember is the specific thing everyone remembers. Follow the advice faithfully and you get exactly the five-identical-emails problem, because the most specific detail you have is the shared one.

Templates make it worse. A better template formats the same missing information more neatly. If the input is "we talked about the keynote," no structure on earth turns that into an email that sounds written for one person.

Timing is its own problem, covered in our piece on the 72-hour memory cliff. This one is structural, and sending faster won't fix it.

What memory research says about group conversations

Memory researchers have names for both halves of this. Malcolm Brenner's 1973 work on the "next-in-line effect" found that people taking turns in a group recall poorly what was said just before their own turn, because attention shifts to rehearsing what they're about to say. Anyone who has waited for an opening in a fast table conversation knows the feeling.

The second half is attribution. The source-monitoring framework (Johnson, Hashtroudi and Lindsay, 1993) describes how memories don't carry a tidy "who said it" label. We reconstruct the source later from whatever details survive, and when the details are thin, the attribution drifts. At a table of six, you'll remember that someone is hiring a head of partnerships long after you've forgotten which someone.

The same gap shows up in what people ask online. Met's own scan of r/sales, r/PhD, YouTube, LinkedIn and Google's People Also Ask boxes found the recurring stuck point is what to write once the specifics have faded. Group encounters are the worst case of that question. The advice ecosystem barely treats them as a separate problem.

How do you follow up after meeting multiple people at a conference?

Go back to the dinner. The fix happens as you leave the table, before the next conversation starts: in the coat-check line, the elevator, the walk to the car. One line per person. Something like "product lead: moving off their current KYC vendor in Q1, skeptical of building in-house."

Run each line through one check, the differentiator test. Would this line be true of anyone else at the table? If yes, it's shared context. Keep looking. "Great conversation about the keynote" fails. "Thinks the keynote undersold compliance cost, and they'd know, they run compliance" passes.

Why 90 seconds? It's a working rule, not a lab number. Short enough that you'll actually do it before someone new says hello, and early enough that the next conversation hasn't written over the last one.

The next morning, each email opens on its own line. The shared moment drops to a single clause of callback, if it appears at all. The two people from the bank get separate notes that each reference what that person said, because colleagues compare emails.

What you remember from the dinnerShared or individualWhere it goes in the follow-up
The table's argument about the keynoteSharedOne-clause callback at most
The failed-integration story that got the laughSharedSkip it, unless you're writing to the person who told it
Product lead is moving off their KYC vendor in Q1IndividualOpening line of their email
Founder is hiring a head of partnershipsIndividualOpening line, plus an intro if you have one
The two bankers work on the same teamIndividual, but they'll compareSeparate emails, each built on what that person said
The differentiator test applied to one roundtable dinner (illustrative scenario).

If a line would be true of anyone else at the table, it's shared context. Keep looking.

What changes once you accept the blur

The hard part of following up a group moves out of the inbox and into the room. Capture timing beats writing skill. A brilliant writer holding "we talked about the keynote" loses to a mediocre one holding "moving off their KYC vendor in Q1."

It also changes what a good conference night looks like. Two roundtables where you captured a line for every person will outperform five where you collected cards and kept nothing. And anyone sharing an employer with someone else at the table should be treated as a reader who will see the other email. Identical notes to colleagues read as a mail merge, which is exactly what they are.

One-on-one advice still works for one-on-ones. Most of the room, though, is groups.

Capturing the person before the table blurs

Met's Event Mode was built for exactly this stretch of the night. It keeps capture open while you're still in the room, so scanning a card in the hallway takes seconds and leaves space for the one line that matters: what this person said that nobody else did. The note stays attached to the contact, and when you sit down to write the follow-up, it's right there in front of you.

Contacts live in your own iCloud. No ads, no nudges while you're mid-conversation. Ninety seconds in a coat-check line is the whole habit. Met makes sure the line lands somewhere you'll find it on Monday.

Capture one line per person before the table blurs. Get Met.

Met is built for people who meet a lot of people in a short window: conference dinners, roundtables, booth clusters. Event Mode keeps capture open while you're still in the room, so each contact gets their own line of context before the group conversation blurs into one memory. Storage is iCloud-only, with no ads and no interruptions.

Get Met in your inbox

Field notes on conference networking, follow-up timing, and what we ship next. No spam, no AI hype.

No spam. Unsubscribe anytime. Replies go to support@sailquery.com.