One contact, five apps, no common key: why conference notes go unused

Day two, 11pm, and one person in five places

Picture the hotel desk at 11pm on day two. Somewhere in your phone is everything you need to follow up with the operations lead you met by the coffee station that afternoon. You know it's in there. You put it there yourself.

There's a voice memo, recorded on the walk back to the elevator: their name, their company, something about a vendor contract that renews in the spring. There's a photo of their business card in your camera roll, wedged between a keynote slide and a shot of the lunch line. There's a new contact in your phone with a first name, a mobile number and every other field blank. There's a LinkedIn connection request, sent without a message. And there's a badge scan sitting in the conference app with no annotation at all.

Five records. One person.

None of them knows the others exist.

The no-common-key problem

Call it the no-common-key problem. Each of those five records is accurate, and each app did exactly what it was built to do. The recorder recorded. The camera saved a photo. The contacts app stored a number. What's missing is the thing that would let you join them: a shared field, a link, anything that says these five fragments belong to the same human.

So reassembly falls to you. One person means five apps, a search inside each one, and a judgment call about which unlabeled voice memo goes with which half-filled contact. Do that for fifteen people after a day on your feet and the math stops working. The effort to unify the pile is higher than the energy you have left, so the follow-up waits until tomorrow, then until you're home, then until it's awkward.

This is a different failure from forgetting. The context survived the day intact. It just can't be reached at the moment the follow-up gets written.

Why 'take better notes' makes it worse

Most post-conference advice works on content or timing. Write down the one detail they'll remember you by. Do it within the hour. Assume the specifics fade fast. That advice is sound, and Met has published its share of it, including [the 72-hour memory cliff](/articles/72-hour-memory-cliff/). But every version of it assumes the problem is an empty notebook.

For a lot of people working a conference floor, the notebook is full. It's spread across five covers.

Tell that person to take more notes and they'll produce a sixth fragment. The habits that look like diligence (a quick memo here, a card photo there, a LinkedIn add before the conversation ends) are the habits that build the pile. Each one was the fastest option in the moment, and speed in the moment is the right instinct. The cost lands later, at assembly, and no conference schedule leaves time for assembly.

Tell someone with five fragments to take more notes and they'll produce a sixth.

How do you keep track of people you meet at a conference?

That's the question people actually type, along with how to organize notes from a conference. The phrasing is telling: the searcher already has notes and wants to know what to do with them.

The standard answer is to pick one system and route everything into it: a spreadsheet, a CRM, a notes template. The destination is right. The cost estimate is off. Opening a spreadsheet at a coffee station, mid-conversation, is slower than any of the five fragment apps, which is exactly why people reach for the camera instead.

Look at the tools by category and the pattern holds. Card scanners own the card. Note apps own the note. Event apps own the badge scan. Professional networks own the profile. Each category solves its own fragment well and treats the person as somebody else's problem.

What reassembly looks like for one contact

Back at the desk. You open Contacts and find the first name. No surname, no company, so you can't be sure it's the right person. You open the camera roll and scroll back through the afternoon until the card shows up, and now you have a surname and a title. You open the recorder and play untitled memos until you hear the contract detail, which is the only reason your email will read like you were paying attention. You check LinkedIn to confirm the spelling. You glance at the conference app to see if the scan added anything.

It didn't.

Then you write the email. That's one person, several minutes if nothing goes wrong. By the fourth or fifth contact the shortcuts start: you skip the memo because finding it is a chore, and the follow-up comes out generic. The fragment that made it personal was the hardest one to reach, and it's the first one you drop.

Attach the key at capture time

If the missing key is the problem, the fix sits in the few seconds after a handshake. That's the only point where you know for certain which fragment belongs to which person. Anything captured then with a link to the person stays reachable. Anything captured without one joins the pile.

A practical rule: a note doesn't count unless it's attached to a person record at the moment you take it. Card, context, where you met, what they said they needed. Same record.

And an audit worth running at your next event: before you leave the venue on day one, count how many places hold information about the people you met. One or two, and you'll follow up. Five, and you're betting every follow-up on a late night you won't have.

Where Met fits

Met is built around that one-record rule. Event Mode keeps the room captured while you keep talking, so the card scan, the note about the spring contract renewal and the event where it happened land on the same contact. Event Mode automatically attaches the event to each contact you capture: the event's name is filled in as where you met and the contact is linked to that event, so it lands under the event without extra typing. It doesn't add a context note at capture time. You can add notes and a tone afterward from the event outbrief or the event detail screen. When you sit down at 11pm, there's nothing to assemble. The follow-up draft starts from that record, with the detail that makes it personal already in it.

Contacts stay in your iCloud, not on someone else's server. No ads in the flow, no nags while you work the room.

The people you met this week are still recoverable. The pile is what stands between you and them, and the pile is easiest to prevent at the source.