Notion Is Not a Note-Taking App

You don't ask "where do I put this page?" anymore. You ask "what kind of thing is this?"

That question is the whole shift, and once it clicks, folders stop making sense.

#The folder habit dies hard

Most teams bring a filing-cabinet instinct into Notion and build folders anyway, a Marketing folder, an Engineering folder, a folder per client. It works, for a while. Then someone asks a question that crosses folders, "show me every decision that touched Compliance this quarter", and there's no way to answer it. The information exists. It's just scattered across containers that were never designed to talk to each other.

A folder can hold a document. It can't hold a relationship.

#The database mental model

A meeting is a meeting whether it's about Marketing or Engineering, so it doesn't live in a department folder. It lives in one Meetings database, and "Marketing" or "Engineering" becomes a property on it, not a location. Same for SOPs, projects, clients, systems: one database per kind of thing, with properties that describe it and relations that connect it to everything else.

Now every meeting is automatically connected to the client, the project, and the decisions made. You don't copy information around. You relate it.

That one distinction, property vs. location, is the entire migration.

#What it looks like in practice

Every meeting, one database. Title, date, and then the properties that matter: Client and Project as relations (live links to other databases, not typed-in text), plus Decisions, Action Items, Transcript. Change the client's name once, and it updates everywhere it's referenced, no hunting down five stale copies.

Every SOP, one database. Owner, Department, Status, Last Reviewed, and a Related Systems relation. This is what makes "show me every SOP nobody's reviewed in six months" an answerable question. A folder of Word docs can't do that, there's nothing to query.

#The part that actually matters

A page can appear in many places without being duplicated. One project can show up on the Engineering page, the Operations dashboard, and a client's page, same underlying record, three different views. That's why people end up calling Notion an operating system instead of a note-taking app: the pages aren't the point. The relationships are.

Which is also why the real payoff isn't writing better documents. It's that the whole thing becomes a semantic layer you can query, every decision that touched a given system, every meeting that led to a given architecture. Those answers exist only because the underlying objects, people, clients, projects, systems, decisions, are connected. Not because someone happened to write a great summary.

#The test

Next time you're about to create a folder, ask instead: is this a kind of thing that already recurs, a meeting, a project, a system, a decision? If so, it belongs in a database with properties, not a folder with a name. The folder question is "where does this go." The database question is "what is this, and what does it connect to." Only one of those scales.