A personal operating system in Notion
Notion is where most of these get built, and for good reasons. It is worth being precise about what it does better than a folder of files, and about the two things it structurally cannot do, because one of them is why people leave.
What Notion genuinely does better
Relations. In Notion a project can point at a person, a person at a meeting, a meeting at a decision, and every one of those links is live and queryable in both directions. Building that in plain markdown means maintaining links by hand or accepting that the graph is approximate. If your system's value comes from cross-referencing, Notion earns its place and it is not close.
Views, too. The same underlying database as a board, a calendar, a table and a filtered list costs nothing extra, and for anyone who thinks visually that is a real ongoing benefit rather than a setup novelty.
The two structural limits
| Limit | What it means in practice |
|---|---|
| You do not hold the files | Your system is rows in someone else's database, reachable through their app and their API. Export exists and produces something meaningfully less useful than what you had. |
| Nothing fills it for you | Every row is a row you created. Notion's own AI helps you write inside a page; it is not an assistant reading your mail and filing to the right project without being asked. |
The first limit is a bet on the company, and reasonable people take it. The second is the one that decides whether the system survives, because it means the upkeep is yours, forever, and that is the same trap every other hand-maintained system sets. A beautifully related Notion workspace goes stale on exactly the same timetable as a folder of markdown files does, for exactly the same reason.
If you have built one of these before and abandoned it, it is worth being precise about why. It is almost never that the structure was wrong. It is that a fortnight went by, the rows stopped matching reality, and the dashboard started lying quietly.
When to stay
Stay in Notion if relations are the point, if you share parts of the system with other people, or if you know from experience that you do keep things updated. Those are real, and swapping tools will not improve any of them. A tidier comparison of Notion against the file-first world is at Notion versus Obsidian.
When to leave
Leave when either limit starts costing you. If the thought of your decade of records living in a product you do not control has started to bother you, that is the ownership argument, worked through at who owns your notes. If you are tired of being the thing that keeps the workspace true, that is the maintenance argument, and the difference a file-reading assistant makes is at Notion AI versus Claude Code.
Worth saying plainly: leaving is not free. You give up live relations and you rebuild views as queries. What you get is a record that outlives any company and a system somebody else keeps current. The structure that survives the move is at the template.
The version nobody has to maintain
The book builds the whole system in plain files you own, with the filing handed to an assistant. Every prompt is printed, and there is no code to write.
Get the bookSee what self-filing looks like
Projects and people kept current from real email and meetings, with nobody creating the rows. Try the demo.
See the demo