
Every note tool looks like a text box with a sidebar. Underneath, they make different bets about how knowledge gets organised: by day, by association, or by structure the user designs. Choosing the wrong bet is why people abandon a tool after a month.
Three tools make the bets concrete: Reflect, Mem, and Tana.
The short answer
Reflect if you review your days; Mem if you never file anything; Tana if you will design a system. All three are good at their bet and frustrating at the others.
The three bets
| Tool | Organising principle | Best user |
|---|---|---|
| Reflect | The daily note | People with a review habit |
| Mem | Automatic association | People who capture quickly |
| Tana | User-defined structure | People who build systems |
The third column matters more than the first. A tool that matches your existing habit needs no process change; a mismatch requires one you probably will not make.
Reflect: the day as the container
Reflect starts from dated entries with backlinks. Everything lives on a calendar, which is a strong opinion: if it did not happen on a day, where is it. That suits people who journal, review, and plan in days. It is the wrong shape for a reference base.
Mem: capture without filing
Mem removes the filing decision and surfaces related notes as you write. The advantage is friction: there is nothing to decide, so capture happens. The risk is that automatic association is not your association — retrieval can feel like someone else's filing system.
Tana: the system you design
Tana makes you define node types and structure, and then keeps them consistent. It rewards a day of design with a workspace that behaves like a tool; it punishes ad-hoc capture with a system that fights you.
The migration question
Notes are the most personal data most people have, and migration is lossy: links break, formatting shifts, tags are re-interpreted. That makes the choice sticky, which argues for trying the bet before importing a thousand notes.
A practical test
Spend a week taking notes in the tool's native shape without importing anything. If by Friday you are still writing, the bet fits. If you are avoiding the tool, it does not — and no migration will fix that.
Frequently asked questions
Do these integrate with agents? Some do; the general pattern is a files export or an API. See MCP servers for knowledge-base servers.
Can I use more than one? Capture in one and keep a reference base in another, but do not split the same work across two tools.
Which is best for teams? None of these three. See docs as retrieval corpus.




