← Back to Writing
Building Reflection

Your Brain Is Not a Filing Cabinet

· 5 min read

I’ve tried every knowledge management system. Notion databases with perfectly tagged entries. Obsidian vaults with bidirectional links. Apple Notes, Google Keep, physical notebooks. Each time, the setup feels like progress. And each time, the system quietly dies within a few weeks.

The pattern is always the same: I spend more time deciding where to put a thought than actually developing it.

The filing cabinet assumption

Most productivity tools are built on the same premise — that your brain works like a filing cabinet. Thoughts arrive pre-labeled. You just need the right folder structure. If you can’t find something later, it’s because you filed it wrong.

This has never matched how I actually think. Ideas show up half-formed and context-dependent. A conversation triggers a connection to something I read three months ago. A walk surfaces an approach to a problem I wasn’t consciously working on. These thoughts don’t arrive with tags attached.

Forcing them into categories at the moment of capture kills them. The friction of deciding “is this a project idea or a reflection or a research note” is enough to make me close the app and move on. The thought evaporates.

Capture first, organize later

I’ve been thinking about what a tool would look like if it started from a different assumption: that the value is in capturing the thought at all, and that organization is something you do later — if ever.

Not inbox-zero for your brain. More like a living collection that you can search, revisit, and let accumulate. Something closer to how a writer keeps a notebook than how an accountant keeps a ledger.

The interesting part isn’t the capture mechanism — any text box can do that. The interesting part is what happens after. How do you surface relevant thoughts without requiring manual curation? How do you find connections you didn’t explicitly create? How do you make a growing collection more useful over time instead of more overwhelming?

What I’m building

This is the idea behind Thought Manager. It’s a capture-first thinking tool — designed to remove the friction of getting thoughts out of your head and into a system that doesn’t punish you for being disorganized.

I’m still early. The core capture flow works, but the retrieval and connection layer is where the real challenge lives. I’m experimenting with different approaches to surfacing related thoughts — some algorithmic, some spatial, some time-based.

What I know so far: the tool has to be fast enough that reaching for it is easier than not. And it has to be forgiving enough that you never feel like you’re using it wrong.

The meta-problem

There’s an irony in building a thinking tool: you have to think clearly about how thinking works, which is exactly the kind of problem the tool is supposed to help with. I’ve caught myself wanting to capture notes about Thought Manager inside Thought Manager, which either means I’m onto something or I’ve lost the plot entirely.

I’ll share more as it takes shape. For now, I’m focused on the part that matters most — making it effortless to capture a thought before it disappears.