Why I stopped forcing my team into Notion

Let me be fair to Notion up front, because this gets misread fast. Notion is a genuinely good tool. My team lived in it for years. If your job is people reading and writing pages, it’s excellent at that.

That’s exactly the problem. It’s excellent at people reading and writing pages. And the way I work now, most of the reading and writing isn’t done by people anymore.

The old way vs. the new way

Here’s the split that matters, and it’s not “which app has more features.”

The old way: humans are the ones doing the work in the tool. The tool’s job is to give people a nice interface — pretty pages, drag-and-drop, databases you click through. AI, if it’s there at all, is a sidebar you visit, ask a question, and copy the answer out of.

The new way: your AI does a large share of the work directly, and the tool’s job is to give the AI clean context to operate on. You direct; the AI reads, writes, and files. The interface matters less because you’re not clicking through it all day — you’re talking to an AI that is.

Notion is a best-in-class version of the old way. And no amount of AI features bolted onto the side changes what it is underneath: a page-builder designed for humans first.

Where it actually broke for us

The breaking point wasn’t a missing feature. It was watching my AI struggle to work with our own knowledge.

Everything valuable was locked inside Notion’s blocks — great for a human eye, awkward for an AI to read and write quickly. So the workflow became: ask AI in one window, copy the answer, paste it into Notion, reformat it, and hope the next person finds it. I was the integration layer. Every single time.

Multiply that by a team and it’s death by a thousand copy-pastes. The AI never had the full picture, so it never got better with our context. It just answered whatever I pasted in that moment and forgot it.

What I wanted instead

I didn’t want a prettier Notion. I wanted our knowledge to live as clean text that any AI could read and write instantly — so my team’s AI could work off the same brain we do, without me in the middle.

That’s a different category of tool, not a nicer version of the same one. Built for a team and their AI to operate off one shared context: files, tasks, and the decisions behind them, all in plain text, all reachable by whatever AI each person already uses.

The honest takeaway

If your team is mostly humans clicking through pages, stay in Notion — it’s great at that, and switching would be a downgrade.

But if you’ve noticed you’re increasingly the copy-paste layer between your AI and your team’s knowledge, that’s the signal. It’s not that your tool got worse. It’s that the way you work changed, and your tool is still built for the old one. That’s the trap worth naming — not “which page-builder wins,” but whether you’re still using a people-first tool in an AI-first workflow.