The People You Forgot You Know
Your contacts app stores names, not relationships. That's a design choice with consequences that compound over years.
The average smartphone contains somewhere between 300 and 600 contacts. Robin Dunbar, the British anthropologist who spent the 1990s studying primate cognition and ended up with a number named after him, estimates the human brain can actively maintain about 150 meaningful relationships at once. Which means somewhere between half and two-thirds of the people in your phone are ghosts: names you recognize, faces you might remember, contexts that have completely evaporated.
This isn't memory failure. It's a design failure with a long tail.
What a contacts app actually stores
When you add someone to your contacts, you capture their identity: name, email, phone number, maybe a company. What you don't capture is the relationship — how you met, what the connection was for, what you talked about last, why you added them in the first place. That context lived in your head at the moment of adding, and you assumed it would stay there.
It doesn't. It decays. Slowly at first, then faster, until all that's left is a name and a number pointing at a person you might not recognize on the street.
The contacts app is designed as if relationships were stable objects: things to be filed, not maintained. You add someone once. You don't add context. You don't update depth or recency. You never mark a connection as dormant. The entry just sits there, indistinguishable from the person you talk to every week, until one day your phone suggests calling someone and you genuinely cannot remember who they are.
The dormant tie problem
In 2011, Daniel Levin and colleagues published a study in Organization Science on what they called "dormant ties" — professional relationships that had gone quiet. Their finding was counterintuitive: reconnecting dormant ties was surprisingly valuable, often combining the novelty you'd get from a new contact with the trust you'd built years before. The value hadn't decayed as fast as people thought.
But here's what they also found: reactivating a dormant tie requires context. Not just a name and an email address. You need to remember the history — what you worked on together, what they were curious about, what they were doing when the relationship went quiet. Without that, the reconnection starts too far back. You spend the first conversation rebuilding a foundation you already built once, and both of you know it.
Most contacts apps store none of this. They store the identity. They drop the relationship.
The noise problem
There's a second issue, less discussed but equally structural. When everything is stored equally, nothing is weighted. An AI searching your contacts for "someone who works in climate tech" will find the person you met at a conference in 2018 and never talked to again, right alongside the collaborator you've worked with for three years. Both appear as contacts. Neither carries a signal about depth, recency, or how the connection actually worked.
This is the ghost problem at scale. Not that your contacts are wrong — it's that they're undifferentiated. A flat list of 600 people with no relationship metadata is less useful than a smaller, carefully maintained list with actual context attached. You'd be better off with 100 contacts you understand than 600 you don't.
The people who've solved this maintain personal CRMs: separate tools where they log interaction history, take notes after calls, track relationship health over time. It's a manual discipline, and it mostly appeals to salespeople and very deliberate networkers. But the underlying problem isn't professional. Anybody who depends on a network of people — for work, for advice, for introductions — has the same ghost problem. Most of them have just accepted it as normal.
What a person record could look like
The honest version of a contacts app would store more than identity. It would store context: how you met, what the relationship has been for, what you talked about last time. It would track recency without you manually logging it. It would surface dormant connections before they decay completely, not after.
Some of that requires a shift in how we think about what a "contact" even is. Not a card in a rolodex. Not an entry in a database. Something closer to a working document: a person record that accumulates context over time, links to the tasks and projects that run through the relationship, and is rich enough to actually jog memory rather than just confirm a name.
I've thought about this for a long time, partly because I've felt it. Reaching for a contact I added years ago and realizing the entry tells me nothing useful — not why I added them, not what we were supposed to talk about, not whether the connection even still makes sense. The name is there. The relationship is gone.
A contacts app is supposed to help you remember people. Most of the time, it just stores them.
Asgeir Albretsen is the founder of Harbor.