I’m bad with names. So I built a system.

I am very bad with names.

Not “sometimes I forget.”

Very bad.

I can remember the shape of a conversation.

I can remember what someone cared about.

I can remember the product they were building, the school they worked at, the problem they were trying to solve, or the strange detail that made the meeting interesting.

But the name itself?

Gone.

Sometimes immediately.

This is embarrassing.

A small version of this has happened more than once.

I will remember the school.

I will remember the project.

I will remember the exact concern someone raised in our last conversation.

I will remember the weird operational detail that made the meeting important.

And then, right before I need to speak, the name disappears.

That is the funny version.

The more expensive version is when I forget the promise attached to the person.

The thing I said I would send.

The intro I said I would make.

The follow-up that would have made the next conversation feel thoughtful instead of restarted.

It is also useful.

Because it forced me to admit something I probably should have admitted earlier:

And if I am building companies, teaching, selling, writing, going to church, meeting people in Hong Kong, talking to people in Korea, and trying not to become completely owned by the work, that is a problem.

Not because forgetting a name is the end of the world.

Because names are only the visible failure.

The deeper failure is context.

Who introduced us?

What did we talk about last time?

What did I promise to send?

What were they worried about?

What did I learn about their company?

What did I learn about their family?

What was the one detail that would make the next conversation feel like I actually listened?

That is not just memory.

That is relationship infrastructure.

And for a long time, too much of it lived only in my head.

Which means it did not really live anywhere reliable.

That is cognitive busy.

Not the dramatic kind.

The quiet kind.

The kind where your brain becomes the only search engine for your own life.

A person asks about something.

A prospect follows up.

A student says something that connects to another idea.

A church friend mentions a detail I should remember.

A founder I met three months ago reappears in my inbox.

And suddenly my brain starts doing archaeology.

Where did I meet this person?

What did we discuss?

What did they care about?

Did I promise something?

Did I write it down somewhere?

Was it in Notion?

A WhatsApp message?

A calendar note?

A random transcript?

My head?

This is the part of work that does not look like work.

No one sees it on a calendar.

But it costs attention.

It creates guilt.

It slows down replies.

It makes relationships more fragile than they need to be.

So I built a system.

Not a perfect one.

Not a beautiful productivity-influencer system.

A practical one.

Most of it lives in Notion.

The goal is simple:

For people, I want a note that answers:

For projects, I want a note that answers:

For decisions, I want a record of:

For follow-ups, I want the system to tell me:

That last question matters more than it sounds.

A lot of cognitive busy is just future embarrassment trying to warn you early.

You know something will come back later.

You know forgetting it will cost trust.

You know the open loop is still alive.

So the brain keeps holding it.

That is useful for about five minutes.

Then it becomes noise.

The system is my attempt to move that noise somewhere safer.

This is where Notion AI actually helps me.

Not because I want AI to be my personality.

Not because I want it to replace judgment.

But because I want it to hold and retrieve context.

Before a meeting, I want to ask:

Before writing a proposal, I want to ask:

Before replying to someone, I want to ask:

Before making a decision, I want to ask:

That is not AI doing my thinking.

That is AI helping me stop wasting my best thinking on retrieval.

There is a difference.

Thinking is deciding what matters.

Retrieval is digging through the mess to find the thing you already knew.

I want to spend more time on the first one.

Less time on the second.

This is why I do not think a personal knowledge base is just a productivity hobby.

For me, it is closer to a care system.

If someone told me something important and I forget it because I was moving too fast, that is not just inefficient.

It is relationally expensive.

If a founder tells me what they are struggling with and I ask the same shallow question next time, the conversation resets.

If a client explains the real constraint and I lose it in my notes, the next proposal gets worse.

If a student says something that reveals how they think and I do not capture it, my teaching gets less precise.

If a friend shares something small but meaningful and I forget it every time, I become less present than I want to be.

So yes, I am building a system because I am bad with names.

But the system is not really about names.

It is about lowering the chance that my lack of memory becomes someone else’s experience of being unseen.

That is the human layer.

There is also an operating layer.

If everything important only exists in my head, I did not build a system.

I built a bottleneck with better intentions.

That is not Not Busy.

That is just being busy in a more invisible way.

The work can look organized from the outside.

The calendar can look clean.

The task list can look manageable.

But if every relationship, decision, and context thread still has to be reconstructed manually by me, I am cognitively busy.

The company is still renting my memory by the hour.

The goal is not to remember everything.

The goal is to build a system that makes remembering less heroic.

Capture should be easy.

Retrieval should be fast.

Review should happen before the moment I need the context.

The system should make it easier to be thoughtful.

Not more performative.

This still breaks.

Sometimes I do not capture the note.

Sometimes I capture too much and never review it.

Sometimes the record exists, but I forget to look before the meeting.

Sometimes the AI summary is too generic.

Sometimes I realize the real context was emotional, not factual.

A note can remember what someone said.

It cannot automatically know what mattered.

That is still my job.

But the system catches more than my brain did alone.

And that is enough progress for now.

Being Not Busy is not just having fewer tasks.

It is not forcing my brain to be the only place where everything lives.

It is making the important things retrievable.

People.

Projects.

Promises.

Decisions.

Context.

Because the work can grow.

The relationships can grow.

The number of open loops can grow.

But my head cannot be the only place everything has to survive.

That is the point of the system.

Not to make me look organized.

To make me less fragile.

And maybe a little more present.

— Chris, still trying