Obsidian vs Ember: Managing Your Ideas or Thinking With Them

I’ve downloaded Obsidian more times than I’d like to admit.

Every time, I started with big hopes. I used the daily note. I watched the graph grow into a little galaxy of dots. I linked notes both ways. Near the end, I even had a Claude skill that searched my vault for related ideas.

And every time, the same thing happened. I’d drop a thought into the vault, close the app, and never go back. Somewhere along the way, I stopped thinking about my ideas and started thinking about where they should go.

A fellow deep thinker put it this way:

I’ve been using Obsidian for the past year and a half as my Zettelkasten system. It is the very definition of a system overtaking its purpose. There’s always new features and a new way to interact with your data that wasn’t there before, which causes you to have to go back and reshuffle your data a different way to match the system. I was so excited when I first started using it but it has become a constant source of frustration.

A system overtaking its purpose. Woah.

Nobody starts a vault hoping to spend Saturday moving notes around. They start because an idea moved them.

Libraries need librarians

Obsidian is a great tool. For people who love to tinker with systems, building the library is the joy. I get that.

But a library needs a librarian. Someone has to sort the shelves, fix the labels, and keep up with every new way of arranging things.

AI makes this interesting. Now you can point Claude at your vault and have it find connections, write notes for you, and clean things up. But that’s still managing. It’s the same librarian with a better assistant. The shelves are still there, still asking to be sorted.

I don’t want to manage my ideas. I want to think with them.

For me, it all comes down to sentences. A line from a poem. Something a friend said over coffee. A paragraph that made me stop reading and stare out the window. It’s so simple. And the minute I get into an app built for anything more, I fall into the trap of keeping up with features or building the perfect setup.

A fire you sit by

So here’s the picture I keep coming back to.

Obsidian is a library you build. Ember is a fire you sit by.

A fire needs a little tending. But you tend a fire in seconds, and you never reorganize it. You add a log and sit back down. The whole point is the sitting.

That’s why I built Ember the way I did. It’s two simple tools in one app: a commonplace book and a journal. Nothing else.

How the fire works

Gather kindling. You save sentences that moved you into your commonplace book. From poems, books, articles, conversations. No folders. No tags to keep up with.

Let it come back. Ember hands you one of those saved ideas as your daily spark, and brings others back during your thinking sessions. You don’t have to go looking. Ideas come back to you without effort, and sometimes in ways that surprise you.

Answer it. This is the journal. When you start a thinking session, you start with something you saved. Then you write and write and respond. The journal looks like a chat thread on purpose, because it is a conversation. With yourself, and with the people whose words you saved. A blank page feels like a test. A thread feels like someone already spoke and now it’s your turn.

I’m a talk it out kind of guy, so I use voice transcription a lot. I just let my mind wander around the idea and see where it goes.

Keep it going. When the fire starts to die down, you stoke it. There are three ways to do that.

Stoke with Spark. Ember hands you related ideas from your commonplace book. Other voices join the conversation.

Stoke with Question. Ember asks you a question that turns your thinking upside down. It can show you things you didn’t know were there.

Stoke with Session. Ember brings back one of your past thinking sessions. This is where patterns start to show up. The thing you wrestled with in March might be the same thing showing up today under a different name.

So one thinking session can hold three conversations at once: with others, with the questions you haven’t asked yet, and with who you used to be.

Notice what’s missing from all of that. There’s no step where you sort, file, tag, or tidy. All of the work is thinking. None of it is keeping up.

Why do you save ideas?

This isn’t a knock on Obsidian or the people who love it. If building the library is what lights you up, build away.

The real question is why you save ideas in the first place.

If you save them so you can find them later, you probably want a library.

If you save them because you want to think with them, sit with them, and let them change you, you want a fire.

I built Ember for the second kind of person. Because I’m that kind of person.

So pull up a chair. Add a log. See what catches.

Try Ember

Thanks for reading The Idea Shepherd! Subscribe for free to receive new posts and support my work.