Why I Ditched Popular Project Managers for a Simple Text File

The App That Was Supposed to Save Me

It started, like most productivity spirals, with good intentions. I had just taken on three simultaneous client projects, a personal writing goal, and some half-finished home renovation plans that had been sitting in my head rent-free for months. I needed a system. So I did what everyone does: I went looking for the right tool.

I tried Notion first. Built out a beautiful dashboard with linked databases, kanban boards, and color-coded priority tags. Spent about four hours setting it up. Used it actively for maybe nine days before the maintenance overhead quietly killed my momentum. Then came Asana, which felt more “professional” until I realized I was spending more time triaging notifications than actually working.ClickUp promised to replace everything. It nearly replaced my will to live. Every app had a learning curve that turned into a lifestyle, and somewhere in the middle of customizing my third “productivity workspace,” I lost track of the actual work I was supposed to be doing.

This is not a rare experience. It has a name in productivity circles: tool addiction. The feeling that the right system is always one more feature away.

What a Text File Actually Is

I want to be precise here, because “text file” means different things to different people. I’m not talking about a chaotic brain dump. I’m not describing a graveyard of half-formed ideas. What I settled on was a single plain text file opened in a basic editor, no plugins, no cloud sync required structured only by logic and line breaks.

The format evolved organically. At the top, a short block of what’s active today. Below that, a running list of everything pending, grouped loosely by project. At the bottom, a kind of archive section where completed items slide down when I’m done with them. No color coding. No due date fields. No integrations. Just text, arranged by priority, maintained by me.

The file is called work.txt. It lives on my desktop. I open it in the morning and close it at night.

What surprised me wasn’t that it worked. It was how much faster everything became.

The Hidden Tax of Feature-Rich Tools

There’s a version of this argument that sounds like Luddism some guy yelling at clouds about technology. That’s not what I’m after. The problem with modern project management software isn’t that it’s powerful. The problem is that power has a cost, and that cost is almost never disclosed upfront.

Every time you open Notion, there’s a small but real cognitive decision tree: which view am I in, what database does this belong to, should I add a property for this, did I tag this correctly? These micro-decisions accumulate. Researchers who study cognitive load describe this as “decision fatigue by interface” the idea that every structural choice an app forces on you is a small tax on your working memory. Individually, each tax is negligible. Collectively, they reshape how you experience your own work.

A plain text file has none of that overhead. You open it, you read it, you edit it. The interaction is so frictionless that the tool disappears entirely. You stop thinking about the system and start thinking about the work. That shift is worth more than any Gantt chart.

What You Actually Lose And Whether It Matters

Let me be honest about the tradeoffs, because pretending there aren’t any would make this essay useless.

You lose collaboration features. If you’re managing a team, a text file doesn’t scale gracefully. You lose automated reminders. If you need a system that actively pokes you, a text file won’t do that. You lose visual dashboards, progress metrics, integration with your calendar, and the ability to share a beautifully designed project brief with a client.

Some of those losses are real. If your job requires synchronized team task management, something like Linear or Basecamp makes legitimate sense. I’m not arguing that everyone should abandon software. I’m saying that a significant portion of people using complex project managers are solo workers, freelancers, or small teams who adopted the complexity because it felt more “serious” not because it solved an actual problem they had.

There’s a psychological dimension here that doesn’t get discussed enough. Complex tools signal effort. A beautifully organized Notion workspace looks productive. A text file looks like you’re not trying. And so people build elaborate systems partly for the systems themselves, as a performance of organization rather than its practice.

The text file doesn’t let you perform. It just makes you work.

The Surprising Durability of Plain Text

One thing I didn’t anticipate when making this switch: plain text is essentially indestructible.

Notion has had outages. Asana has had outages. My text file has never been unavailable because it requires no server, no account, no subscription, and no internet connection. It will open on any computer made in the last forty years. When I export it, it’s already in the most universally readable format that exists. There’s no vendor lock-in, no pricing tier that suddenly changes, no “we’re sunsetting this feature” email arriving on a Tuesday morning.

Software companies are businesses. Their incentives are not always aligned with your stability as a user. The apps that promised to organize your life are also the apps that need you to keep paying for them, which means they keep adding features to justify the price, which means the interface keeps growing, which means the cognitive tax keeps rising.

Plain text opted out of that entire dynamic a long time ago.

How I Actually Use It Day to Day

The morning ritual matters. I open work.txt before I open email, before I open Slack, before I open anything that might redirect my attention. The first ten minutes of my day are spent reading the file and deciding manually, consciously what gets done today. That act of manual prioritization is not a bug. It’s the feature.

I write tasks as complete sentences when they need context: “Finish the second draft of the Henderson proposal, specifically the pricing section.” Short tasks get short lines. Nothing is ever “urgent” in the system because urgency lives in my head, not in a tag.

When something is done, I delete it or move it to the bottom archive. The satisfaction of that deletion genuinely, physically removing a line from existence turned out to be a better psychological reward than checking a box in any app I’ve ever used. There’s something about the permanence of deletion that makes completion feel real.

The Deeper Question This Raises

Here’s what the text file experiment actually taught me, and it has nothing to do with productivity apps.

It taught me that I had been outsourcing my judgment. Every time I let a tool decide how to structure my work what counts as a project, what counts as a subtask, how to categorize and prioritize and visualize I was handing a small piece of cognitive ownership to software. Over time, I stopped trusting my own sense of what mattered because I had systems telling me what to look at.

Working from a plain text file forced me to develop and maintain my own organizational logic. I had to decide what mattered. I had to build the structure myself, which meant I understood it completely, which meant I could change it instantly when my work changed. No migration, no restructuring a database, no watching a tutorial.

There’s real value in that kind of self-reliance. Not because simplicity is a virtue in itself, but because the clarity that comes from simplicity makes you better at the actual work not better at managing the software that is supposed to help you manage the work.

Some tools help you think. The best ones disappear.