Why I Stopped Using Notion for Everything

I used Notion for everything for two years. Tasks, notes, project management, client tracking, writing drafts, bookmarks, meal planning — if it could go in a database, it went in Notion. Then I stopped. Not because Notion got worse, but because I realized I'd been building a cathedral when I needed a shed.

This is not a Notion hit piece. Notion is a genuinely good tool for specific things. The problem was me — and if you're reading this, there's a decent chance the problem is you too.

The Seduction of the All-in-One

The pitch is irresistible. One tool for everything. One workspace. One source of truth. You watch a YouTube video where someone shows their Notion setup — 47 linked databases, a custom dashboard with rollups and relations, color-coded status fields — and something in your brain goes "yes, that's what I need." You don't need a task manager and a notes app and a project tracker and a wiki. You need Notion. Notion is all of those things.

So you build it. You spend a weekend setting up your workspace. Then another weekend refining it. Then you discover templates and spend a third weekend importing someone else's system and customizing it. By the end of month one, you have an elaborate personal operating system that tracks everything. By the end of month two, you've stopped using most of it.

The seduction is real because the logic is sound — in theory. Fewer tools means less context-switching, less data scattered across apps, less monthly subscription overhead. What the theory misses is the maintenance cost. Every linked database, every rollup, every relation is a piece of infrastructure that needs to stay accurate. When your all-in-one system gets big enough, maintaining the system becomes a task that competes with the tasks the system is supposed to track.

What Actually Happened

Here's what my Notion looked like at peak usage. A task database with 800+ items, most of them stale. A client tracker that was current for the first three months and then slowly diverged from reality because updating it felt like work. A notes database where I dumped everything — meeting notes, article ideas, random thoughts — and never looked at any of it again because the search was slow and the organization was theoretical. A content calendar that I maintained religiously for six weeks and then abandoned when the friction of logging every piece of content exceeded the value of seeing it on a calendar.

The databases were beautiful. The dashboards looked professional. The system was coherent. And I was spending — I actually tracked this for a week — about 45 minutes a day on Notion maintenance. Not doing work in Notion. Maintaining Notion. Updating statuses, moving items between views, fixing broken relations, reorganizing things that had drifted.

Forty-five minutes a day is over five hours a week. That's a part-time job managing a tool that was supposed to save me time. And the thing that finally broke the spell was noticing that my actual work — the stuff that generated money and moved projects forward — was happening in a text file, my terminal, and a group chat. Notion was where I recorded what I'd done. The doing happened elsewhere.

The Architecture Trap

This is a pattern I see constantly with people who are — let's be honest — smart and slightly obsessive about systems. You don't just use a tool. You architect a system inside the tool. You design databases. You create taxonomies. You build dashboards that aggregate information across those taxonomies. And the architecture feels like work because it uses the same cognitive muscles as real work — planning, organizing, categorizing, structuring. But it's not work. It's infrastructure. And infrastructure is only valuable when someone builds on top of it.

The tell is simple: if you spend more time maintaining your system than doing the things your system tracks, the system is the problem, not the solution. I hit that point with Notion around month eight and didn't admit it until month eighteen. The sunk cost of all those databases — all that setup time, all that structural thinking — made it feel like quitting would waste the investment. It wouldn't. The investment was already wasted. I just hadn't processed the loss yet.

Notion specifically encourages this because it's so flexible. That flexibility is genuinely its strength for team wikis and lightweight project management. But for individuals, flexibility means there's no guardrail stopping you from building a system so complex that it collapses under its own weight. The tool doesn't tell you "this is too many databases." It just lets you keep building.

What I Replaced It With

This is the part that feels embarrassing to admit because it's so boring.

Tasks go in a plain text file. Specifically, a markdown file called tasks.md that lives on my desktop. It has three sections: Today, This Week, and Backlog. I add things by typing. I remove things by deleting the line. There are no statuses, no priority fields, no due dates, no automations. If something matters, it goes in Today. If it doesn't get done today, I either move it to tomorrow or I delete it because it wasn't that important. The entire system is visible on one screen without scrolling.

Notes go in Apple Notes. Not because Apple Notes is great — it's fine. It syncs, it's fast, it searches well enough, and it requires zero maintenance. I don't organize my notes into folders anymore. I just search. This feels chaotic if you're a systems person, and it turns out chaos with fast search is more useful than order with slow retrieval.

Client tracking happens in a spreadsheet. A Google Sheet with columns for name, status, last contact, and notes. No linked databases. No rollups. No automations. A spreadsheet. I update it after client calls and it takes about 30 seconds per update. The total weekly maintenance is under five minutes.

Project management for anything with more than one person still uses a proper tool — but it's Linear now, not Notion. Linear does one thing. It does it fast. There's no temptation to build a second brain inside it because it doesn't have the primitives for that. The constraint is the feature.

The total time I spend maintaining these tools is maybe 15 minutes a week. That's a five-hour weekly savings compared to peak Notion. And nothing fell through the cracks — or rather, the same things fell through the cracks because those things were falling through the cracks in Notion too. The system wasn't catching them. It was just documenting the failure in a prettier format.

The Notion-Shaped Hole

I want to be precise about what I'm saying and what I'm not saying. I'm not saying Notion is bad. I'm saying Notion-as-everything is a trap for a certain kind of person — the person who finds system-building intrinsically rewarding. If you're that person (I am that person), Notion is dangerous the way a woodshop is dangerous for someone who loves building furniture but needs to actually sit down and write. You'll build beautiful shelves instead of writing the thing.

Notion is good at being a team wiki. It's the best tool I've used for shared documentation where multiple people need to contribute and the information is relatively stable — product specs, process docs, company handbooks. It's good at that because the flexibility lets you structure information the way your team thinks, and the database features let you create views that surface what different roles need to see.

Notion is mediocre at being a personal task manager, a CRM, a content calendar, or a note-taking app. Not because it can't do those things — it can — but because it does each of them at about 60% the quality of a dedicated tool while requiring 200% the setup time. The 60% is fine if the consolidation benefit of having everything in one place outweighs the quality gap. For me, after two years, it didn't.

The Lesson (Not About Notion)

The deeper pattern here isn't about Notion specifically. It's about the difference between a tool and a project. When you set up a task manager, you're using a tool. When you spend three weekends building a custom task management system inside a flexible platform, you've started a project. Projects need maintenance. Projects drift. Projects become their own source of work.

The question I ask myself now before adopting any tool: will I use this, or will I build inside this? If the answer is "build inside," I need a very good reason — like it's my job and someone is paying me to build the system. If nobody is paying me, if the system is just for me, I want the dumbest, simplest tool that gets the job done. A text file. A spreadsheet. An app that does one thing.

I spent two years building a beautiful system in Notion. The system was impressive. The work I did with the system was the same work I'd have done with a text file. The only thing the system produced was the system itself. That's a hobby, not a tool. There's nothing wrong with hobbies — but I was calling it productivity and billing it to my work hours, and that's the part I had to stop.

If you're reading this at 2am while also having a Notion tab open with a database you're "refining," I see you. Close the Notion tab. Open a text file. Write down the three things you need to do tomorrow. Go to bed. The text file will still work in the morning. It will work without a template. It will work without a rollup. And you'll spend zero minutes maintaining it.

This article is part of The Weekly Drop at CustomClanker — one topic, one honest take, every week.

Related reading: The Tool Collector's Guide to Owning Nothing, Architecture Cosplay, The Hex Constraint — Free Download